Quick Answer
Shopware 5 hit end of life back in July 2024. No more security patches. Plugin support is thinning out fast. If your store still runs on it, this guide is for you. We go through the entire Shopware migration from SW5 to SW6: what actually moves over, what you’ll have to rebuild, ballpark costs, and how to keep your Google rankings intact while switching.
Why This Shopware 6 Migration Can’t Wait Any Longer
Here’s the situation. Shopware officially pulled the plug on Shopware 5 support back in July 2024. That means no more security patches, no more bug fixes, and the plugin marketplace is slowly drying up. If you’re still running your store on SW5, every month you wait adds more risk. We’ve seen stores get hit with vulnerabilities that would’ve been patched in a week on Shopware 6. It happened to a client of ours last year, and the cleanup wasn’t cheap.
The tricky part? This Shopware migration isn’t like hitting an update button on WordPress. Not even close. Shopware 6 runs on a totally different database, a different frontend stack, and a plugin system that shares almost nothing with version 5. Imagine packing up your entire apartment and moving to a building with different sized rooms and different shaped doorways. If you rush that move, boxes get lost. Except here the “boxes” are your Google rankings, your customer records, and years of order history.
This guide breaks down exactly how to handle the Shopware 5 to Shopware 6 migration without torching anything important along the way. Which data actually makes the trip? Where do people mess up? What’s the damage to your wallet going to look like? And how do you keep Google from penalizing you mid switch? All of that is in here. If you’ve got real revenue riding on your store, don’t skim this one.
Already know you need expert help? Our Shopware development services team has handled these migrations end to end. But let’s walk through the process first.
What Actually Changed Between Shopware 5 and 6
People keep calling this an “upgrade” and that’s misleading. Shopware 6 was rewritten from the ground up. Different architecture, different frontend stack, different everything. You can’t just click update and hope for the best. Here’s what’s different:
| Feature | Shopware 5 | Shopware 6 |
|---|---|---|
| Architecture | Monolithic PHP | API first, Symfony framework |
| Frontend Templates | Smarty (.tpl files) | Twig + Vue.js |
| Content Management | Shopping Worlds | Shopping Experiences (drag and drop) |
| Plugin System | Legacy extension model | Modern app system with Shopware Store |
| B2B Features | Limited, needed add ons | Native B2B components built in |
| Multi Language / Currency | Basic, clunky setup | Built in, scales cleanly |
| Security Updates | Ended July 2024 | Active development, regular patches |
| Hosting | Self managed servers | Cloud, PaaS, or self hosted options |
The bottom line: your old Smarty templates won’t work. Your old plugins probably won’t work. And the data structure underneath has changed enough that you can’t just copy paste a database. That’s why a proper migration plan matters so much.
What Data Migrates and What Doesn’t during shopware 6 upgrade
This is the question everyone asks first. And the honest answer is: some things move over cleanly, some need manual work, and some have to be rebuilt from scratch. Shopware’s Migration Assistant handles the standard stuff. Everything else? That’s on you or your agency.
| Data Type | Transfers Automatically | Needs Manual Work |
|---|---|---|
| Products + Variants | ✅ Yes | — |
| Customer Accounts | ✅ Yes | Passwords require reset |
| Order History | ✅ Yes | — |
| Categories | ✅ Yes | May need restructuring |
| SEO URLs + Metadata | ⚠️ Partial | 301 redirects must be set up manually |
| Shopping Worlds | ❌ No | Rebuild as Shopping Experiences |
| Custom Plugins | ❌ No | Rebuild or find SW6 alternatives |
| Themes / Templates | ❌ No | Complete rebuild (Smarty to Twig) |
| Media Files | ✅ Yes | Clean up dead files before migrating |
| Custom Fields | ⚠️ Partial | Manual mapping for complex fields |
| Newsletter Recipients | ✅ Yes | — |
| Product Reviews | ✅ Yes | — |
Here’s something that surprises almost everyone: you can’t bring customer passwords over. SW5 and SW6 hash them in completely different ways, and there’s no workaround. So after the switch, every customer has to reset their password on the first login.
Sounds bad, right? It’s actually fine if you handle it well. Send out a heads up email beforehand, set up an automated reset flow, and most people won’t even complain.
The Shopware Migration Process, Step by Step
After going through a bunch of these projects, one thing became really obvious. The actual migration? That’s maybe a fifth of the total effort. Everything else is prep work, scrubbing your data, and then testing until your eyes glaze over. People who skip the boring parts end up paying double after launch. Anyway, here’s how we approach it:
Step 1: Audit Everything in Your Current Store
Don’t touch a single thing until you’ve written down what’s in your store right now. Product count, which plugins you’re running, any custom PHP that someone bolted on three years ago. Pull up your URL structure and screenshot it. Got an ERP connection? PIM? Payment gateway? Write every single integration point down. Think of this document as your moving manifest. Without it you’re basically tossing stuff into boxes with no labels.
Step 2: Set Up Shopware 6 in a Staging Environment
Spin up a fresh Shopware 6 install on a staging server. Keep your live SW5 shop running like nothing’s happening. Customers keep shopping, orders keep flowing. Meanwhile, on the Shopware 5 side you install the Migration Connector plugin, and on the SW6 side you install the Migration Assistant. That’s what connects the two systems and lets them talk to each other during the transfer.
Step 3: Clean Your Data Before You Move It
Nobody wants to do this part but it matters more than people think. You’ve probably got dead products sitting in your catalog. Duplicate customer entries from that one import you did in 2019. Categories that don’t lead anywhere. Bloated media files nobody downloads. Leave all of that behind. Go through your catalog, kill what’s dead, standardize your attributes, and toss anything you haven’t touched in two years. You’re moving to a new house. Don’t bring the junk drawer.
Step 4: Run the Migration Assistant
Now you’re ready to actually move data. Open up the Shopware 6 admin panel, go to Settings > Migration, and let the assistant walk you through importing your products, customers, orders, media, and categories. It does this in batches. Works fine for most stores. But if you’ve got a monster catalog, say 50,000+ products? Use the CLI instead. The browser based tool tends to choke and time out on really large imports. The command line version is way more stable for heavy lifting.
Step 5: Handle SEO — This Is Where Most Migrations Fail
This is the step that separates a good migration from a disaster. URLs look different in Shopware 6. If you just launch without redirects, Google sees a bunch of dead pages and a bunch of “new” pages with no authority. Years of ranking work, gone. We watched one store lose 40% of their organic traffic in three weeks because nobody set up the 301s. Don’t be that store. Export every URL from your SW5 install. Map each one to where it lives in SW6. Build your redirect file. Upload it. Then go into Search Console and resubmit your sitemap so Google crawls the new structure right away.
Step 6: Test Everything, Then Launch in a Low Traffic Window
Don’t launch without doing proper QA. And I mean actually going through checkout yourself. Placing test orders. Trying every payment option. Checking if shipping rates calculate right. Pulling up the store on your phone. Logging in as a customer and seeing if their old orders show up. Do all of that. Once you’re satisfied nothing’s broken, pick your quietest traffic window for the switchover. Saturday night works for most EU stores. Then park yourself in front of a dashboard for the next 72 hours and watch for anything weird. Oh, and write a rollback plan before you launch. Hopefully you won’t need it.
Need Expert Help With Your Shopware Migration?
Our team handles the full process from audit to launch.
Talk to Us →How Much Does a Shopware 5 to 6 Migration Actually Cost?
Nobody likes vague pricing, so here’s a realistic breakdown based on projects we’ve seen and worked on. The biggest cost driver isn’t the migration tool itself. It’s the custom plugin rebuilds, ERP reconnections, and theme development that eat up the budget.
| Store Complexity | Estimated Cost | Timeline |
|---|---|---|
| Small (under 1,000 SKUs, standard setup) | €5,000 to €15,000 | 4 to 8 weeks |
| Mid Market (1,000 to 10,000 SKUs, custom plugins) | €15,000 to €40,000 | 2 to 4 months |
| Enterprise (10,000+ SKUs, ERP/PIM, multi store) | €40,000 to €80,000+ | 4 to 6 months |
What makes the bill jump? Mostly custom plugins. Each one that needs rebuilding is basically its own mini dev project. ERP integrations are another big one because the API structure is completely different in SW6, so those connections have to be rewired from scratch. And if you want a full storefront redesign on top of the migration, that adds weeks and budget. Keeping a similar look with standard plugins? You’ll stay toward the bottom of those ranges.
Common Shopware Migration Mistakes (and How to Dodge Them)
We’ve cleaned up enough botched migrations to know where things go wrong. Every single one of these has cost someone real money:
- Nobody cleaned the data first. Someone migrated 3,000 dead products and 10,000 duplicate customers, then spent two weeks deleting them on the other side. Total waste.
- The 301 redirects got forgotten. This one physically hurts to watch. Organic traffic dropped 40% in three weeks. Recovery took months.
- Old plugins were assumed to work on SW6. They didn’t. The plugin architecture is completely different. Always check compatibility before you start migrating, never after.
- Migration ran on the production server instead of staging. One corrupted import later, the live store went down for 8 hours on a Tuesday afternoon.
- Checkout went live without testing payments. A store launched with a broken payment gateway. They didn’t notice until customers started emailing.
- Nobody watched the store after launch. The first 72 hours are when the weird stuff shows up. Edge cases, broken product pages, shipping miscalculations. Have a human watching.
Pre Shopware 5 to 6 Migration Checklist
Screenshot this or paste it into whatever project tool your team uses. Seriously, don’t kick off the migration until you can tick every one of these:
☐ Full product and category audit completed
☐ Plugin compatibility reviewed and replacements identified
☐ Complete URL inventory exported from Shopware 5
☐ 301 redirect map created (old URL to new URL)
☐ Staging environment with fresh Shopware 6 installed
☐ Migration Connector (SW5) and Migration Assistant (SW6) installed
☐ Data cleaned: dead products, duplicate customers, broken categories removed
☐ ERP / CRM / PIM integration plan documented
☐ Theme and design direction finalized
☐ Post launch monitoring plan and rollback strategy in place
Frequently Asked Questions
Nope. Not even a little bit. Anyone who calls this an upgrade either hasn't done one or is trying to undersell the work. SW6 was built from the ground up on different technologies. You're not updating. You're packing up shop and rebuilding on a new foundation. That's a replatforming project, full stop.
Depends entirely on how much custom stuff you've got. A straightforward store with standard plugins? Probably 4 to 8 weeks and you're live. Once you add custom plugins that need rebuilding, you're looking at 2 to 4 months more realistically. Enterprise setups with ERP connections, multiple storefronts, and complex product data? Budget 4 to 6 months minimum. The custom work is what stretches the timeline, not the migration tool itself.
Not if you do the redirect work properly. We keep hammering this point because it's that important. Map your old URLs to the new ones, set up 301 redirects, move your metadata over, and push your updated sitemap to Google. Will you see some wobble in rankings the first couple weeks? Probably. That's normal. Give it a month and things settle back down, usually in the same spot or better.
The standard stuff, yes. Products, customers, orders, categories, your media library. Those come across through the assistant without much drama. But anything custom? Forget it. Your Shopping Worlds have to be rebuilt as Shopping Experiences. Plugins need replacement or redevelopment. Themes are a complete redo. If your store has a lot of custom work, the assistant maybe handles 60% of what needs to happen. A developer has to do the rest.
Honestly? If you've got a tiny store, maybe 200 products, zero custom plugins, stock theme, you could probably muscle through it yourself using the Migration Assistant. Grab a coffee, set aside a weekend, you'll be fine. But the second you've got custom functionality, an ERP plugged in, or organic traffic that actually pays your bills? Get professional help. We've cleaned up enough DIY migrations to know that the agency fee is always less than what a botched migration costs you in lost sales and wrecked rankings.
Gone, unfortunately. The hashing is different between the two platforms and there's zero workaround for it. Every customer has to set a new password after you migrate. Sounds worse than it is though. If you fire off an email ahead of time letting people know, and set up a smooth reset flow, barely anyone complains. Maybe one or two support tickets out of a thousand customers. It's manageable.
Why should you choose iCreative Technologies for Shopware Migration Services?
“We’re not going to pretend we’re the only agency that can handle a Shopware migration. But we’ve been at this for 11+ years, and our track record speaks for itself:”
| What We Bring | Details |
|---|---|
| Certified Shopware Partner | Bronze Partner, Extension Partner, and Shopware 6 certified by the Shopware Academy |
| 30+ In House Shopware Developers | Dedicated team, not freelancers or outsourced contractors |
| 50+ Extensions Published | Live on the official Shopware Store with a 4.3/5 average rating |
| 280+ Brands Migrated | Across the US, Germany, Austria, the Netherlands, and the wider DACH region |
| Multi Platform Expertise | Shopware, Shopify, Magento, and WooCommerce migrations under one roof |
We know where the landmines are buried because we’ve stepped on a few ourselves.
Here’s what working with us actually looks like:
- Full Store Audit — we document every product, plugin, integration, and URL before touching anything
- Clean Data Migration — manual QA checks at every stage, not just automated scripts and hope
- SEO Preservation — complete 301 redirect mapping, metadata transfer, and sitemap resubmission
- Custom Plugin Rebuilds — if your SW5 plugin doesn’t have a SW6 equivalent, we build one
- Post Launch Support — we stick around after go live, not disappear the day you launch
- 200+ In House Developers — fully staffed across the US and India, so you get enterprise resources without the enterprise markup
If you’re also evaluating whether Shopify might be a better fit than Shopware 6, we handle those migrations too. Take a look at our Shopware development services page to see the full range of what we offer before you commit either way
Ready to Start Your Shopware Migration?
Get a Free Migration Consultation →Final Thoughts
Look, Shopware 5 is finished. That ship has sailed. The longer you sit on it the more risk piles up. No patches, fewer working plugins, and technical debt that gets heavier every quarter. Moving to Shopware 6 stopped being optional a while ago. The only real question left is whether you make the switch on your own schedule with a solid plan behind it, or panic migrate after a security incident forces your hand..
Bookmark this page and use it as your checklist when you’re ready to pull the trigger. Do the audit. Clean the data. Build in staging. Obsess over your redirects. Test like your revenue depends on it, because it does. And if you get to a point where you’d rather hand the whole thing to someone who’s been through it a dozen times, we’re not hard to find.
