Shopware 5 to 6 migration: a step-by-step guide

Shopware 5 has not received security updates since July 2024. For many online shop operators this means migrating to Shopware 6 is no longer a question of if, but when. The move is not a one-click update, because Shopware 6 was rebuilt from scratch on an entirely different architecture.

This guide walks you through the migration step by step: how to prepare, how to transfer your data, and how to keep your SEO intact without losing data. Whether you plan to migrate on your own or with an agency, you will find the key steps here.

1. Why you shouldn’t wait to migrate from Shopware 5 to Shopware 6

Shopware 5 was a reliable platform for German e-commerce for many years. Since its official end of life in July 2024, however, there are no more security patches or compatibility updates. The consequences:

• Known security vulnerabilities remain unpatched, which puts you and your customers at risk
• Current PHP versions and databases are no longer supported
• Plugin developers are discontinuing support for Shopware 5
• Shopware no longer provides official support
• Newer features like Flow Builder, AI Copilot or Shopping Experiences are not available

Shopware 6, on the other hand, brings an API-first architecture, the Rule Builder for flexible business logic, native Shopping Experiences and headless capabilities.

Tip: If you treat the migration as a mandatory chore, you miss an opportunity. Use the move to rework your shop design, category structure and conversion strategy.

2. Shopware 5 vs. Shopware 6: what’s different?

Before planning your migration, it helps to understand why this is not a typical update. Shopware 6 shares neither code nor database structure with its predecessor. The key differences:

Framework and technology

Shopware 5 is based on the Enlight/Zend framework with Smarty templates and an ExtJS administration. Shopware 6 uses Symfony 5+, Twig templates with Bootstrap 5 in the frontend, and a new admin interface based on Vue.js.

API and flexibility

Shopware 5 offered limited API capabilities, while Shopware 6 follows a strict API-first approach. The Admin API and the Store API allow full control of the shop via interfaces. This is the foundation for headless commerce and modern integrations.

Content and automation

The old “Shopping Worlds” are now called “Shopping Experiences” and can do considerably more. In addition, the Flow Builder automates processes and the Rule Builder handles flexible business rules, features that used to require expensive custom development.

Shopware licensing model

The old model with Community, Professional and Enterprise editions has been replaced. Shopware 6 offers a free Community Edition and paid plans (Rise, Evolve, Beyond) with different feature sets.

So there is no simple update. Shopware 6 is set up as a new installation, and the data is transferred with the official Migration Assistant.

3. Phase 1: Preparation and analysis

Careful preparation pays off. Cutting corners here costs you later through data loss, SEO drops or unexpected expenses.

Audit your Shopware 5 store

Document your current setup:

• How many products, categories and orders do you have?
• Which plugins are in use? Are there Shopware 6 equivalents?
• How complex is your theme? What customizations exist?
• Which integrations (ERP, payment providers, etc.) are connected?
• Are there custom fields that need manual mapping?

Check plugin compatibility

Shopware provides a migration assistant that shows the status of each plugin:

1. Successor available: a Shopware 6 version exists
2. Successor planned: a release date has been announced
3. No successor planned: you need an alternative or custom development

Important: Check critical plugins early. If replacements are missing, plan custom solutions in advance.

Document your SEO status

SEO is one of the most sensitive parts of the migration:

• Export indexed URLs from Google Search Console
• Document meta titles, descriptions and canonicals
• Run a full crawl (e.g. Screaming Frog)
• Identify top landing pages and rankings
• Review existing 301 redirects
• Keep in mind that image URLs will change

Budget and timeline

The effort depends on complexity:

• Simple shop: €3,000–9,000, about 4–10 weeks
• Mid-sized shop: €10,000–40,000, about 3–6 months
• Complex shop: €40,000–100,000+, about 6–12 months

4. Phase 2: Data migration

Shopware provides a Migration Assistant to transfer the core data.

Preparation in Shopware 5

1. Make sure you run version 5.4 or higher
2. Install the Migration Connector
3. Reload the backend
4. Create API credentials

Setting up Shopware 6

1. Install a fresh Shopware 6 (staging)
2. Install the Migration Assistant
3. Connect both systems via API

Data migrated automatically

• Products, categories, customers, orders
• Manufacturers, media, SEO URLs
• Newsletter subscribers, reviews

Manual migration required

• Theme and design
• Shopping Experiences
• Static pages
• Custom fields and plugin data
• Shipping rules and integrations

Tip: Run the migration several times in staging to keep the data up to date.

5. When the Migration Assistant reaches its limits

In practice, problems come up regularly:

Missing orders

Older or plugin-based orders may not transfer correctly. We use custom scripts to recover them.

Customer data issues

Missing accounts or broken logins are common. Data reconciliation tools help fix this.

Product inconsistencies

Variants, pricing and custom fields often cause issues. These can be fixed with adjustments at database level.

Our tooling

We have built internal tools for these issues, so fixes often take hours instead of days.

6. Phase 3: Theme and design

Shopware 5 themes are not compatible. Your options:

1. Customize the standard storefront
2. Build a custom theme
3. Go headless (Vue/React/Next.js)

7. Phase 4: SEO migration

This phase decides whether you keep your rankings.

URLs

Keep the URL structure if possible, otherwise set up redirects.

301 redirects

Make sure every old URL redirects to the right new one.

Monitoring

Track crawl errors and rankings after launch.

8. Phase 5: Go-live

The checklist includes testing payments, integrations, performance and redirects.

9. Common mistakes

• Missing redirects
• Insufficient testing
• Ignoring plugin compatibility
• Copying the old shop instead of improving it
• No staging environment

10. Conclusion

Migrating to Shopware 6 takes effort, and it is also a good moment to improve your shop.

Planning your migration? We support you from the initial analysis to go-live. Get in touch with us if you would like to discuss your project.