In short: Shops on xt:Commerce, Gambio, VirtueMart, osCommerce and related systems often run astonishingly stably - and that is exactly the trap: outdated PHP versions, extinct module ecosystems and missing legal features make every further month of operation riskier. There are no official Shopware migration profiles for these systems (community approaches exist for Gambio) - the proven path is a structured data import via the Shopware API. The good news: with these shops, the data volume is usually manageable and the switch more plannable than operators fear.
A personal word first
I spent part of my agency years with xt:Commerce shops before moving my first shop to Shopware in 2012. These systems were good in their time - this is not mockery but a sober observation: their time is over. The communities have shrunk, module developers have stopped, and modern requirements (mobile checkouts, the withdrawal button, structured data for AI search) simply no longer reach these systems.
Why "it still works" is the most expensive strategy
- Security: many of these shops run on PHP versions without security support. One known vulnerability in an orphaned module is enough - and in case of damage, the GDPR question arises too.
- Legal features: new obligations like the withdrawal button (since June 2026) no longer arrive as updates for these systems. Every legal change becomes an expensive one-off - if you can still find someone who knows the system.
- The developer factor: the silent killer. The number of people who can and want to maintain xt:Commerce 3 or VirtueMart shrinks every year - and their hourly rate rises accordingly.
- Business: no Merchant-Center-ready feed without tinkering, no clean ERP integration, no agentic commerce. The shop becomes a growth brake.
How the move realistically works
Without an official migration tool, the path is still well established - it just has a different name:
- Data analysis in the old system: what is there, and what of it is still good? After 15 years of operation, decluttering pays double - dead records, duplicates and orphaned categories do not need to move along.
- Export and mapping: extract products, categories, customers and (where sensible) order history from the old database and map them onto the Shopware data model. These systems' databases are well documented - this is craft, not magic.
- Import via the Shopware API - repeatable as test runs on staging until the result is right. Passwords cannot be carried over (different hashing) - customers reset them once; that is standard and communicable.
- SEO rescue: old shops in particular often hold valuable rankings grown over years. Complete redirect mapping for every old URL - the classic among underestimated items.
- Rebuild instead of replica: theme and functions are set up fresh in Shopware. That sounds like extra effort, but it is the opportunity: the 2009 checkout does not need to be rebuilt - it was never good.
Cost frame: since these shops rarely carry complex custom development, the move often lands in the mid four-digit to low five-digit range - frequently cheaper than a Magento migration and almost always cheaper than another year of playing for time.
My conclusion
For xt:Commerce, Gambio and VirtueMart shops, the question is not whether the switch comes, but whether it happens planned or forced - by a hack, a PHP version discontinued by the hoster, or a legal topic with a deadline. Planned, it is a manageable project with a clear end. Forced, it is an emergency with lost revenue. The upfront analysis costs little and turns diffuse worry into a concrete plan.