Website & application migration in Poznań
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 Poznań Community
Poznań companies usually ask about Astro or Next.js when a WordPress, Joomla or Drupal site has become slow to load, slow to edit or risky to update. Across Greater Poland (Wielkopolska), digital platforms support distinct export and B2B operations: trade-fair and conference portals connected to the Poznań International Fair (Międzynarodowe Targi Poznańskie, Grupa MTP) in Grunwald and Jeżyce, modern business services and software houses around Andersia and Garbary, and industrial, automotive and furniture manufacturers in Tarnowo Podgórne, Komorniki, Swarzędz and Września exporting along the A2 corridor to Berlin and Western Europe. I handle the technical migration end to end from Gdynia: the URL inventory, the typed content model, the 301 redirect map, the structured data parity, the staged cutover and the Search Console checks afterwards. This page explains how that engineering process runs, what Polish regulatory rules apply, and what to send me for a written scope.
Is migrating to Astro or Next.js worth it for a Poznań business?
Not always. If the slowness comes from a heavy page builder, an old theme or a dozen plugins loading scripts on every page, cleaning up the existing CMS costs less, and I say so in the written scope instead of proposing a rebuild. A migration earns its keep when the bottleneck sits in the architecture: an admin panel that times out while publishing multilingual trade-fair catalogues, security updates nobody dares to run before a major industry event at MTP, a frontend that cannot meet Google’s official Core Web Vitals thresholds (Largest Contentful Paint up to 2.5 seconds, Interaction to Next Paint up to 200 milliseconds, Cumulative Layout Shift up to 0.1) without fighting the theme, or a platform that has to serve Polish, German and English markets from one maintainable codebase.
The target framework follows your route requirements rather than industry hype:
- Astro fits content-driven and catalogue platforms: industrial product specifications, furniture and building-materials lookbooks, corporate investor portals, B2B lead-generation sites, technical documentation and multi-language marketing pages. Astro compiles templates to static HTML at build time and ships zero client-side JavaScript by default, hydrating interactive islands (such as a distributor locator, an RFQ drawer or a booth-booking calculator) only where the user interacts with them.
- Next.js fits when the application relies on authenticated dealer portals, live inventory and pricing feeds from SAP, Comarch ERP XL or Enova365, complex multi-step product configurators, or per-request server-side logic across dozens of dynamic routes.
- Hybrid routing is straightforward when you need both: Astro for the public SEO-critical pages and headless WordPress or a typed API backend for editors and dealers.
Why do Wielkopolska exporters and B2B companies outgrow monolithic templates?
In Poznań and the surrounding communes (gminy) of Tarnowo Podgórne, Dopiewo, Komorniki, Kórnik and Swarzędz, commercial websites rarely serve a single domestic audience. Greater Poland manufacturers and logistics operators sit directly on the Warsaw-Poznań-Berlin transport axis and generate a large share of their revenue from DACH, Benelux and Nordic buyers. Over five or six years, a typical monolithic WordPress or Drupal installation accumulates structural debt that plugin patches cannot resolve:
- Multilingual database bloat (
pl,de,en). When a manufacturer maintains 3,000 SKUs across Polish, German and English inside WPML or Polylang, every post-meta lookup multiplies table joins in MySQL. Moving the public presentation layer to Astro decouples database queries from visitor traffic: pages are built once during continuous integration or cached at the edge, so a sudden spike in traffic from a trade fair in Hanover or Poznań never touches the origin database. - Technical PDFs, CAD files and Declaration of Performance documents. Furniture, window, machinery and automotive-component producers host thousands of downloadable PDFs, BIM models and compliance sheets. Legacy CMS media folders (
wp-content/uploads/2021/...) are routinely linked inside printed catalogues, QR codes on exhibition stands and external distributor portals. If a relaunch changes those file paths without permanent edge-level 301 redirects, B2B buyers hit dead links immediately. - ERP and PIM synchronisation fragility. Many Wielkopolska businesses synchronise stock, technical parameters or B2B price lists from Comarch ERP Optima/XL, Subiekt GT/nexo, Symfonia or SAP Business One through brittle PHP cron jobs that lock the database during daytime traffic. In a headless Astro or Next.js architecture, ERP webhooks trigger isolated background builds or incremental cache revalidation without slowing down public page delivery.
How does the migration run, step by step?
I execute every migration as an engineering sequence where each phase produces a verifiable written deliverable before the next starts:
- Complete URL and asset inventory. I crawl the current production domain, export all XML sitemaps, extract historical indexed URLs from Google Search Console, pull landing pages with recorded sessions from analytics, and export backlink targets from Ahrefs or Majestic. Combining all five sources is the only way to catch orphan campaign pages, PDF datasheets and regional landing pages that a standard crawler misses.
- Typed content schema and Astro Content Collections. I map every legacy post type, custom taxonomy, ACF field group or Drupal paragraph into strict TypeScript and Zod schemas (
src/content/config.ts). If an editor forgets a mandatory German translation slug, a canonical path or a product specification unit, the build fails in CI with a clear error message instead of publishing a broken layout to production. - Line-by-line 301 redirect matrix. Every legacy URL gets a deterministic row in a version-controlled redirect specification: source path, query-parameter rule, destination path, HTTP status code (
301or410) and technical rationale. Unchanged URLs are explicitly listed so that path parity is tested automatically. - Metadata, canonical and JSON-LD parity. Titles, meta descriptions, canonical tags, Open Graph metadata and structured data (
Organization,LocalBusiness,Product,FAQPage,BreadcrumbList,JobPosting) are generated from the typed frontmatter and verified against the legacy HTML output. - Closed staging verification. I deploy the new frontend to a password-protected or
X-Robots-Tag: noindex, nofollowstaging environment. Before any DNS or edge cutover, I run an automated HTTP test suite against the entire redirect matrix and crawl the staging build to verify zero broken internal links and zero redirect chains. - Staged or atomic cutover. On large portals, edge routing rules (Cloudflare Workers or reverse-proxy path rules) shift traffic section by section, for example, moving
/de/or/produkty/first while legacy routes remain on the old server. On compact corporate sites, cutover runs as a single atomic switch with low DNS TTL. - Post-cutover Search Console and log monitoring. After launch, I monitor server access logs, Googlebot crawl stats, the Page Indexing report per language folder and Core Web Vitals field telemetry, fixing any unmapped legacy URLs that appear from external referrals.
Pre-cutover verification gates for Poznań migrations
Before switching production traffic, the staging build must pass six objective engineering checks:
| Verification gate | What I test on staging | Passing criterion before cutover |
|---|---|---|
| URL & PDF coverage | Union of crawl, XML sitemaps, GSC export, analytics landings and backlink targets | 100% of active URLs and PDF datasheets resolve with 200 OK or a single-hop 301 |
| Hreflang reciprocity | Bidirectional pl, de, en and x-default annotations in HTML <head> and sitemaps | Zero non-200 hreflang targets; every locale links to itself and all translated siblings |
| Structured data parity | Schema.org JSON-LD blocks compared route-by-route against the legacy site | Zero schema validation errors; Organization NIP/KRS and Product attributes preserved |
| Core Web Vitals lab & field readiness | Astro zero-JS baseline or Next.js Server Components payload inspection | Built to satisfy official web.dev thresholds (LCP <= 2.5 s, INP <= 200 ms, CLS <= 0.1) |
| Consent & PKE compliance | Network inspection of cold page load before any user interaction with the consent banner | Zero non-exempt marketing or analytics scripts or cookies fired prior to explicit opt-in |
| Form & CRM/ERP endpoints | End-to-end submission of RFQ, contact and career forms with validation and spam protection | Payloads delivered with HTTP 200/201, correct UTF-8 Polish diacritics and UODO processor disclosures |
How do I keep Google rankings when URLs change?
Google’s official documentation on site moves with URL changes asks for server-side permanent redirects (301 or 308) from each old URL to its specific new counterpart, confirms that permanent redirects pass ranking signals, and recommends keeping those redirects active for at least one year. I apply those rules strictly:
- Single-hop execution: If your Poznań site went through an earlier redesign in 2019 (
http://tohttps://, or/oferta.htmlto/oferta/), I flatten all historical hops so that the oldest backlink resolves to the final Astro or Next.js URL in one step. - No homepage catch-alls: Redirecting discontinued product pages or old trade-fair announcements to the homepage is treated by Google as a soft 404. If a page has a genuine successor, it receives a
301to that specific URL; if the content was permanently retired with no equivalent, it returns HTTP410 Goneso crawlers drop it cleanly from the index. - Preserving URL paths where possible: If your existing
/pl/,/de/and/en/URL structure is clean and well-indexed, the safest SEO decision is to keep the exact same URLs in Astro or Next.js. A framework migration does not require changing slugs just because the underlying template engine changed.
How should a Poznań site handle Polish, German and English versions?
Poznań is the capital of the Greater Poland Voivodeship, and the city’s Investor Relations Department (Biuro Obsługi Inwestorów) explicitly highlights modern business services, IT, research and development, and high-tech manufacturing as priority sectors, operating across English and German alongside Polish. Because Berlin is less than three hours away by rail or motorway, German (de-DE / de) is very often the primary export language for Poznań B2B companies, right beside English (en) and Polish (pl-PL).
When migrating a multilingual Poznań site, I replace fragile plugin-based translation tables with a deterministic locale architecture:
- Explicit locale routing: Each language lives in its own clean directory (
/pl/...,/de/...,/en/...) or dedicated country domain, configured directly in Astro’s i18n router or Next.js middleware. - Content-ID linking instead of slug guessing: A Polish slug like
/pl/automatyka-przemyslowa/and its German counterpart/de/industrieautomation/share a stabletranslationIdin frontmatter or the headless CMS. The build pipeline uses that ID to generate exact<link rel="alternate" hreflang="..." />tags and XML sitemapxhtml:linkblocks. - Strict locale formatting: Dates, number separators, metric units and statutory company notices are formatted per locale so that a German procurement manager in Brandenburg or Bavaria reads native DACH terminology while a Polish client sees proper Polish grammar and diacritics (
ą, ć, ę, ł, ń, ó, ś, ź, ż).
Which Polish and EU laws apply to a Poznań website after the move?
Rebuilding a corporate site or B2B store in Poland requires aligning the technical architecture with specific national statutes and supervisory authorities. I bake these technical controls into the templates before cutover:
1. Personal Data Protection Office (UODO) and GDPR (RODO)
In Poland, the Personal Data Protection Office (Urząd Ochrony Danych Osobowych, UODO) enforces the EU General Data Protection Regulation (RODO) alongside the Polish Act of 10 May 2018 on the Protection of Personal Data (Ustawa o ochronie danych osobowych). Moving from a monolithic PHP host to an edge-deployed Astro or Next.js stack changes your sub-processors (for example, Cloudflare, Vercel, Hetzner, AWS Frankfurt, or a transactional email API). Before launch, I deliver a complete technical register of every hosting region, CDN edge network, form handler and analytics endpoint so your legal counsel or Data Protection Officer (Inspektor Ochrony Danych, IOD) can update your Article 13 GDPR information clauses accurately.
2. Polish Electronic Communications Law (Prawo komunikacji elektronicznej, PKE)
On 10 November 2024, the Electronic Communications Law (Prawo komunikacji elektronicznej, Dz.U. 2024 poz. 1221) replaced the old Polish Telecommunications Law. Under the PKE (aligning with the ePrivacy regime supervised alongside the President of the Office of Electronic Communications, Prezes UKE, and UODO), storing information on or accessing information already stored in a subscriber’s or end-user’s terminal equipment (cookies, localStorage, tracking pixels) is permitted only after the user has been given clear information and has granted prior consent, unless the storage is strictly necessary for transmitting a communication or providing a service explicitly requested by the user. In Astro and Next.js, I wire third-party scripts (Google Tag Manager, Meta Pixel, LinkedIn Insight Tag, Hotjar) so they remain completely unexecuted until the consent state is explicitly granted, and I ensure the banner provides an equally prominent one-click rejection path.
3. Polish Accessibility Act (Polski Akt o Dostępności, PAD)
Poland transposed the European Accessibility Act (Directive 2019/882) through the Act of 26 April 2024 on Ensuring Compliance with Accessibility Requirements for Certain Products and Services by Economic Operators (Ustawa o zapewnianiu spełniania wymagań dostępności niektórych produktów i usług przez podmioty gospodarcze, Dz.U. 2024 poz. 731), enforced from 28 June 2025 under the supervision of the President of the Management Board of PFRON (Prezes Zarządu PFRON) and sector market surveillance authorities (including Prezes UKE). If your Poznań business provides consumer e-commerce services or digital booking/contract flows and exceeds the statutory microenterprise exemption (fewer than 10 employees and annual turnover or balance sheet total not exceeding EUR 2 million), your frontend must meet functional accessibility criteria mapped to EN 301 549 / WCAG 2.1 Level AA. Because a migration replaces every HTML template, I build semantic landmark hierarchy, full keyboard focus traversal, explicit <label> bindings, ARIA live error announcements and AA contrast ratios directly into the component library.
4. Commercial Companies Code (KSH), CEIDG and Omnibus / UOKiK transparency
Under Articles 206 and 374 of the Polish Commercial Companies Code (Kodeks spółek handlowych, KSH), commercial letters and company websites of limited liability companies (sp. z o.o.), simple joint-stock companies (P.S.A.) and joint-stock companies (S.A.) must display the company’s full registered name, registered office and address, the registry court where its documentation is kept, for Poznań entities, typically Sąd Rejonowy Poznań-Nowe Miasto i Wilda w Poznaniu, VIII Wydział Gospodarczy Krajowego Rejestru Sądowego, along with the KRS number, NIP (tax identification number), REGON, and the share capital (kapitał zakładowy, plus paid-up capital for S.A. and P.S.A.). Sole proprietors registered in CEIDG must identify their full name and NIP. If the site sells to consumers, the Office of Competition and Consumer Protection (Urząd Ochrony Konkurencji i Konsumentów, UOKiK) strictly enforces the Act on Consumer Rights (Ustawa o prawach konsumenta) and the Act on Informing about Prices of Goods and Services (Ustawa o informowaniu o cenach towarów i usług), including the Omnibus requirement to display the lowest price from the 30 days prior to any promotional discount. I build dedicated schema and UI fields for these statutory disclosures so they cannot be omitted on new landing pages.
How we work together remotely (and what I do not do)
I run WPPoland as a solo developer based in Gdynia. When you hire me for a Poznań migration, you deal directly with the engineer writing your Astro or Next.js code, configuring your redirect rules and checking your Search Console reports, never an account manager or a junior subcontractor.
To keep engineering work focused and predictable, I follow three clear working rules:
- Written, asynchronous communication only. I do not hold video calls, discovery meetings, daily stand-ups or phone consultations. Every audit, architectural proposal, redirect matrix and status update is delivered in writing by email or inside Git pull requests, and I send written replies on working days. That gives your Poznań management, marketing and IT staff a permanent written record they can review on their own schedule.
- Client-supplied visual design. I am a software engineer, not a graphic designer or branding agency. If you want a new look alongside the migration, your designer or creative agency supplies the Figma files, wireframes or visual guidelines, and I implement them in clean, accessible code. If you are happy with your current visual design, I port your existing layout directly into Astro or Next.js while stripping out the legacy page-builder bloat.
- Full code ownership at handover. You own the Git repository, the CI/CD deployment pipeline, the environment variables, the automated redirect test suite and a written operations guide covering how to publish content, preview branches and roll back a deployment. If you have in-house developers in Poznań, they receive a clean, standard TypeScript codebase with zero proprietary lock-in. For related engineering details, see my Next.js and Astro migration overview, headless CMS development and WordPress performance optimisation in Poznań.
How to start your Poznań migration scope
Send me a message via the contact page with your current website URL, the CMS or framework it runs on, the languages you publish in (pl, de, en or others), and any external integrations such as ERP, PIM, CRM or job boards. Tell me whether your URLs should stay identical or be restructured. I will review your setup and reply in writing on working days with a concrete migration scope, a risk assessment and the exact phases required for a clean cutover.
Selected projects
Examples of my work.
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...
E-commerce Development: radio.friko.pl
Radio.friko.pl is an internet radio station that operated between 2005 and 2010 as part of the Friko.pl platform, offering users access to music streaming, l...
WordPress support & development in Poznań
Need this service: Next.js / Astro migration in Poznań?
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.