Website & application migration in Prague
I migrate sites from WordPress, Joomla, Drupal, Angular, Vue and other technologies to Astro and Next.js. I plan each migration to keep SEO, content and features intact and switch over in an agreed window. I work alone and have years of experience with both legacy and modern stacks.
- I have had a wordpress.org account since 2006.
- I contributed to WordPress core for versions 7.0 and 7.1.
- I maintain 30 plugins on wordpress.org.
- I organise and speak at WordCamps.
- I have attended every WordCamp Europe from 2017 to 2026.
- Local WordPress meetup: NášWP WordPress komunita
This page is for a Prague company that runs a Czech (cs) and English (en) site on WordPress, Drupal or a Next.js stack that grew faster than the product needed. Marketing pages behave like static brochures but still download application-scale JavaScript. I split the stack: Astro for public cs and en content, Next.js for logged-in areas, and I align cookie loading with Act No. 127/2005 Coll. section 89 and accessibility with Act No. 424/2023 Coll., under supervision practice of the Office for Personal Data Protection (ÚOOÚ). I work solo from Gdynia, remotely and in writing.
When a Prague site is ready to replatform
You usually reach out when one of these blocks a release:
- Core Web Vitals field data drifts above the public web.dev thresholds on Czech mobile networks while the marketing team only publishes twice a week
- A Drupal or Joomla install no longer receives security updates your IT policy allows
- English and Czech pages diverged because translation plugins stored different slug patterns
- Legal asks for proof that analytics tags do not run before cookie consent under Czech electronic communications law
If a plugin cleanup on the existing CMS would fix the issue, I say so in the first written review.
Czech and English information architecture
Prague B2B sites commonly use:
- Czech as the primary commercial language with full product detail
- English for export pages, investor summaries and API docs
- Sometimes German landing paths for DACH campaigns without a full
desite
I model locales in the CMS with a stable translation group key. Astro routes become /cs/... and /en/... (or your existing pattern if it already works in Search Console). Each built page lists hreflang siblings with return links.
The inventory includes Seznam-indexed URLs, not only Google Search Console, because Prague readers still discover content through native search properties.
Prague concentrates the country’s largest pool of export-facing B2B domains, often maintained in Czech with English investor mirrors. When translation plugins forked slugs per locale, middleware on a shared Next.js shell hid the canonical path from editors until Search Console and Seznam disagreed on which /cs/ product page was authoritative.
The Office for Personal Data Protection (ÚOOÚ) at uoou.gov.cz/en enforces GDPR alongside sector regulators; Prague SaaS vendors increasingly attach staging HAR summaries to DPIAs before board sign-off. Astro marketing routes that ship without default analytics imports give counsel a shorter baseline than legacy _app files that initialised tags on mount.
Rebuilding with stable CMS translation keys restores reciprocal hreflang between Czech commercial copy and English export summaries without client-side locale guessing that broke when campaigns temporarily added German landing paths for DACH ads. Act No. 127/2005 Coll. consent screenshots from staging are filed beside the URL map so ÚOOÚ follow-ups reference the same build legal approved. Seznam sitemap URLs are diffed against Google exports so Czech-primary slugs stay indexed through cutover week. Export landing pages keep stable attachment URLs for customs brokers who bookmarked specification PDFs.
Act No. 127/2005 Coll. section 89 and consent order
The Electronic Communications Act (zakonyprolidi.cz/cs/2005-127) section 89 paragraph 3 states that anyone who stores data on or reads data from a user terminal must obtain prior provable consent from the user, except for storage strictly necessary to transmit a message or provide a service explicitly requested by the user.
In a migration I translate that into load order:
- HTML shell, self-hosted fonts and essential session cookies for features the user explicitly opened (for example a client zone on Next.js)
- Consent UI with equal accept and refuse paths
- Analytics, heatmaps and marketing pixels only after documented opt-in
Global Next.js _app imports that initialise tags on mount are removed from Astro marketing layouts. The same guard applies to remaining Next.js routes so cs and en behave consistently.
The ÚOOÚ (uoou.gov.cz/en) enforces GDPR alongside sector regulators. I update the script inventory annex for your privacy notice; I do not sign legal statements on your behalf.
Act No. 424/2023 Coll. and accessibility from June 2025
Act No. 424/2023 Coll. on accessibility requirements for certain products and services (zakonyprolidi.cz/cs/2023-424) took effect on 28 June 2025 for services within its scope, implementing European accessibility rules.
During template rebuild I:
- Use semantic landmarks, headings in logical order and visible focus outlines
- Label forms and error messages in the page language
- Provide text alternatives for meaningful images
- Document known gaps and remediation dates your legal team approves
Astro’s default static HTML makes landmark structure straightforward; interactive islands receive keyboard tests.
Astro for marketing, Next.js for client areas
| Route family | Typical Prague example | Target |
|---|---|---|
| Product and service pages | Industrial automation, cybersecurity offerings | Astro static pages |
| Blog and changelog | Release notes, security advisories | Astro content collections |
| Careers | Open roles | Astro |
| Client dashboard | Licence usage, ticket portal | Next.js |
| Configurator | Pricing with login | Next.js |
| OIDC or SAML callback | Enterprise SSO | Next.js server route |
Islands handle small widgets (ROI calculator, consent-friendly map) without promoting the whole site to a single-page app (docs.astro.build/en/concepts/islands/).
WordPress may remain the editorial core: editors use Gutenberg or ACF, the public site reads via REST. Official WordPress REST documentation describes the endpoints used for import and preview.
URL inventory, Seznam and Google parity
The inventory merges:
- Crawl of the live site
- Google Search Console export
- Seznam Webmaster URLs where you grant access
- Server logs for PDF attachments linked from ranked pages
Each row: path, locale, CMS ID, action (keep, 301, merge). Permanent moves use server-side 301 per Google redirect guidance.
Corporate identifiers required under the Czech Civil Code trade disclosures stay visible in footers across cs and en templates (company name, registered seat, identification number links to the public register your legal team maintains).
Core Web Vitals gate before cutover
| Metric | web.dev good threshold (75th percentile) |
|---|---|
| LCP | within 2.5 seconds |
| INP | within 200 milliseconds |
| CLS | at or below 0.1 |
I compare the same URL sample before and after the Astro build on staging. Claims stop at those public thresholds.
Choosing headless WordPress versus a flat file repo
Some Prague teams want editors in WordPress forever; others want Git-backed Markdown for developer docs. I support both: WordPress REST for marketing, content collections in the repo for technical manuals. The framework map states which collection lives where so security reviews know which attack surface changed.
Hybrid setups need clear preview URLs: editors click preview in WordPress, see the Astro render, and approve before publish hooks fire webhooks to rebuild static pages.
Drupal and Joomla exit paths
Drupal 7 end-of-life pressure and Joomla extension debt are common triggers. Export paths vary: JSON via custom scripts, XML feeds, or staged database dumps. I never bulk-import unrevised HTML with inline styles from WYSIWYG eras; content gets normalized into components your team can maintain.
Legacy ?Itemid= Joomla URLs receive explicit 301 rows so Seznam and Google stop hitting parameter permutations.
When your sales team embeds Calendly or similar schedulers, I load them as consent-gated islands or link out to the vendor in a new tab, depending on what your DPO prefers after reading the transfer assessment.
Comparison: monolithic CMS versus split Astro and Next.js
| Concern | Monolithic WordPress theme | Split Astro plus Next.js |
|---|---|---|
| Editor familiarity | High | High when WordPress stays headless |
| Public JS payload | Often large | Small on Astro routes |
| Client portal | Plugin or custom | Native Next.js |
| Cookie surface | Entire theme | Per-route policy possible |
| Rollback | Theme switch | Edge route to legacy deploy |
This table is a planning aid only; your inventory decides the actual split.
Written project flow
- You send the domain, CMS and access to analytics or Search Console.
- I return the URL inventory draft and framework map for written approval.
- Astro cs and en prototypes on preview with three content types you choose.
- Consent and script register aligned with section 89 paragraph 3.
- Redirect tests and hreflang validation on staging.
- Phased cutover: marketing first, portal last.
- Handover repository, CI, editor note and open risk list.
Personal data flows ÚOOÚ expects you to describe
Forms feeding HubSpot, Pipedrive or domestic CRM tools are listed with legal basis and processor name. Cookie consent logs and CMP exports are mentioned in the privacy notice appendix. Migration is a sensible moment to delete unused newsletter widgets that still called retired Mailchimp endpoints.
If your DPO already maintains a record of processing activities, I align script and form changes with that register instead of inventing a parallel spreadsheet.
Seznam and Google monitoring after launch
Czech teams often track Seznam Webmaster coverage alongside Search Console. I submit updated sitemaps for both properties after each cutover phase and watch server logs for bots hitting retired Joomla query strings (?option=com_content patterns).
Structured data for Organization and Product is compared against the legacy site with a diff tool. Missing FAQPage markup from an old WordPress plugin is either restored intentionally or removed with your approval.
Risks specific to Czech English pairs
- Mixed slug scripts: English slugs with diacritics in Czech paths break analytics segments. I normalize slugs in the inventory before build.
- Cookie wall dark patterns: Refusing non-essential cookies must stay as easy as accepting under section 89 practice. I test both buttons on staging in cs and en.
- Accessibility statement: Act 424/2023 may require a published accessibility declaration for in-scope services. I link the statement from the footer in both languages once legal supplies text.
- Exchange rate widgets: CZK and EUR display in Astro can be a tiny island fed by your API without hydrating the article body.
Extended verification table
| Step | Purpose |
|---|---|
| Legacy query URL purge | Retire index.php patterns with 301 or 410 |
| cs and en canonical pair | Each URL self-canonicalises; duplicates collapse |
| Portal session isolation | Next.js caches do not leak authenticated HTML |
| Invoice footer fields | IČO and registered seat visible on cs and en |
| Third-party font audit | Self-host where consent or transfer review requires |
| Post-cutover Seznam ping | You submit refreshed sitemap when your process requires |
What you receive at handover
Git repository with CI, environment variable documentation, redirect configuration, bilingual editor guide, open issue list and staging screenshots for consent order and keyboard navigation on representative templates.
Contact
Use the contact page with your Prague site URL, current CMS, languages (cs, en, others) and whether a client login exists. I reply on working days with a concrete scope outline and staging plan.
Selected projects
Examples of my work.
E-commerce Development: PARTNERSTWO IOS/ANDROID APP
The mobile app, available at Google Play, was developed for NSZZ Solidarność to achieve the key objectives of a project promoting good practices in sustainab...
E-commerce Development: pepegotti.com
The pepegotti.com website is a modern platform dedicated to furniture distribution, combining clear design with advanced functionalities tailored for both in...
E-commerce Development: pluginfinance.com
pluginfinance.com is a modern, highly scalable WordPress-based service dedicated to showcasing and distributing financial plugins. The project was designed w...
WordPress support & development in Prague
See also in Czech Republic
Need this service: Next.js / Astro migration in Prague?
Describe your project by e-mail. I reply within 48 hours.
Describe your projectExplore other WordPress services and knowledge base
Migration to Astro, Next.js, and headless WordPress.
WooCommerce sync with ERP and wholesale systems.
Business process automation around WordPress and company systems.
Library of concrete automation use cases.
Headless WordPress, Sanity, Strapi, and Contentful with Astro or Next.js.
Astro, MDX, edge delivery, and Core Web Vitals measured on real traffic.
Custom WordPress engineering and architecture.
Scalable headless, ERP, and AI architecture for enterprise.
Related categories
Supporting articles

Six to sixteen weeks for typical engagements, with a four-phase shape: discovery, scoping, build and cutover, tuning. The variables are catalogue size, integration count, URL preservation, and editorial team readiness, not framework choice.

A definitive 4-year Total Cost of Ownership (TCO) analysis, real-world Core Web Vitals benchmarks, Astro 7 GraphQL APQ architecture, and a 10-point executive decision matrix for choosing between decoupled and traditional WordPress.

The Shopify Plus vs WooCommerce headless decision in 2026 is no longer a binary "platform vs custom" trade-off. Both can run headless, both integrate AI, both ship at the edge. The real axes are control, total cost over five years, and exit strategy. This article walks the matrix with confirmed platform facts.