Use this Shopware 5 → 6 migration checklist to protect SEO rankings, reduce go-live risk, and launch with a controlled cutover plan. Built for DACH/EU stores (Germany, Austria, Switzerland) with multilingual and B2B requirements.
Want us to sanity-check your redirect map and launch plan?
Get a migration audit
The safest Shopware 5 → 6 migration is a parallel build: set up Shopware 6 in staging, migrate data using Migration Assistant + Migration Connector, map every URL, deploy 301 redirects, validate canonicals/hreflang/sitemaps, then execute a staged cutover (blue-green or canary) with a final delta migration and strict monitoring.
Why Shopware 5 to 6 migration matters (especially for DACH/EU)
Shopware 5 has reached end-of-life. Shopware states Shopware 5 development was discontinued at the end of July 2024. If you're still on Shopware 5, you face growing security and compatibility risk over time. Shopware 5 end-of-life (official)
Shopware 6 is not a direct upgrade. Plan it as a relaunch with staged migration, testing, and a controlled go-live. Official migration overview (Shopware docs)
Pre-migration checklist (do this before you migrate anything)
- Inventory your current store: plugins, theme overrides, custom modules, payments/shipping, ERP/PIM, tracking, cron jobs.
- Baseline SEO: export top landing pages, categories, products, rankings, organic sessions, crawl errors, CWV.
- Freeze launch scope: must-have for go-live vs phase 2 backlog.
- Rollback plan: define exactly how you revert traffic if checkout breaks or 404 spikes.
Related reading: Shopware 6 performance optimization guide
Step 1: Check Shopware 6 system requirements
Before installation, confirm your server meets Shopware 6 requirements. Shopware 6 system requirements (official)
- Staging parity: staging should match production versions and services as closely as possible.
- Performance readiness: cache, PHP settings, DB tuning, image pipeline, and your search stack.
Step 2: Install Shopware 6 (parallel environment)
Install Shopware 6 as a clean, parallel environment so you can migrate, test, and validate SEO before go-live. Shopware 6 installation guide (official)
Step 3: Install migration tooling (Shopware 5 + Shopware 6)
- Shopware 5: install Migration Connector
- Shopware 6: install Migration Assistant
Then create the connection in Shopware 6 Admin under Settings → Migration. Migration process and connection setup (official)
Step 4–6: Connection, data selection, migrate, repeat until clean
- Create connection: choose correct profile and gateway (API vs local DB).
- Select datasets: products, categories, customers, orders, media, languages, sales channels.
- Run migration: fix assignment issues, rerun until stable, then plan final delta migration for go-live.
SEO-safe migration checklist (the ranking protection layer)
1) URL mapping + 301 redirects
- Export all indexable URLs from Shopware 5 (categories, products, CMS pages).
- Create a complete URL map: old → new (one-to-one wherever possible).
- Deploy 301 redirects for all changed URLs and avoid redirect chains.
2) Metadata + internal linking parity
- Preserve titles/meta descriptions for top pages (improve after stability).
- Keep key content blocks and internal links consistent on high-traffic pages.
3) Indexation control (canonicals, facets, robots)
- Validate canonicals on category and product pages.
- Prevent filter/sort URLs from being indexed (index bloat kills crawl budget).
- Block staging from indexing; verify production is crawlable.
4) GEO: multilingual + hreflang for DACH
- Validate hreflang for DE/EN (and de-DE / de-AT / de-CH if relevant).
- Ensure localized shipping/returns/payment/legal pages match target countries.
Most post-migration traffic drops happen because of missing 301 redirects, indexation mistakes, faceted URL bloat, broken canonicals, and performance regressions on category and product pages. If you want a clean go-live with SEO and revenue protected, our Shopware team can audit everything before you switch traffic.
Typical deliverables: URL map + redirect rules review, canonical & robots validation, sitemap + Search Console checks, facet index control, CWV performance fixes, checkout QA, and a launch readiness report.
Near-zero downtime go-live plan (controlled cutover)
“Zero downtime” usually means a controlled cutover window with staged routing and a final delta migration. The goal is to avoid prolonged outages and prevent revenue loss from broken checkout or missing redirects.
- Traffic staging: blue-green or canary routing when possible.
- Final delta migration: sync last changes (orders/customers/products) before switching traffic.
- Cache warmup: pre-warm key categories and PDPs.
- Rollback triggers: define abort thresholds and revert steps.
Post-launch checklist (first 72 hours)
- Fix 404s fast: missing redirects are your #1 ranking drop cause.
- Search Console monitoring: coverage, sitemap processing, URL inspection for top pages.
- Checkout validation: payment callbacks, tax/VAT, shipping rules, emails, order capture.
- Performance checks: verify CWV on listing and product templates.
If you want this handled end-to-end, see: Hire Shopware developers or Shopware 5 to 6 migration service .
FAQ
Can I directly upgrade from Shopware 5 to Shopware 6?
No. Shopware 6 is typically implemented as a new installation and your Shopware 5 data is migrated using migration tooling and a structured relaunch plan.
Will I lose SEO rankings after migrating to Shopware 6?
You don’t have to. Rankings are protected by a complete URL map, 301 redirects, metadata parity on top pages, canonical validation, and post-launch Search Console monitoring.
What’s the #1 reason Shopware migrations lose traffic?
Missing or incorrect redirects. 404 spikes and redirect chains are the fastest way to lose indexation and rankings.
How do I migrate with near-zero downtime?
Build Shopware 6 in parallel, run repeatable migrations in staging, then perform a staged cutover (blue-green/canary where possible) with a final delta migration and a defined rollback plan.
Do I need to rebuild my theme and plugins for Shopware 6?
Often yes. Many Shopware 5 plugins/themes don’t have a one-to-one match in Shopware 6. Audit your plugin list early and plan replacements or custom development.
What data can be migrated from Shopware 5 to Shopware 6?
Commonly migrated data includes products, categories, customers, orders, and media. The exact coverage depends on your setup and extensions, so validate results in staging after each run.
How long does a Shopware 5 to 6 migration take?
It depends on catalog size, customizations, integrations (ERP/PIM), and storefront complexity. The fastest projects enforce a strict launch scope and push enhancements into Phase 2.
What should DACH/EU stores double-check before launch?
VAT and tax rules, customer groups (B2B), multilingual routing and hreflang, consent/cookie setup, and localized legal pages (imprint, privacy, returns, shipping, payments).
Need a Shopware migration checklist review?
We’ll review your URL map, redirect plan, plugin/theme risks, and go-live steps before you touch production.