Magento to Shopware 6: What the Migration Assistant Does and Doesn't Do
Shopware publishes an official Migration Assistant, and there's a Magento profile plugin that adds Magento 1.x and 2.x support to it. That tooling is genuinely good, and it is also the source of the most common misunderstanding about this project.
The Migration Assistant moves your data. It does not move your store. Your theme, your extensions, your custom modules, your integrations, and every business rule encoded in them are out of scope, and they are most of what your store actually is.
Plan for a replatform and the tooling is a pleasant accelerator. Plan for a data migration and you'll be six weeks in before you find out.
What the tooling actually covers
The Migration Assistant plus the Magento profile handles the structured entities: products, categories, customers, orders, media, and the core attribute data behind them. That's a serious amount of work you don't have to write, and it's the right starting point.
What it doesn't handle, and what you should scope separately:
| Area | Reality |
|---|---|
| Theme | Magento themes are not compatible with Shopware. The storefront is rebuilt. |
| Extensions | No path. Find a Shopware equivalent, or rebuild the behavior. |
| Custom modules | Rewritten against Shopware's plugin system. |
| Integrations (ERP, PIM, WMS) | Re-pointed and re-tested. Your middleware assumptions change. |
| Product variants | Data structures differ fundamentally — this is the mapping that consumes the time. |
| CMS content | Page Builder content doesn't map cleanly to Shopping Experiences. |
| Customer passwords | Hashing differs; plan a reset flow or a transparent rehash strategy. |
Shopware's own documentation is refreshingly direct that additional manual steps and custom development are required for a complete migration. Believe it.
The variant model is where the time goes
If you take one technical point from this post, take this one.
Magento models configurable products as a parent product plus child simple products, each a full product record with its own SKU, inventory, and price. Shopware models variants as a parent with generated variant combinations from property groups.
Those are not the same shape, and the conversion is lossy in both directions unless you make explicit decisions:
- A Magento simple product that belongs to a configurable and is sold standalone has no clean Shopware equivalent. Pick one behavior.
- Per-child pricing that doesn't follow a rule needs to become explicit variant pricing.
- Disabled or out-of-stock children affect what Shopware generates as valid combinations.
- Custom options, bundles, and grouped products each need their own mapping decision.
On a catalog of a few hundred simple products this is an afternoon. On 40,000 SKUs with deep configurables, it's the critical path of the project, and it needs a data person rather than a general developer.
Budget honestly
Published guidance puts a Magento to Shopware 6 migration at three to six months depending on complexity, and that matches what we see. The distribution is wide because it depends almost entirely on two things: how much custom code you have, and how clean your catalog data is.
A rough shape:
| Phase | What happens |
|---|---|
| Discovery and data audit | Catalog structure, attribute mapping, integration inventory, extension replacements |
| Storefront build | Design and build in Shopware; this runs in parallel with data work |
| Data migration runs | Repeated dry runs into staging, each one measured, not eyeballed |
| Integration rework | ERP, PIM, payments, shipping, tax, marketing |
| SEO and redirects | See below — start early, not at the end |
| Cutover and stabilization | Freeze, final delta run, DNS, then two weeks of watching |
The single biggest schedule risk is treating data migration as one event near the end. Run it repeatedly from week two. Every run surfaces mapping problems while you still have time to decide, and the final run becomes routine rather than dramatic.
The SEO work decides whether it succeeded
This is where replatforms visibly fail, and it's not subtle: traffic drops, and everyone remembers.
Map every URL before cutover. Magento and Shopware generate different URL structures. Export your live URLs — from your sitemap, from Search Console, from server logs — and produce an explicit old-to-new map. Anything without a target is a decision you haven't made yet, not a rounding error.
301, not 302, and no chains. Redirect once, to the final URL. Chained redirects leak signal and slow things down.
Prioritize by traffic and revenue, not by page count. Your top few hundred URLs carry most of the value. Get those exactly right; handle the long tail with patterns.
Keep structured data and metadata. Product schema, canonicals, hreflang if you're multi-region, title and description patterns. Rebuild them deliberately in the new templates rather than accepting defaults.
Baseline before, measure after. Record rankings, traffic, and conversion by template a month before cutover. Without a baseline you can't distinguish a migration problem from seasonality, and you'll argue about it for a quarter.
When Shopware is the right answer
To be fair to both platforms:
Shopware fits if you're in Europe and value its ecosystem and partner network; if you want a modern API-first core with a strong out-of-box content and merchandising story; if Shopping Experiences suits how your marketing team actually works; or if your Magento build has become an unmaintainable pile of extensions and you're rebuilding regardless.
Magento still fits if you have very large catalogs with complex attribute structures, sophisticated B2B pricing and quoting, heavy ERP integration built over years, or a team and agency relationship deep in the PHP ecosystem. If the honest problem is that your store is unpatched and slow, replatforming is an expensive way to avoid fixing that directly.
The worst version of this project is replatforming to escape technical debt you'll simply recreate. The best version is replatforming because the new platform genuinely fits how your business works now.
If you're going the other way, we've written that up too: Shopware to Magento.
Emyrix works on both platforms and will tell you when a replatform isn't the answer. If you want a scoped assessment — catalog complexity, integration inventory, and a realistic timeline — get in touch.
Migration Assistant capabilities change between releases. Verify current coverage against Shopware's documentation before scoping around this list.
