Migrating from Shopware 5 to 6: process, costs and pitfalls

Migrating from Shopware 5 to Shopware 6 isn't an update you click through in an afternoon – it's a rebuild of your shop on a modern technical foundation, and that's exactly why it needs to be planned properly. With us, a migration like this starts at €3,900. The most important reason to act now: Shopware 5 has had no official support and no security updates since the end of July 2024 – every month you stay on the old version is a growing security risk. In this article you'll get the full process, realistic costs, and the pitfalls that would otherwise cost you your Google rankings.

Why you shouldn't wait any longer to move from Shopware 5 to 6

"Shopware 5 end of support" isn't a distant threat anymore – it's been reality for a while. Shopware stopped developing Shopware 5 at the end of July 2024. Since then:

• No more security updates. Newly discovered vulnerabilities won't be patched by the vendor. For a shop that processes customer data and payment information, that's not just a technical problem – it quickly becomes a legal one (think GDPR).
• No bug fixes, no official support. If something goes wrong, you're on your own. There's no going back to the vendor.
• Plugin vendors are pulling out. More and more providers are discontinuing their Shopware 5 extensions. What still works today stops getting updates tomorrow – and at some point a payment or shipping integration simply breaks.
• Your environment ages along with it. Shopware 5 relies on outdated PHP versions. Once your host switches those off, your shop may not run at all.

There are commercial third parties still selling extended security updates for Shopware 5. But that's a bridge at best, not a destination – you're paying to keep a dead system artificially alive instead of investing in a foundation that will carry you for years. Migrate now and you do it calmly and on your own schedule. Wait, and you'll do it under pressure at some point, because something broke.

What fundamentally changes between Shopware 5 and 6

The most common misconception: "5 to 6, that's just one number up." In reality these are two completely different systems. Shopware 6 was rebuilt from the ground up. You should understand that before you try to estimate the cost:

• New architecture. Shopware 6 is built on the Symfony framework and an API-first structure. The frontend (the "storefront") and the backend are cleanly separated. That makes the shop faster, more flexible and more future-proof – but also fundamentally different under the hood.
• Plugins are not compatible. Not a single Shopware 5 plugin runs in Shopware 6. For every extension you use today, you need either the matching Shopware 6 counterpart or a custom rebuild. That's one of the biggest cost drivers – and the point where quotes start to diverge wildly.
• The theme has to be rebuilt. Shopware 6 uses Twig and Bootstrap, a different templating stack than Shopware 5 with Smarty. Your old design can't be carried over; it gets rebuilt on the new foundation or rethought from scratch.
• Different data structure. Products, categories, customers and orders sit differently in the database in Shopware 6. That's why moving your data is a real migration with mapping – not a simple export/import.

In short: you're not moving house, you're building a new one – with your data and your knowledge as the foundation. That sounds like a lot, but it's also a chance to shed old baggage. The same logic sits behind every larger legacy replacement, by the way – it's a big part of what our custom software work is about.

How a clean migration works, step by step

A Shopware 6 migration done by gut feeling almost always ends in chaos. That's why we work in clear stages in our projects. Here's what the process looks like:

1. Analysis and inventory

First we look at what you actually have: how many products, variants and categories? Which plugins are in use – and which of them do you even still need? Which integrations are attached (ERP, shipping, payment, accounting)? And which pages currently bring you traffic and revenue? This analysis determines the entire scope of work. A shop with 300 products and three standard plugins is a different world from a B2B shop with 20,000 items and an ERP connection.

2. Test migration in a protected environment

Nothing goes straight live. We set up Shopware 6 in parallel on a separate environment and run a first test migration of your data there. That way everyone involved sees early on what the new shop looks like and where it snags – without touching your live shop.

3. Setting plugins and features back up

Now it's on to functionality. For every plugin you need, we clarify: is there a suitable Shopware 6 plugin, does a built-in feature replace the old one, or do we have to build a custom extension? This is where the wheat separates from the chaff – because shops often drag along plugins for years that nobody needs anymore. Those we simply drop.

4. Theme and design

Your design gets implemented on the new storefront stack. You can have your existing look rebuilt as closely as possible, or use the move for a fresh, faster appearance. What matters is that the pages with the most important URLs stay intact – more on that in a second.

5. Data migration with reconciliation

Only once the foundation is in place do we migrate the real data properly: products, customers, order history, prices. After that we reconcile rather than hope – do item counts, customer counts and totals match before and after? Only when the numbers line up is this step done.

6. SEO move with redirects

This is the step most people underestimate – and the one that decides your revenue after go-live. Shopware 6 partly generates different URL structures than Shopware 5. For every old URL that has rankings or backlinks, you need a 301 redirect to the matching new address. We build a complete redirect map for that, so neither Google nor your customers run into dead ends.

7. Go-live and follow-up checks

Finally we switch the new shop live – ideally at a low-revenue moment. And that's not the end of it: we keep a close eye on the checkout process, payment methods, redirects and Google indexing during the first few days, so anything odd gets caught immediately.

What happens to your Google rankings – and how to protect them

The most legitimate fear in any shop migration: "will I lose my rankings?" The honest answer: with a badly executed migration, yes; with a clean one, no. Google doesn't drop your positions because you switch systems – it drops them because URLs disappear, load times explode or content goes missing.

These three levers protect your visibility:

1. Complete 301 redirects. Every old URL points to its new target via a permanent redirect. That way the authority a page has built up carries over to the new address.
2. Bring your content and metadata along. Product copy, category copy, title tags and meta descriptions all need to come with you. Lose half your descriptions during the migration and you lose rankings too.
3. Use the technology instead of wasting it. Shopware 6 is faster than Shopware 5 out of the box. A good migration turns that into better Core Web Vitals – a ranking factor you get for free if you do it right.

A short, controlled "dip" right after go-live is normal – Google has to crawl the new shop first. After two to four weeks, positions should have recovered. How to get Shopware in shape for search engines beyond that, we've covered in detail in our article on Shopware SEO.

Typical pitfalls in a Shopware 6 migration

We see these mistakes over and over in practice – and every one of them costs unnecessary money or revenue:

• No redirect plan. The classic. The new shop looks great, but half the old URLs land on a 404 page. Rankings gone, ad links dead.
• Trying to rebuild everything 1:1. The migration is the perfect opportunity to get rid of unused plugins and tangled processes. Copy everything over stubbornly and you're paying for baggage.
• Underestimating integrations. ERP systems, shipping providers and payment providers often sit deeper in the system than you'd think. Those dependencies belong on the table very early, not at go-live.
• Not testing enough. If you don't check the checkout process with real test purchases across every payment method, you'll find out the payment is broken from your first real customer.
• Going live without a buffer. A go-live on a Friday afternoon before the weekend is an invitation for trouble. Plan the switchover with time for follow-up checks.

How long does a migration really take?

That depends heavily on size and complexity, but as a rough guide: a manageable shop with standard features and clean data is realistically migrated in four to eight weeks. Add lots of custom plugins, deep ERP integrations or an elaborate custom design and you should plan for three to six months. The biggest time sink is almost never moving the data itself – it's rebuilding the features that don't exist 1:1 in Shopware 6. That's exactly why analysis comes first for us: so you get a number you can rely on and no nasty surprises.

Migrate, or rebuild from scratch?

A question almost everyone asks us: "is the migration even worth it, or should I just build new?" The answer depends on the state of your current shop.

A real migration makes sense if your Shopware 5 shop works well at its core, you're happy with the structure and product range, and above all you want to bring along a lot of order history, customer data and hard-earned rankings. Then moving is the right, cheaper path.

A fresh start makes sense if your shop has grown organically over the years and become unwieldy, nobody can keep track of all the plugins anymore, or the design is showing its age regardless. Then it's often smarter to bring the data over cleanly but rethink the structure and features from scratch.

In practice the truth is usually a mix: we bring over what's valuable (data, URLs, proven processes) and deliberately leave behind what was just baggage. That's exactly what we clarify in the analysis at the start – honestly, so you don't pay for things that get you nowhere.

What does migrating to Shopware 6 cost?

Concrete numbers instead of "it depends" – here's how our pricing works:

• Migration from €3,900 – for a clean move to Shopware 6 with data transfer, a redirect plan and a working standard shop.
• Shop expansion from €11,900 – if you want to use the migration for custom features, your own plugins, a tailor-made design or deep integrations.
• Ongoing support from €199/month – for updates, security, monitoring and a real contact person, so the end-of-life issue never catches you again.

These numbers are honest starting points, not headline prices with asterisks. What your project actually costs depends on your product range, your plugins and your integrations – which is why you always get a real assessment from us before you decide. You'll find an overview of our packages on our pricing page, and you can read up on what's behind our Shopware development in detail there.

Bottom line: turn the obligation into an opportunity

Shopware 5 is at the end of its life cycle – it's not a question of whether you migrate, but when. The good news: a clean migration to Shopware 6 isn't a necessary evil, it's the chance to get a faster, safer, future-proof shop that belongs to you again and grows with you. What matters is getting the analysis, the data and above all the SEO move with redirects right – then you keep your rankings and gain technically on top.

Still on Shopware 5 and wondering what the move would mean for you? Let's take a look at your shop together in a free initial consultation – we'll tell you honestly how much work your migration really is, what it costs, and how we'll protect your visibility along the way. No obligation, no sales pressure, straight talk.