Website & application migration in Turin
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 Torino Meetup
Next.js to Astro migration in Turin: engineering zero-JS industrial and corporate platforms
Turin (Torino) is the historical heart of Italian industrial engineering, automotive manufacturing, aerospace research, and B2B software. Across the mobility and robotics clusters at Mirafiori and Lingotto, the aerospace research corridor along Corso Marche, the innovation campus at OGR Tech (Officine Grandi Riparazioni), the Environment Park in Spina 3, and the Politecnico di Torino ecosystem in Crocetta and Cenisia, engineering firms and digital product companies run complex multi-language web platforms. Over the past five years, many of these organizations built their corporate portals, technical documentation hubs, and supplier catalogs on Next.js, assuming that a full React single-page application runtime was necessary for every web property.
In production, running a content-heavy B2B catalog, investor relations portal, or multilingual engineering specification site on a full Next.js hydration runtime introduces avoidable operational friction:
- Unnecessary Client-Side JavaScript Execution: A technical specification page, press release, or supplier compliance directory is fundamentally static reading material. Delivering a full React runtime, router bundle, and serialized JSON payload forces the visitor’s browser to parse and execute hundreds of kilobytes of JavaScript just to display text and tables. When procurement engineers or international buyers access your catalog on mobile connections at trade fairs or production plants, main-thread blocking degrades Interaction to Next Paint (INP).
- Serverless Cold Starts and SSR Cache Fragility: With the Next.js App Router, a single uncached dynamic call or header read can opt an entire route tree out of static generation. Companies end up paying for continuous serverless compute, Edge middleware invocations, and Redis cache layers simply to serve pages that change only when an editor publishes an update in a headless CMS.
- Italian Regulatory Exposure in Client-Side Bundles: Under the strict enforcement of the Italian Data Protection Authority (Garante per la protezione dei dati personali), non-essential tracking scripts, unconsented telemetry, and third-party US CDN font requests embedded inside React
_apporlayout.tsxtrees create immediate compliance risks. Furthermore, custom JavaScript div-based controls frequently fail keyboard navigation and screen-reader audits required under Italy’s Legge Stanca (Legge 9 gennaio 2004, n. 4) and the European Accessibility Act transposition (D.Lgs. 27 maggio 2022, n. 82).
I migrate Turin corporate portals, industrial catalogs, and SaaS marketing platforms from Next.js to Astro. I work as an independent developer based in Gdynia, Poland, collaborating with your Turin engineering or marketing stakeholders entirely in writing. By replacing whole-page React hydration with Astro’s zero-JavaScript-by-default compilation and isolated Astro Islands, I eliminate runtime bloat while keeping your existing React components where genuine interactivity is required.
Why Turin B2B and engineering platforms outgrow Next.js
When an automotive Tier-1 supplier in Rivalta or Grugliasco, an aerospace systems integrator near Caselle, or a fintech and design studio in Centro Storico or San Salvario evaluates their web stack, the mismatch between Next.js and content-driven publishing usually shows up in three areas: Core Web Vitals, build-pipeline complexity, and total cost of ownership.
Core Web Vitals and Main-Thread Contention
For supplier portals in Rivalta and Lingotto, field data in Chrome User Experience Report (CrUX) is judged against the three official “Good” thresholds on web.dev:
- Largest Contentful Paint (LCP): at or under
2.5 secondsfor Italian and European field traffic. - Interaction to Next Paint (INP): at or under
200 millisecondsduring catalog interactions. - Cumulative Layout Shift (CLS): at or below
0.1across specification layouts.
On a Next.js site, even when pages are pre-rendered via Static Site Generation (getStaticProps or App Router static segments), the browser downloads the HTML and then immediately downloads, parses, compiles, and executes the React framework bundle to “hydrate” the DOM. During that hydration window, the browser’s main thread is occupied reconciling the virtual DOM. If a user clicks a language switcher, opens a specification accordion, or types into a part-number search field during hydration, the input is delayed until the JavaScript task finishes, pushing INP above the 200 ms threshold.
Astro changes this execution model at the compiler level. By default, Astro components (.astro) render to pure, semantic HTML and scoped CSS at build time or on the server, shipping zero framework JavaScript to the browser. Interactive elements are explicitly opted in using client directives:
---
// src/pages/it/prodotti/[slug].astro
import BaseLayout from '../../../layouts/BaseLayout.astro';
import TechnicalSpecTable from '../../../components/TechnicalSpecTable.astro';
import PartConfigurator from '../../../components/react/PartConfigurator.tsx';
import { getProductBySlug } from '../../../lib/cms';
const { slug } = Astro.params;
const product = await getProductBySlug(slug, 'it');
---
<BaseLayout title={product.seoTitle} description={product.seoDescription} lang="it">
<article class="product-shell">
<h1>{product.name}</h1>
<p class="lead">{product.summary}</p>
<!-- Torino catalog table: compiled HTML, no client framework bundle -->
<TechnicalSpecTable specs={product.specifications} certifications={product.isoCerts} />
<!-- Part configurator island: React loads only after scroll reaches this block -->
<PartConfigurator
client:visible
sku={product.sku}
toleranceMatrix={product.toleranceMatrix}
locale="it-IT"
/>
</article>
</BaseLayout>Because TechnicalSpecTable, the navigation header, the legal footer, and the editorial prose ship as plain HTML, the browser paints the Largest Contentful Paint immediately and leaves the main thread idle. The React PartConfigurator island loads its JavaScript bundle asynchronously only when the engineer scrolls down to the configuration section.
Eliminating Next.js Upgrade Churn and Build-Pipeline Fragility
Many Turin engineering teams maintain Next.js repositories that started on Next.js 12 or 13 (pages/ directory) and are now caught half-migrated to the Next.js 14/15 app/ directory. Every framework upgrade forces adjustments to React Server Components boundaries ("use client" vs. server modules), caching heuristics (fetch cache defaults, revalidatePath), and complex webpack or Turbopack plugin chains.
Astro uses a clean, explicit Vite-based build pipeline and a file-based routing model where every .astro page executes its data-fetching frontmatter strictly at build time (or server request time in SSR mode) in standard TypeScript. There are no hidden React Server Component serialization payloads (__NEXT_DATA__ or RSC flight streams) duplicating your page text inside <script> tags at the bottom of every HTML document. Removing that duplicated JSON payload typically cuts raw HTML document transfer size in half before gzip or Brotli compression is even applied.
Preserving multilingual SEO, hreflang and legacy industrial URLs
Turin companies rarely operate in a single language. An industrial manufacturer or B2B software provider in Piedmont typically publishes in Italian (it), English (en), German (de) for DACH automotive buyers, and French (fr) for cross-Alpine supply chains in Auvergne-Rhône-Alpes.
A poorly executed framework migration can destroy years of organic search equity if URLs shift, trailing slashes change, or hreflang reciprocity breaks. When I execute a Next.js to Astro migration, SEO preservation is treated as a deterministic engineering gate rather than an afterthought.
1. Complete Route Inventory and Canonical Mapping
Before touching page templates, I extract every route from your existing Next.js codebase (pages/, app/, next.config.js redirects() and rewrites(), plus your live XML sitemaps). I build a machine-verifiable route manifest covering:
- Localized marketing and service URLs (
/it/soluzioni/...,/en/solutions/...,/de/loesungen/...,/fr/solutions/...). - Deep links to technical datasheets, PDF manuals, CAD/STEP archives, and UNECE/ISO compliance certificates often referenced in printed catalogs or QR codes on machinery.
- Blog, newsroom, and investor relations archives.
If you keep the exact URL structure in Astro, I configure Astro’s trailingSlash and build.format options in astro.config.mjs to match your historical canonical format byte-for-byte, preventing redirect chains that waste crawl budget. Where legacy URLs are consolidated, I generate static edge redirect rules (_redirects for Cloudflare Pages, vercel.json, or Nginx map files) returning direct 301 Moved Permanently responses with zero intermediate hops.
2. Reciprocal Hreflang and Schema.org Graph Parity
In Next.js projects, hreflang tags and JSON-LD structured data are frequently assembled through scattered next-seo props or inconsistent generateMetadata functions that drift out of sync across locales. In Astro, I centralize canonical URLs, hreflang alternate links (including x-default), and Schema.org @graph generation into a single strongly typed <SEOHead /> component backed by Astro Content Collections (zod schemas).
Every build validates that:
- Every Italian page links to its exact translated counterparts (
en,de,fr) and back again. Organization,LocalBusiness,Product,TechArticle,FAQPage, andBreadcrumbListJSON-LD schemas are rendered server-side in the document<head>without relying on client-side JavaScript injection.
Italian statutory and regulatory compliance in the architecture
A web platform operated by an Italian Società per Azioni (S.p.A.) or Società a responsabilità limitata (S.r.l.) registered in Turin must comply with specific Italian statutory requirements alongside European Union regulations. Porting a Piedmont enterprise site from Next.js to Astro creates a deterministic compile-time boundary for Italian statutory compliance.
1. Garante per la Protezione dei Dati Personali & Cookie Guidelines (10 June 2021)
The Italian Data Protection Authority (Garante per la protezione dei dati personali), enforcing the GDPR (Regolamento UE 2016/679) and the Italian Privacy Code (Codice in materia di protezione dei dati personali, D.Lgs. 196/2003 as amended by D.Lgs. 101/2018), issued binding Linee guida cookie e altri strumenti di tracciamento on 10 June 2021 (Provision No. 231).
Under the Garante’s enforcement rules:
- Zero Non-Technical Scripts Before Prior Consent: Analytical cookies (unless strictly first-party and anonymized under the Garante’s specific masking requirements) and all marketing/profiling scripts must not execute until the user gives explicit affirmative consent.
- Equal Visual Prominence and Default Continuation Without Tracking: The banner must feature a clear closure mechanism (commonly the top-right
Xwith explicit notice that closing continues navigation with only technical cookies) and equal visual hierarchy between accept and reject actions. - Self-Hosted Typography and Assets: Loading Google Fonts or icon libraries from third-party US servers exposes visitor IP addresses on page load without consent. During the Astro migration, I eliminate
next/font/googleruntime calls and self-hostsubsetted.woff2fonts directly from your first-party origin withfont-display: swap.
In Astro, because there is no global React provider tree automatically hydrating third-party SDKs, analytics and marketing tags are strictly gated behind a lightweight, consent-aware script loader or offloaded to first-party server-side tagging.
2. Legge Stanca (Legge 4/2004) and D.Lgs. 82/2022 Accessibility
Italy’s Legge 9 gennaio 2004, n. 4 (Legge Stanca), implemented by AgID, sets accessibility duties for public bodies. D.Lgs. 27 maggio 2022, n. 82 transposes Directive 2019/882 and, as AgID explains on its accessibility pages, applies to private providers of the digital services listed in that decree, with AgID acting as supervisory authority and handling complaints through its reporting channel.
Next.js applications built with heavy UI component libraries often render custom dropdowns, modal dialogs, and tabs as nested <div> elements that lack ARIA states, trap keyboard focus, or break when React hydration fails on slow connections. While rebuilding Piedmont templates in Astro I:
- I use native HTML5 semantic landmarks (
<header>,<nav>,<main>,<article>,<aside>,<footer>), native<details>/<summary>disclosures, and native<dialog>elements wherever possible. - Every interactive Astro Island is tested for full keyboard operability (
Tab,Shift+Tab,Escape, arrow keys), visible:focus-visibleoutlines, programmatic form labels, and WCAG 2.1 Level AA color contrast ratios. - If your Turin business falls under the D.Lgs. 82/2022 service list, the semantic DOM and AgID linee guida alignment make publishing and updating your dichiarazione di accessibilità straightforward; purely informational sites outside that list still benefit from WCAG hygiene but are not automatically subject to the same AgID filing workflow.
3. Mandatory Corporate Disclosures under Art. 2250 Codice Civile
Under Article 2250 of the Italian Civil Code (Codice Civile), Italian capital companies (S.p.A., S.r.l., S.a.p.a.) must publish specific corporate identification data on their websites and digital communications, not merely buried inside a PDF, but accessible across the site. I structure the global Astro footer and legal layout to ensure deterministic display across all locales of:
- Full company name (Ragione sociale) and registered office address (Sede legale in Torino or province).
- VAT number (Partita IVA) and Tax Code (Codice Fiscale).
- Registro delle Imprese di Torino registration number and REA (Repertorio Economico Amministrativo) number (e.g.,
TO - XXXXXX) at the Camera di Commercio di Torino. - Paid-up share capital (Capitale sociale i.v. - interamente versato), and whether the company is a single-member entity (Società a socio unico) or subject to management and coordination (soggetta a direzione e coordinamento under Art. 2497-bis c.c.).
- Certified email address (PEC - Posta Elettronica Certificata) and, where applicable for B2B invoicing specifications, the Codice Destinatario SDI (Sistema di Interscambio).
Step-by-step technical migration plan for Piedmont sites
I execute every Next.js to Astro migration through a structured, verifiable engineering sequence in an isolated Git branch so your ongoing operations in Turin experience zero downtime.
| Migration Layer | Legacy Next.js Architecture | Target Astro Architecture |
|---|---|---|
| Content & Schemas | Untyped JSON responses, scattered Markdown, or ad-hoc fetch calls inside getStaticProps / RSCs | Strongly typed Astro Content Collections (zod validation at build time) or typed Headless CMS loaders (Sanity, Strapi, Directus, DatoCMS, Storyblok, WordPress REST/GraphQL) |
| Page Rendering | Full-page React VDOM hydration (__NEXT_DATA__ or RSC flight payloads on every route) | Zero-JS static HTML compilation (.astro) with selective hydration (client:load, client:visible, client:idle) only for interactive islands |
| Image Pipeline | Runtime <Image> serverless optimization endpoint (/_next/image?url=...) incurring compute billing | astro:assets <Image /> and <Picture /> compiling responsive .avif and .webp srcsets with explicit dimensions (CLS = 0) at build time |
| Routing & i18n | Complex middleware.ts locale redirects and fragile App Router [lang] dynamic segments | Native Astro i18n routing (src/pages/[lang]/...) with compile-time locale parity verification and zero-latency static HTML delivery |
| Styling & Design | CSS-in-JS runtime overhead (styled-components, Emotion) or unpruned CSS bundles | Scoped Astro styles or build-time Tailwind CSS compiled from your team’s existing Figma or design files |
Handling Headless CMS Webhooks and Incremental Builds
Many Turin enterprises manage their editorial content in DatoCMS (widely used in Italy), Storyblok, Sanity, Strapi, Directus, or a headless WordPress backend. During the migration:
- I replace Next.js On-Demand ISR (
revalidateTag/revalidatePath), which often suffers from stale cache states across edge nodes, with Astro’s Content Layer API or clean build hooks. - For catalogs with thousands of SKUs or technical datasheets, Astro’s Content Layer caches unchanged CMS records between builds so a webhook triggered by an editor in Turin rebuilds and deploys static assets to Cloudflare Pages, Vercel, Netlify, or your own European Docker/Nginx infrastructure in seconds.
- If specific routes require live server-side execution, such as authenticated B2B dealer portals, real-time inventory lookups against an ERP (SAP, Zucchetti, TeamSystem), or gated technical downloads, I enable Astro’s hybrid rendering (
export const prerender = falseon those specific endpoints) while keeping 95%+ of the public site purely static.
Questions Piedmont teams ask before a Next.js to Astro cutover
How do I migrate a Turin automotive or aerospace documentation portal from Next.js without breaking technical PDF and CAD links?
I extract every legacy route, locale prefix, and static asset path from your Next.js repository before writing the Astro router. I generate deterministic 301 redirect rules and static asset mappings so deep links to specification sheets, ISO certificates, and CAD downloads continue resolving without 404 errors.
Can interactive 3D configurators or investor filters remain in React when the rest of a Turin platform moves to Astro?
Yes. Astro Island Architecture compiles product specifications, corporate news, and technical articles into zero-JavaScript HTML while isolating interactive React components into client:visible or client:idle islands that hydrate only when needed.
How does an Astro migration support Italian Garante cookie rules and Legge Stanca accessibility requirements?
Moving from client-side React rendering to static semantic HTML removes third-party runtime scripts that fire before consent under the Garante cookie guidelines of 10 June 2021, while clean DOM landmarks and native form controls support WCAG 2.1 AA targets referenced by AgID under Legge 4/2004 and D.Lgs. 82/2022 where that decree applies to your services.
When does AgID expect a private Piedmont company to file an accessibility statement after a WordPress to Astro cutover?
AgID states that D.Lgs. 82/2022 applies to private providers of the digital services listed in that decree, not every brochure site. During scoping I map your Turin routes against that list; where it applies, the Astro layout ships the dichiarazione di accessibilità link and monitoring hooks AgID describes for non-conforming services.
Can WordPress stay as the editorial backend while visitors see an Astro frontend for a Turin corporate site?
Yes. Editorial teams keep WordPress in the admin layer while Astro pulls typed content through REST API or WPGraphQL at build time. Webhooks trigger rebuilds when editors publish in Italian or English without exposing the wp-admin surface on the public hostname.
How do you keep Camera di Commercio di Torino REA and PEC fields consistent across Italian and English pages?
Art. 2250 Codice Civile fields live in a single schema-validated data module consumed by the Astro footer on every locale. Editors cannot accidentally drop the REA number or PEC address on the English investor section because the template renders the same legal block server-side on each route.
How I work: written-only remote collaboration
I am Mariusz Szatkowski, a solo WordPress and Astro developer in Gdynia who works directly with CTOs, lead engineers, and product managers in Turin without agency layers.
To keep engineering velocity high and maintain an unambiguous technical record, I work 100% remotely and exclusively in writing:
- No video calls, phone calls, or on-site workshops: Every architectural review, route mapping table, CMS schema contract, and pull request summary is documented clearly in writing (via email, GitHub/GitLab issues, or your written project tracker). Your developers in Turin can review every decision asynchronously without calendar disruptions.
- Design boundary: I do not create graphic designs from scratch. When your migration includes visual updates alongside the move to Astro, your team or design studio provides the Figma files, brand assets, or UI specifications, and I translate them into clean, accessible, high-performance Astro and React code. When it is a 1:1 architectural migration, I preserve your existing visual interface directly from your current Next.js CSS and component templates.
- Clear working-day communication: I reply to all messages and code review comments in writing on working days, delivering staging previews on every milestone so your team can inspect real HTML output, Lighthouse/Web Vitals metrics, and URL redirect matrices before anything touches production.
If your Turin platform is weighed down by Next.js hydration bundles, slow mobile responsiveness, or fragile App Router upgrades, send me your repository structure or current domain URL via the contact form, and I will prepare a written technical migration plan at no charge for the first written estimate.
Selected projects
Examples of my work.
E-commerce Development: like2slide.com
like2slide.com is a website for the ski, snowboard, and wakeboard community, built for inspiration, publishing, and stable operation.
E-commerce Development: marcoaldany.pl
marcoaldany.pl is a WordPress website built to present personalised services to show how this system can support companies offering personalised services or...
E-commerce Development: mavicon.pl
The website mavicon.pl has been designed with a view to providing a comprehensive presentation of the company’s offerings, which are based on innovative tech...
WordPress support & development in Turin
Need this service: Next.js / Astro migration in Turin?
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.