Next.js / Astro migration in Porto

Migration to Astro & Next.js in Porto. I migrate sites from WordPress, Joomla, Drupal and other CMSs with redirect mapping, SEO checks and staged cutover.

Next.js / Astro migration

Website & application migration in Porto

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: WordPress Porto Meetup

My WordPress.org profile

Porto is the second-largest city in Portugal after Lisbon, situated on the Douro estuary at the heart of the Porto Metropolitan Area (Área Metropolitana do Porto) of roughly 1.8 million residents and the industrial engine of Northern Portugal (Região Norte). Many companies across Porto, Matosinhos, Maia, Vila Nova de Gaia, and surrounding manufacturing corridors run websites that grew over years on WordPress, Joomla, or Drupal, usually in European Portuguese (pt-PT) and English (en), and often adding Spanish (es), French (fr), or German (de) for export buyers. When that legacy CMS stack becomes sluggish on mobile, fragile during updates, or risky to patch, moving the public frontend to Astro or Next.js solves the bottleneck. Working solo, remotely and in writing from Gdynia, I execute that migration step by step so your organic search visibility and incoming enquiries survive the switch intact.

#Does my Porto website actually need a migration?

Not always. If the slowness stems from a single bloated page builder, an uncompressed media library, or missing server-level page caching, cleaning up the existing CMS is cheaper, and I state that plainly in my written review. A migration to Astro or Next.js earns its keep when the underlying platform itself is the obstacle: plugin updates that break layout templates, an administrative dashboard that editors avoid, static content that gets rebuilt by PHP and MySQL on every visitor request, or a security patch schedule nobody dares to touch ahead of an export trade fair.

When a new frontend is justified, I select the framework according to what each route group on your site does:

  • Astro fits content-driven websites: corporate service pages, B2B industrial catalogues, architectural and hospitality showcases, editorial blogs, and technical documentation. It compiles clean static HTML at build time and loads JavaScript only where an interactive component (island) explicitly requires it, making it straightforward to stay well within Google’s official Core Web Vitals thresholds (Largest Contentful Paint up to 2.5 s, Interaction to Next Paint up to 200 ms, Cumulative Layout Shift up to 0.1).
  • Next.js fits platforms with authenticated B2B distributor logins, personalised client dashboards, dynamic stock or lead-time lookups, or heavy per-request server rendering. Both frameworks can read content from a headless CMS, from Markdown/MDX files in Git, or directly from your existing WordPress installation via its REST API or WPGraphQL during a staged transition.

#Porto and Northern Portugal sectors: where decoupled frontends deliver the clearest return

Across business districts from Boavista, Marquês, and Baixa do Porto to UPTEC (Science and Technology Park of the University of Porto), Lionesa Business Hub in Matosinhos, the Maia industrial and tech parks, and the Port of Leixões logistics corridor, companies manage web platforms with distinct engineering demands:

  • Industrial Manufacturing, Footwear, Textiles, Cork and Metalomecânica Exporters (Maia, Trofa, Vale do Ave, São João da Madeira, Santa Maria da Feira): Northern Portugal is Portugal’s primary industrial export region. Manufacturers and B2B suppliers publish hundreds of product family pages, technical datasheets, ISO certifications, and lookbooks across four or five European languages (pt-PT, en, fr, de, es). Moving from a fragile WordPress + WPML or Joomla setup to typed Astro collections guarantees that every product URL and PDF datasheet resolves in a single hop while serving pages instantaneously to international buyers.
  • Software Scaleups, Engineering R&D and Shared Service Centres (UPTEC, Lionesa Matosinhos, Boavista, Campanhã): Technology hubs and R&D centres operating in Greater Porto publish developer documentation, security compliance portals, and high-volume recruitment pages. Astro allows engineering teams to maintain technical docs in Git-backed MDX while marketing and HR teams publish campaign and career pages through a headless CMS.
  • Port Wine Houses, Hospitality, Architecture and Cultural Tourism (Vila Nova de Gaia, Ribeira, Foz do Douro, Douro Valley): Cellar tour operators, boutique hotel groups, and architectural studios rely on image-heavy portfolios, wine catalogues, and booking engine integrations. Pre-rendered Astro templates paired with AVIF/WebP image pipelines eliminate layout shift (CLS) and render-blocking scripts on mobile connections.

#How do I move a Porto website without losing Google search traffic?

Organic traffic attaches to specific URLs, so the URL inventory comes before any code is written:

  1. Exhaustive URL and asset inventory. I crawl the live website and combine the output with your Google Search Console and analytics data: every indexable URL, every landing page that receives impressions, clicks, or external backlinks, and legacy redirects or PDF catalogues from earlier redesigns.
  2. Written 301 URL map. Each historical URL receives one explicit outcome in a version-controlled redirect file: retain the exact path, redirect via a single-hop HTTP 301 to its closest equivalent, or return a deliberate HTTP 410 when obsolete content is permanently retired. Redirect chains and blanket redirects to the homepage are strictly excluded.
  3. Typed content model. Legacy post types, custom fields, taxonomies, and navigation menus become strictly typed collections (validated with Zod in Astro). Visual page-builder shortcodes, inline styles, and translations linked through legacy plugin tables are cleaned up during extraction.
  4. Structured data generation. Organization, BreadcrumbList, Article, Product, LocalBusiness, or FAQPage JSON-LD markup is generated directly from the same typed fields as the visible text, so schema and visible copy never drift apart.
  5. Field-by-field parity check on staging. I compare old and new pages across <title>, meta description, canonical URL, H1-H3 hierarchy, structured data, and internal links on a non-indexed preview domain.
  6. Staged cutover. Larger portals transition section by section behind edge routing rules while the legacy system serves the remaining paths. Smaller corporate sites switch in a single coordinated window during low traffic with the old server kept warm for instant rollback.
  7. Post-launch Search Console monitoring. I register the new XML sitemaps in Search Console, track coverage in the Page Indexing report, and check redirected addresses over the initial weeks after launch. If the domain or subdomain changes (for example, moving from .com to .pt), I file a Change of Address notification in Search Console.

#How should European Portuguese (pt-PT), Brazilian Portuguese (pt-BR) and export languages be paired?

Portuguese is the official language of Portugal, and a Porto business website typically serves several markets at once: domestic clients in European Portuguese, European and North American buyers in English (en), Spanish (es), French (fr), or German (de), and sometimes Brazilian buyers who search in Brazilian Portuguese (pt-BR). Deciding the URL structure (/pt/, /en/, /fr/, /es/) and hreflang strategy happens before content moves.

Google accepts a language code alone (pt) or a language code combined with an ISO 3166-1 Alpha 2 region code (pt-PT, pt-BR). If your Portuguese copy is written specifically for Portugal and you also publish a separate Brazilian edition, distinct pt-PT and pt-BR annotations let Google surface the right regional version in each market. If a single Portuguese edition serves all Lusophone readers alongside English, pt (or pt-PT) paired with en and x-default is used. Every page must list itself and all sibling translations reciprocally; I generate these tags directly from a shared translation ID in the content model and verify reciprocity on the compiled HTML before cutover.

#Pre-cutover verification table for Porto migrations

Verification areaWhat I check before switching production traffic
URL & PDF redirect ledgerEvery indexed URL and linked PDF in Search Console and server logs returns HTTP 200 or a single 301 hop
Multilingual hreflang (pt-PT, en)Bidirectional return links and self-referencing canonicals verified on built HTML across all export locales
Core Web Vitals thresholdsTemplates verified against official web.dev thresholds (LCP up to 2.5 s, INP up to 200 ms, CLS up to 0.1)
CNPD & Lei 41/2004 privacy rulesZero non-essential analytics or marketing cookies before consent; processor list documented per form
DL 82/2022 & WCAG 2.1 AASemantic HTML landmarks, heading hierarchy, form labels, focus order and colour contrast checked
Art. 171 CSC & footer linksNIPC/NIF, Conservatória do Registo Comercial do Porto, share capital and Livro de Reclamações verified

Moving from a monolithic CMS to Astro or Next.js is the best moment to verify compliance across Portuguese data protection, cookie storage, digital accessibility, and statutory corporate disclosures:

Personal data and CNPD supervision (Lei n.º 58/2019 & GDPR). Personal data collected through your website, including contact forms, B2B quote requests, recruitment uploads, newsletter lists, and analytics logs, is governed by the GDPR and Portuguese Law no. 58/2019 of 8 August, supervised by the Comissão Nacional de Proteção de Dados (CNPD). Because decoupling the frontend changes where form submissions are sent and stored, I document every serverless endpoint, CRM webhook, and EU/EEA hosting region so your privacy policy (Política de Privacidade) and records of processing activities reflect the live stack, and so your team has the exact processor inventory needed under GDPR Article 33 (72-hour breach notification to the CNPD).

Cookies and terminal storage (Lei n.º 41/2004). Under Law no. 41/2004 of 18 August (transposing the ePrivacy Directive), storing or reading non-essential data on a user’s device requires prior informed consent, with an exemption only for strictly necessary technical storage. Because the rebuilt Astro or Next.js frontend loads only the scripts you explicitly approve, forgotten campaign pixels are dropped and analytics or marketing tags remain blocked until the visitor actively consents.

Accessibility (Decreto-Lei n.º 82/2022 & Decreto-Lei n.º 83/2018). Portugal transposed the European Accessibility Act through Decree-Law no. 82/2022, which applies to covered products and consumer e-commerce/digital services from 28 June 2025, alongside Decree-Law no. 83/2018 (monitored with technical tools from AMA, accessibility.gov.pt). Building new Astro or Next.js components from scratch ensures clean heading hierarchies, keyboard navigation, form labels, and WCAG 2.1 Level AA contrast across every template.

Mandatory company disclosures and consumer links (Art. 171 CSC & DL n.º 24/2014). Under Article 171 of the Portuguese Commercial Companies Code (Código das Sociedades Comerciais), corporate websites of Portuguese companies (such as a sociedade por quotas, Lda., or sociedade anónima, S.A.) must display the registered company name, legal form, registered office (sede), Commercial Registry office (Conservatória do Registo Comercial, e.g. Porto), corporate tax identification number (NIPC / NIF), and share capital (capital social). Where the website sells goods or services to consumers in Portugal, information duties under Decree-Law no. 24/2014 (supervised by DGC and ASAE) and the mandatory link to the electronic complaints book (Livro de Reclamações Eletrónico, livroreclamacoes.pt, where applicable) are built directly into the global footer templates.

#What breaks most often in a CMS migration, and how do I prevent it?

  • URLs and PDF catalogues that quietly vanish. After launch I re-crawl the full historical URL list against the live domain and fix any unexpected 404 or redirect chain immediately.
  • One language edition left behind. If the English route redirects properly but its Portuguese or French counterpart is missed, hreflang reciprocity breaks. I verify every language pair on the built HTML.
  • Forms, booking widgets and tracking failing silently. In legacy WordPress sites, forms and conversion events live inside plugins. I catalogue every integration upfront and test each one on staging with real submissions before cutover.
  • Editors locked out of publishing. A fast frontend that your marketing team cannot update without calling a developer is an operational failure. The editing workflow is agreed in the written scope and tested with your editors before cutover.

#Deliverables transferred to your Porto company at handover

Your company receives full ownership of the Git repository, the complete URL map and edge redirect file, documented environment variables, the automated deployment pipeline, and a concise written guide explaining how content is edited and published. Google Search Console and analytics stay in your own accounts.

The broader engineering process is described on my Next.js and Astro migration page, and if you want to keep WordPress or another system as a decoupled editorial backend, see the headless CMS developer page.

#How to request a written scope for your Porto website

Send me your current website URL, the CMS and version it runs on, the languages it publishes in (pt-PT, en, es, fr, de or others), and where your traffic comes from (organic search, paid ads, newsletters, booking platforms, or partner referrals) via the contact page. Read-only Search Console access helps but is not required for an initial look. I reply in writing on working days with a free initial estimate and written scope covering what moves, what changes, which URLs need redirects, and which technical risks I see on your site.

See also in Portugal

Need this service: Next.js / Astro migration in Porto?

Describe your project by e-mail. I reply within 48 hours.

Describe your project

Explore other WordPress services and knowledge base