In short: Switching from JTL-Shop to Shopware is technically well feasible - but the real decision is not about the shop, it is about the ERP (JTL-Wawi). If you want to keep the Wawi, you can connect Shopware via a connector and only replace the frontend. If you leave the whole JTL ecosystem, you are planning a larger project with an ERP question attached. There is no official Shopware migration profile for JTL - data moves via structured import through the Shopware API or third-party migration tooling.
The Wawi question first - everything else follows
JTL is not a shop system but an ecosystem built around the free JTL-Wawi merchandise management. That is exactly why a switch has two fundamentally different scenarios:
Scenario 1: Wawi stays, shop changes. You keep JTL-Wawi as your ERP and attach Shopware as the frontend - established connectors exist in the Shopware ecosystem for this. Sensible when your warehouse, shipping and marketplace processes run well in the Wawi and only the shop is limiting you (design, B2B features, extensibility, storefront quality). This is the smaller, more plannable move.
Scenario 2: Complete exit from JTL. Shop and ERP get replaced. Then the Shopware migration is only a sub-project next to the ERP decision - this path usually only pays off once the Wawi itself has become the bottleneck (multi-company structures, special processes, Windows server strategy).
My experience: most merchants who say "away from JTL" mean scenario 1 - they are happy with the Wawi and unhappy with the shop.
Why merchants switch from JTL-Shop to Shopware
- Storefront and Shopping Experiences: Shopware offers far more design freedom without template tinkering - from Shopping Experiences to the new component system.
- Extensibility: the Shopware plugin ecosystem and API-first architecture are a different league when custom processes need to be mapped.
- B2B: anyone planning serious B2B finds native components in Shopware (Evolve plan) instead of workarounds.
- Future topics: agentic commerce, AI product feeds and structured data are visibly developed in the Shopware core.
How the migration works technically
- Data: in scenario 1, products, variants, customers and orders largely arrive in Shopware via the Wawi connection; in scenario 2 via export/API import with clean mapping. JTL-specific constructs (parent/child articles, attributes, custom fields) need a well-thought-out target model in Shopware.
- Processes: shipping, payment methods, tax configuration and marketplace connections are set up anew or continued via the Wawi - this decides the project scope.
- SEO move: redirect mapping for all URLs - as with every migration, the item cheap offers leave out.
- Test phase: test order processes end-to-end with real Wawi communication before switching over.
Cost frame: scenario 1 often lands in the mid four-digit to low five-digit range for small to medium stores; scenario 2 is an ERP project with a shop component and plays in a different league.
My conclusion
The JTL question is an architecture question: where should the process intelligence of your business live - in the ERP or in the shop? Answer that cleanly and you get a plannable move instead of a bottomless pit. I am happy to help with the answer - including the honest variant "stay with JTL" if your setup is well served there.