Next.js / Astro Migration in Turin

Product, marketing and engineering leads across Turin and the wider Piedmont corridor usually open a migration conversation when the current site stack stops serving day-to-day work. An automotive-adjacent supplier between Mirafiori and the Orbassano logistics belt finds that a decade of WordPress plugins and page-builder CSS fails mobile Largest Contentful Paint when a procurement RFP lands. A design or architecture studio around San Salvario or the Lingotto district ships portfolio case studies that look sharp in Figma but stall on shared hosting once image-heavy project pages grow. A Politecnico di Torino spinout with bilingual product docs discovers that every Italian and English release needs an engineer because templates and content are welded together in PHP.

Platform age alone is not a reason to rebuild. WPPoland treats Astro and Next.js migration as an architecture and continuity decision: inventory URL equity, editorial governance, Italian-English localization and integration edges first, then choose a rendering model. The goal is a lighter public frontend without discarding the search rankings, consent posture or publishing habits that already earn trust in northern Italy.

#Migrate or relaunch on the stack you already have

Before funding a headless move, decide whether you need a new delivery architecture or a disciplined relaunch inside the current CMS.

A relaunch refreshes information architecture, design and templates while the monolith still renders pages. A migration separates the content store from the visitor-facing layer so Astro or Next.js can ship HTML at the edge while WordPress, Drupal or another CMS remains the editorial system of record.

Migration tends to make sense when:

1. Frontend debt outruns caching. Themes stacked with unused scripts, builder markup and layout shift that still degrade Interaction to Next Paint and Largest Contentful Paint after Redis, object cache and a CDN are in place.
2. Admin and database should leave the public perimeter. For supplier portals, partner extranets or sites that process contact and CV data under Italian privacy rules, keeping wp-admin and the database off the open internet while serving static or serverless pages reduces common exploit paths.
3. One content API must feed several surfaces. Marketing site, PDF catalogs, partner microsites and documentation hubs all need the same Italian and English source of truth.
4. Hiring for legacy theme work is slow. Teams that already run TypeScript services find it easier to staff Astro or React routes than to keep extending ten-year-old template PHP.

Stay on a hardened monolith when checkout, membership or critical plugins are deeply tied to WordPress runtime and the real fixes are removing builders, adopting block themes and tightening edge cache. WPPoland will say so in writing when an in-place remediation is enough. Headless is a tool, not a default upgrade.

#Astro versus Next.js by route family

A Turin site is rarely one rendering mode. Marketing corridors, PDF-heavy supplier pages and authenticated quote areas have different caching and session needs. We map the route matrix and assign engines per family.

#When Astro fits

Astro compiles content routes to HTML with little or no client JavaScript by default. That profile fits:

• Corporate sites, service pages and studio portfolios with large photography sets.
• Italian and English resource libraries, white papers and trade-show landing pages.
• Technical documentation for university spinouts and product manuals that must stay fast on mobile.
• Catalog-style pages where every extra kilobyte of framework JS is wasted.

Static HTML on a CDN stays cheap when a campaign or press moment spikes traffic. A lead form or language switcher can still load as a small island without pulling the whole document into a client bundle.

#When Next.js fits

Next.js earns its place when routes need server rendering, auth cookies or live back-office data:

• Authenticated supplier or dealer portals and billing views.
• Configurators that call ERP, CRM or inventory APIs mid-session.
• Search and filter UIs that personalize by account or region.
• Middleware that enforces geo, token or role checks before HTML leaves the edge.

#Hybrid delivery

Many Piedmont estates run both: Astro on the public marketing host for Core Web Vitals and crawler clarity, Next.js on a path prefix or subdomain for the signed-in area. Shared design tokens and cookies keep the experience coherent without forcing every brochure page through an application runtime.

#URL inventory, redirects and SEO continuity

Careless migrations erase years of Google equity from Italian industry directories, university citations and regional press. We treat every URL change as a written decision.

Legacy origin New headless target
------------- -------------------
/blog/2022/migrazione-cms/ == [ 301 ] ==> /en/cms-migration-guide/
/chi-siamo.html == [ 301 ] ==> /en/about/
/servizi/headless/ == [ keep ] ==> /en/services/headless-development/
/wp-content/uploads/*.pdf == [ CDN ] ==> /assets/docs/*.pdf

#Discovery

We build the inventory from three sources:

1. Full crawl of live links, assets and canonicals.
2. Search Console and Bing exports covering roughly sixteen months of impressions and crawled URLs, including deep pages missing from the main nav.
3. Access logs from Nginx, Apache or Cloudflare so bookmarked and referral URLs still in use are not dropped.

#Mapping rules

• Keep the path whenever commercial and technical constraints allow.
• Single 301 to one successor when structure must change (language prefixes, collapsed categories).
• Collapse parameter duplicates from older Joomla or custom PHP (?id=, index.php?option=) onto clean canonicals.
• 410 Gone for retired content with no successor, rather than dumping traffic on the homepage.

#Pre-cutover parity

Automated checks compare staging to production across the map: self-referencing canonicals, bidirectional IT-EN hreflang, Schema.org nodes (Organization, Article, BreadcrumbList, WebPage, FAQPage), robots directives and clean 200 / 301 responses without temporary redirect chains.

#WordPress as the editorial system after cutover

Most Turin marketing and communications teams already know WordPress. A headless project does not require replacing that muscle memory. WordPress becomes the content API; Astro or Next.js becomes the public renderer.

#Modelling and delivery

• WPGraphQL for typed queries that request only the fields a template needs.
• REST API for cacheable feeds and webhook-triggered rebuilds.
• Media offload to object storage plus an image CDN so AVIF and WebP generation does not tax the application server.

+-------------------------------------------------------------------+
| HEADLESS EDITORIAL STACK |
| |
| +---------------------+ +----------------------------+ |
| | WordPress Admin | | Private DB and media | |
| | Gutenberg / ACF | -----> | Isolated from public net | |
| +----------+----------+ +----------------------------+ |
| | |
| v (publish webhook) |
| +-----------------------------------------------------------+ |
| | Build / incremental revalidation at the edge | |
| +--------------------------+--------------------------------+ |
| | |
| v |
| +-----------------------------------------------------------+ |
| | CDN: Astro HTML and Next.js functions | |
| +-----------------------------------------------------------+ |
+-------------------------------------------------------------------+

#Draft preview

Editors keep a signed preview route: clicking Preview in Gutenberg opens an authenticated Astro or Next.js SSR view with production styles, without publishing to the live CDN.

Publishing continues through development. Only the final DNS and cache sync window needs a short freeze so Italian and English drafts do not diverge mid-cutover.

#Measurement, staging, cutover and rollback

Migration value is measured, not asserted. Before DNS moves, we agree what success looks like: redirect coverage, indexation stability, Core Web Vitals floors and form or CRM health.

Migration phases
-----------------------------------------------------------------
1. Architecture audit and content schema
2. API and template build
3. Staging deploy and full URL audit
4. Pre-cutover freeze and final sync
5. DNS switch (low TTL) and edge purge
6. Hypercare telemetry and rollback watch

#Staging checks

Staging sits behind auth and noindex. We run redirect matrix scripts, visual regression across viewports, Lighthouse or WebPageTest against agreed LCP and CLS thresholds, and sandbox tests for lead forms and CRM webhooks.

#Cutover

DNS TTL drops to a few minutes days ahead. Editorial freeze is short and scheduled. After the switch, smoke tests confirm status codes, TLS, canonicals and analytics events.

#Rollback

The legacy origin stays live on a standby host for a multi-day observation window. If a blocker appears (integration failure, unexpected indexing loss), DNS and edge rules revert within minutes, traffic is verified on the old baseline, and the defect is fixed in staging before a new cutover date. Rollback is a practiced step in the runbook, not an improvised weekend firefight.

#Turin patterns: automotive, design studios and spinouts

These are observational patterns we see around Turin and Piedmont, not named client case studies and not price quotes.

Automotive and industrial suppliers often need bilingual capability pages, downloadable compliance PDFs and occasional authenticated areas for dealers or quality documentation. Public marketing routes benefit from Astro; anything session-bound belongs on Next.js. Migrations fail when PDF URLs and old /prodotti/ paths are left unmapped while a redesign invents new English-only slugs.

Design and architecture studios live on photography and project narratives. The bottleneck is usually theme weight and image delivery, not missing React features. Astro plus a modern image pipeline often outperforms a full application framework. Keep Italian project slugs stable; add English alternates with proper hreflang rather than cloning the whole portfolio under new paths overnight.

University and Politecnico-adjacent spinouts publish research explainers, hiring pages and product docs in Italian and English on uneven schedules. Headless WordPress with webhook rebuilds lets researchers and marketers ship without waiting for a theme release. Do not migrate mid-grant-deadline if the only pain is a slow homepage hero - fix the asset pipeline first.

Across all three, northern Italy traffic mixes desktop procurement research with mobile campaign visits. Measure both. A site that looks fine on a fibre connection in the city centre can still fail LCP on mid-range phones during a trade-fair push.

#Italy, EU GDPR and Italian-English publishing

Italian organisations sit under EU GDPR with national enforcement by the Garante per la protezione dei dati personali. Cookie and tracking consent, lawful bases for contact forms, and documentation of processors matter whether the frontend is PHP or Astro. Headless helps when marketing HTML ships without non-essential trackers on first paint, and when the CMS and personal data stores are not reachable from the public origin.

Practical constraints we design for:

• EU residency for application and log processing where contracts require it.
• Consent-aware analytics so measurement survives a stricter banner without inventing vanity conversion rates.
• IT-EN URL strategy with reciprocal hreflang, separate sitemaps and explicit decisions on whether /it/ and /en/ share or split path segments.
• Contract and invoice language that stays consistent when a public site is English-first but legal notices remain Italian.

WordPress Meetup Torino (https://www.meetup.com/wordpress-meetup-torino/) remains a useful local peer check. Ask operators who have already hired for migrations in the city before you sign anyone, including us.

#When you should not migrate yet

Skip or postpone headless when:

• Performance issues trace to a single heavy plugin, unoptimized media or missing cache headers that a two-week remediation would fix.
• The business cannot staff API-aware content modelling or accepts only visual page-builder editing with no structured fields.
• A rebrand, legal entity change or domain move is already scheduled in the same quarter - stacking migrations multiplies SEO risk.
• Critical commerce or booking flows depend on plugins with no headless equivalent and no budget for custom replacement.
• There is no owner for the redirect map and Search Console monitoring after launch.

In those cases WPPoland documents an in-place plan: theme cleanup, hosting and CDN hardening, consent and form review, and a later migration gate when prerequisites exist.

#How WPPoland works with your Turin team

We work as a remote engineering partner alongside your local marketing, IT or agency contacts. Typical split: you own brand voice, Italian legal copy and day-to-day publishing; we own frontend architecture, redirect governance, staging automation and cutover runbooks. Workshops can be remote or on-site when your calendar allows; delivery does not depend on relocating your stack to another country.

Handover includes repository access, environment documentation, deploy pipeline notes and a short operations runbook in English (and Italian summaries when your team needs them). Hypercare covers critical fixes and a performance review after the first real traffic spike - a product launch, a supplier RFP week or a regional campaign - not only the calm hour after DNS flips.

#Next steps for a Turin platform migration

If your organisation in Turin or elsewhere in Piedmont is weighing a move from WordPress, Drupal, Joomla or a custom stack to Astro or Next.js, start with an evidence-based audit rather than a framework preference. WPPoland reviews your URL equity, Core Web Vitals, editorial model and privacy constraints, then recommends migrate, relaunch or wait - with a concrete redirect and rollback plan either way.

Contact WPPoland to schedule a technical discovery session. Bring Search Console access, a rough content owner map for Italian and English, and any supplier or portal requirements that must survive cutover. We return a scoped architecture recommendation you can defend to leadership without invented benchmarks or fixed package pricing.