Shopware 5 to 6 migration: a replatforming, not an update

And it is not an update. Shopware 6 shares nothing with Shopware 5 — not the database structure, not the templating engine, not the plugin architecture. What transfers is data. Everything else gets rebuilt.

This article walks you through the signs that tell you a switch is overdue, what a migration project realistically looks like, and where projects lose money and rankings. The methodology behind it is laid out across 188 pages in our free Replatforming Guide; we link the relevant sections where they fit. Merchants migrating from Magento or OXID should read the dedicated articles for those platforms — the pitfalls are different.

What this article covers

• Six signs your Shopware 5 shop needs to go, and what Shopware 6 changes about them

• What the Migration Assistant handles and what you rebuild from scratch

• The Shopware 5 specifics: plugins, Smarty, Shopping Experiences, customer groups

• The six-phase process, including trial migration and testing

Six signs the switch is overdue

Your system is end of life. No patches means every new vulnerability stays open. Attackers actively scan for EOL software, and your insurer will ask about your patch status when a claim comes in.

Every update has become a project. When plugin dependencies hold back releases for months, the shop has lost its maintainability.

Integrations are permanent construction sites. ERP sync by CSV and cron job, manual clean-up on prices or stock levels.

Business logic lives in the code. Every flow, every shipping rule, every customer group requires a developer.

B2B features are missing. Approvals, budgets, quotes, and customer-specific catalogues are handled outside the shop.

Performance and compliance are falling behind. Core Web Vitals, the accessibility requirements of the European Accessibility Act, and modern payment standards can no longer be solved cleanly in the old system.

The full checklist with scoring criteria is in Guide, section 2.1. Shopware 6 addresses these points at the structural level: Rule Builder and Flow Builder move business logic out of the code and into the admin, the API-first architecture makes integrations the default rather than the exception, B2B Components from Evolve upwards cover the standard B2B workflows, and Shopware 6.7 is built to meet EAA accessibility requirements.

Why it is not an update

Shopware 6 is a ground-up rebuild on Symfony and Vue.js. Smarty templates do not run in Twig, Shopware 5 plugins are incompatible, and the database structure is entirely different. Shopware itself uses the word "migration" and provides the Migration Assistant for the task, with profiles for Shopware 5 from version 5.4 onwards, one profile per minor version.

The Assistant transfers products, categories, manufacturers, customers, orders, media, and reviews. It reads the Shopware 5 database through the Migration Connector; the old shop stays live and unchanged until cutover, and changes can be re-migrated in the meantime. Themes, plugins, custom code, and integrations are not carried over.

The Shopware 5 specifics that drive the effort

Plugins. The inventory audit is the single most important step. Many Shopware 5 plugins have Store equivalents for Shopware 6; some core functions (volume pricing, customer groups, shipping rules) are covered by the Rule Builder; and a remainder has no equivalent at all. That remainder determines the budget.

Templates. Smarty themes are not converted. The frontend is a full rebuild in Twig, or, if you have headless ambitions, with the Composable Frontends. This is the moment to clear out ten years of accumulated theme customisations.

Shopping Experiences. Shopping Worlds from Shopware 5 become Shopping Experiences in Shopware 6. The content cannot be transferred automatically; layouts must be rebuilt — usually fewer than you had before.

Customer groups and pricing. Shopware 5 customer groups with their own prices and discounts map to customer groups, advanced prices, and the Rule Builder in Shopware 6. The logic is more powerful, but it is structured differently — copying it one-to-one throws away the advantage.

SEO URLs. Shopware 6 uses a different default URL structure. Without a complete 301 redirect map, rankings will be lost. That map is its own work package, not a single item on a go-live checklist.

The six-phase process

1. Analysis and audit. Plugins, custom code, integrations, data quality. This inventory determines the budget and timeline.

2. Target architecture. Edition, hosting model, integration patterns, theme strategy. This is also where you decide what consciously will not be migrated.

3. Trial migration. A full run of the Migration Assistant into a closed staging environment. Result: a data quality report and a list of mapping gaps. The approach is in Guide, section 4.4.

4. Build. Theme, custom features, and integrations in parallel. Integrations go first because they take longest and involve external stakeholders.

5. Testing. Integration tests per interface against real data, end-to-end tests of the checkout flow per customer group and payment method, data reconciliation between old and new, load test before cutover. Skip this phase and the customer finds the bugs. Test plans and go-live agenda as templates: Guide, sections 5.5 to 5.7.

6. Cutover and hypercare. Content freeze, final delta migration, 301 redirects live, DNS switch, two to four weeks of heightened availability.

What the migration costs and how long it takes

The biggest cost item is rarely the licence. It is data migration and the rebuild of custom plugins and integrations. A Shopware 5 migration for a mid-sized shop runs three to six months including the test phase and parallel operation; projects with B2B features and ERP integration take longer. Market sources put the cost of pure data migration at €5,000 to €30,000, and €2,000 to €15,000 per integration (qualimero, May 2026). That is a reference range, not a quote.

From practice: where projects fail

First, the audit: plugins nobody remembers until they are missing. Second, data: variants without clean assignments, customers with duplicates, order history without unique keys. Third, testing: projects that cut the load test learn about it on the first peak trading day. Fourth, the organisation: the ERP owner was not scheduled in, the integration is waiting.

Recommendations

1. Have the plugin and integration audit done before any quote is written.

2. Budget the trial migration as a standalone phase with a data quality report.

3. Don't migrate everything — strip out legacy baggage before it becomes Shopware 6 code.

4. Budget testing (integration, end-to-end, load, data reconciliation) as a mandatory phase.

5. Manage the 301 redirect map as its own work package with a named owner.

Conclusion

A Shopware 5 to 6 migration is a replatforming: data moves, everything else is rebuilt. Plan it as an update and you are already underbidding the project.

For decision-makers, the switch is a chance to pull business logic out of the code and standardise integrations. That only works if the project is structured so that the audit, trial migration, and testing are real phases with real time.

Shopware 6.7 is the current target version; 6.8 arrives in 2027 with the end of the legacy B2B Suite. Migrate today and you build on B2B Components, not on something legacy.

If you are facing this decision, we work through the audit with you. As a Shopware agency, we have guided Shopware 5 shops through migrations in both directions — and we know the plugins nobody will miss.

FAQ

Can I still run Shopware 5 in 2026?

Technically yes, officially secured no. Security patches ended on 31 July 2024. Every day of operation after that is a deliberate risk decision with potential liability consequences.

What does the Shopware Migration Assistant transfer?

Products, categories, manufacturers, customers, orders, media, and reviews from Shopware 5 version 5.4 and above. Themes, plugins, custom code, and integrations are not transferred.

How long does a Shopware 5 to 6 migration take?

For a mid-sized shop, three to six months including the trial migration and parallel operation. Longer with B2B features and ERP integration.

Can I do the migration myself?

The data transfer, yes — the Migration Assistant is built for that. Frontend rebuild, plugin replacement, integrations, and testing require development capacity. Most merchants bring in an agency for those.

How do I protect my rankings during the migration?

With a complete 301 redirect map covering all old URLs to their new equivalents, activated at cutover, and close monitoring of Search Console for the following weeks.