Website & application migration in Antwerp
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.
Antwerp is the most populous municipality in Belgium, and its port ranks second in Europe after Rotterdam. Companies here often run websites that grew over ten years on WordPress, Joomla or Drupal, with a Dutch version, a French version and sometimes English for the port and logistics audience. When that stack gets slow, hard to update or risky to patch, a move to Astro or Next.js can fix it. This page explains how I run that move and what I check so search traffic survives it.
When does a migration to Astro or Next.js make sense for an Antwerp company?
It makes sense when the CMS itself is the problem, not a plugin or the hosting plan. Typical signs: pages that need a server round trip for content that changes once a month, an admin that editors avoid, plugin updates that break the theme, or a security patch schedule nobody keeps. If cleaning up plugins and adding a page cache would fix the issue, I say so and the migration does not happen.
Astro suits content sites: service pages, blogs, documentation, multilingual corporate sites. It ships static HTML by default and adds JavaScript only where a component needs it. Next.js suits sites with logins, dashboards, personalised content or heavy server rendering. Both can read content from a headless CMS, from Markdown in a repository, or from the old WordPress through its REST API during a transition.
What does the migration involve, step by step?
- URL inventory. I crawl the current site and export every indexable URL, plus the URLs that receive links or traffic according to your Search Console and analytics. Old redirects from previous redesigns go on the list too, because they often still carry backlinks.
- URL map. Each old URL gets one target: the same path, a new path with a 301, or a deliberate 410 when the content is gone for good. I keep this map in a spreadsheet you can read and in the redirect file the new host serves. No chains, no redirects to the homepage as a catch-all.
- Content model. I turn post types, custom fields, taxonomies and menus into typed collections. This is where hidden problems surface: shortcodes from a page builder, images stored inside HTML, translations linked by a plugin table rather than by an ID.
- Structured data. Organisation, breadcrumb, article, product or FAQ markup moves with the content and is generated from the same fields, so it cannot drift from the visible text.
- Languages and hreflang. Each page in Dutch, French or English carries hreflang links to all its translations and to itself. If you target Belgium specifically, I use nl-BE and fr-BE; if you target Dutch speakers in general, nl is enough. I generate these from the content model and test that every pair is reciprocal.
- Staging and parity checks. Before launch I compare old and new pages: title, meta description, canonical, H1, structured data and internal links. Differences are either fixed or written down as intended.
- Staged cutover. On larger sites the new frontend takes over one section at a time, with edge rules sending the rest to the old system. Small sites switch in one step.
- Search Console after launch. I submit the new sitemap, watch the coverage and page indexing reports, and inspect a sample of redirected URLs. If the domain or subdomain changes, I file a Change of Address request for every verified variant of the old domain, as Google’s site move guide describes.
What can go wrong, and how do I check for it?
- Lost URLs. A URL that existed and now returns 404 loses its links. I re-crawl the old URL list against the new site after launch and fix every 404 and every redirect chain.
- Language versions cut loose. If the French page redirects but the Dutch one does not, hreflang breaks and Google may show the wrong language. I check the hreflang reciprocity on the built HTML, not in the CMS.
- Redirects removed too early. Google’s guidance is to keep redirects for at least one year, and from a visitor’s point of view indefinitely. I leave them in place unless you decide otherwise.
- Forms and tracking that stop working. Contact forms, newsletter sign-ups and analytics often live in plugins. I list each one before the move and test it on staging with real submissions.
- Editors who cannot publish. A fast site nobody can update is a failure. Editors get the CMS or editing flow agreed at the start and a short walkthrough before cutover.
Which local rules affect a website in Antwerp?
Antwerp is in the Flemish Region, where Dutch is the official language. Belgium has three official languages, Dutch, French and German, and four language areas, so many Antwerp companies selling across the country publish in both Dutch and French. That makes the language structure of the site a core part of the migration, not an afterthought: URL prefixes, hreflang, language switcher and translated slugs all need a decision before content moves.
Personal data handled by the site, such as form submissions, analytics and newsletter lists, falls under the GDPR. In Belgium compliance is supervised by the Data Protection Authority (Gegevensbeschermingsautoriteit in Dutch, Autorité de protection des données in French). A migration is a good moment to list which scripts load on each page, which ones set cookies, and where form data goes, because the new stack only gets what you deliberately add back.
Hosting is a choice you make, not a default. Astro output can be served from a static host or a CDN; Next.js with server rendering needs a runtime. If your data handling requires EU hosting, I pick a provider and region that meet it and note it in the handover.
What do I hand over at the end?
You get the repository, the URL map, the redirect file, environment variables, the deploy pipeline and a short document describing how content is edited and published. Search Console and analytics stay in your account. If you want, I keep an eye on indexing and Core Web Vitals in the weeks after launch and fix what comes up.
More detail on the general process is on my Next.js and Astro migration page, and the Astro side is covered on the Astro developer page.
How do I start?
Send me the current site URL, the CMS and version it runs on, the languages it publishes in, and where your traffic comes from (organic search, ads, newsletters, referrals). Access to Search Console helps but is not required for the first look. I reply with a written scope: what moves, what changes, which URLs need redirects and which risks I see on your specific site.
Regulatory frame for projects in Antwerp
Antwerp sits under GDPR and Belgian APD/GBA. For Local SMB and Enterprise that means a processor agreement before first access to personal data, purpose logging on forms, and bounded log retention.
Antwerp gathers partners who already ask about GDPR, NIS2, EAA. The useful answer is a written runbook.
On a migration engagement we record hosting location, who administers WordPress, and what sits out of scope.
FAQ
Why are Antwerp port and logistics businesses migrating to Astro or Next.js?
Antwerp businesses operate in a competitive multilingual environment across Flanders, Wallonia, and international shipping corridors. Legacy CMS installations carrying heavy plugin stacks suffer from slow Time to First Byte (TTFB), high maintenance overhead, and security risks. Migrating to Astro replaces complex PHP execution with pre-compiled, static HTML and isolated islands of interactivity, resulting in sub-second mobile page loads, zero database vulnerabilities, and optimal Google Core Web Vitals.
How do you protect organic search traffic and search rankings during migration?
I perform an exhaustive crawl of every existing URL, metadata tag, canonical link, and image asset before modifying any code. Every legacy route is mapped 1:1 to its new equivalent or redirected using permanent HTTP 301 headers configured at the CDN edge. Complete Schema.org JSON-LD structured data (Organization, LocalBusiness, Article) is verified to safeguard rich snippets.
Can our marketing team continue managing content in their existing CMS?
Yes. We can decouple your architecture, keeping your familiar WordPress, Strapi, or Sanity installation as a headless content repository. Your marketing and editorial teams continue publishing content as usual, while Astro retrieves updates via REST or GraphQL APIs and compiles static pages within seconds via automated webhooks.
What Belgian and European regulations are incorporated into the migration?
Every migration strictly complies with the EU GDPR under Belgian Data Protection Authority (Gegevensbeschermingsautoriteit / APD-GBA) oversight, the Belgian Privacy Act of 30 July 2018, and European Accessibility Act mandates (EN 301 549 / WCAG 2.2 AA). All fonts and assets are hosted locally to eliminate unauthorized international data transfers.
What is the expected delivery timeframe for an Antwerp website migration?
A typical corporate replatforming covering 15 to 45 unique page templates, multilingual translations (Dutch, French, English), and custom forms spans approximately 3 to 5 working weeks from initial crawl analysis to production cutover.
Selected projects
Examples of my work.
E-commerce Development: jpg.pl
jpg.pl is an advanced hosting platform designed for secure storage, management, and distribution of images. The service is aimed at both individual users and...
E-commerce Development: kochamruch.pl
kochamruch.pl is a website for a community focused on movement and physical activity, with content publishing and stable technical foundations.
E-commerce Development: kredytywarszawa.pl
kredytywarszawa.pl is a WordPress website for a business offering loans and financial services, focused on clear services, performance, and basic security.
WordPress support & development in Antwerp
Need this service: Next.js / Astro migration in Antwerp?
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.