E‑commerce replatforming without losing sales, SEO or data
We move stores to Medusa.js from platforms that no longer keep up with sales: Shopify, WooCommerce, Magento, Adobe Commerce, PrestaShop and others.
20 minutes online. You get a straight answer: buy, build or drop it.
- Your current platform
- Products, customers, orders
- New store on Medusa
- From
- Shopify, WooCommerce, Magento, Adobe Commerce, PrestaShop, Sylius, Shopware
- To
- Medusa.js
- Pricing
- A fixed price for an agreed scope
First, we compare migrating with staying on your current platform.
When replatforming makes sense
The platform blocks change
A new process, channel or pricing model needs workarounds that cannot be maintained.
Apps instead of a foundation
App costs and dependencies grow faster than sales.
Ageing technology
The current system needs ever more expensive maintenance, upgrades or rewrites, for example PrestaShop 1.7 without patches, Magento 1 or a Sylius store whose vendor has left.
Split channels
B2B and B2C run on separate systems, so every change is made twice.
Problems we solve
What you get
An audit of your current store
An inventory of data, apps, integrations, URLs and processes to keep, simplify or replace.
A data migration plan
Products, variants, customers, orders and content: field mapping, data clean-up and trial migrations on a copy.
SEO protection
A complete URL list, one-to-one 301 redirects, metadata and structured data. After launch, we compare indexing with the previous state.
A new store on Medusa
The processes that worked, rebuilt, and the ones that needed workarounds, simplified.
Cutover with a rollback plan
A cutover schedule, a short change freeze, a rollback scenario and monitoring of the first days.
How we approach migration
We have not published a migration case study yet, so here are the principles we follow.
Trial migration first
A full run on a copy of your data before we touch production. Differences show up long before launch day.
Redirects are part of the scope
The 301 map is built together with the data model, not a week before launch.
Customer passwords
Not every platform allows passwords to be carried over. When it cannot be done safely, we design a smooth way to set a new one.
Integrations move with the store
ERP, payments and shipping are tested on the new store before cutover day.
How we work
Conversation
Your current platform, the problem and the outcome you expect. Whether migrating makes sense at all.
Audit and fixed price
An inventory of data, apps and integrations. We quote the migration at a fixed price.
Build and trial migrations
The new store is built alongside the current one, and we run trial migrations until the results match.
Cutover
Final migration, redirects, critical-path testing and launch.
After launch
Monitoring orders, integrations and indexing. Fixes and the next stages of development.
Which platform you are coming from
Every platform has a different reason to migrate and different traps when moving data. These are the ones we meet most often.
They are examples, not a closed list. The same things matter for each: how data, URLs and customer passwords can be exported.
| Platform | Why companies move | What we check during the move |
|---|---|---|
| PrestaShop | Version 1.7 has not been maintained since PrestaShop 9 was released in June 2025, and upgrading to 8.2 or 9 requires PHP 8.1 and often a rewrite of modules and the theme. | Customer passwords (they depend on the installation key), discounts from groups and specific prices, and the ERP connector. If the B2B module and the connector are the only reasons to stay, we cost both roads. |
| Sylius | An agency implemented the store, and the agency knows the code. The vendor has left, or Symfony and PHP upgrades eat the development budget. | Pricing, channel and promotion logic. The two data models are similar, so products with variants, channels and price lists map without workarounds. |
| Magento | Magento 1 has been unsupported since 2020, and Magento 2 needs a team for upgrades. | The catalogue with attributes and variants, customer groups and order history. We replace extensions with custom logic only where you really use them. |
| Adobe Commerce | The licence is priced in tiers of gross merchandise value and average order value, so it rises as sales grow. Release lines also lose support: 2.4.6 left regular support in August 2026. | Which B2B module features you really use: company accounts, shared catalogues, negotiable quotes, requisition lists and purchase order approvals. Each one needs an equivalent in the new store, so we list them before we quote. |
| Shopware | Shopware 5 reached end of life at the end of July 2024. Moving to Shopware 6 is a migration, not an update, and Shopware 5 plugins are not compatible with it. Since you migrate either way, it is the moment to compare platforms. | Which plugins carry logic you still need, customer groups with their prices, product variants and the URL structure. The plugin list becomes a list of features to rebuild or drop before we quote. |
| ShopifyBigCommerceWooCommerce | A revenue-based fee, yet another paid app or missing B2B. | Data export through the API and URLs mapped one to one. |
Engagement model: fixed price
We quote the migration at a fixed price for an agreed scope.
The price depends on the amount and quality of data, the number of apps to replace, the integrations to switch over and the number of URLs.
A live store on our foundation launches in 30 days, from €5,000 net.
Live e-commerce in 30 daysQuestions about e-commerce migration
How much does an e-commerce migration cost?
We quote the migration at a fixed price after auditing your current store, so you know the cost before we start. The price depends on the volume and quality of data, the number of apps to replace, integrations and how much the store changes. We also compare it with the long-term cost of staying on your current platform.
How do I migrate a store without losing SEO?
The essentials are a complete list of current URLs, one-to-one 301 redirects, preserved content and metadata, and indexing checks after launch. We do this as part of the migration, not as a separate service.
What data can be migrated?
Usually products with variants and images, categories, customers, order history, content and URLs. The details depend on the source platform, so we verify them in the audit and a trial migration.
Will customers have to create new accounts?
We migrate the accounts. Passwords only when the source platform allows it to be done safely. Otherwise, customers set a new password on their first login, and we design that step to be simple.
How long does a store migration take?
You get the timeline together with the quote, because the time depends on the scope and the number of integrations. We plan the cutover so that the change freeze is as short as possible.
Is migrating always worth it?
No. If configuration, a single app or an integration solves the problem, staying is cheaper. We say so in the first conversation.
I run PrestaShop 1.7. Upgrade or migrate?
Cost both roads first. Upgrading to 8.2 or 9 makes sense when the store sells in a standard way, your modules have versions for the new branch and the ERP integration works. Migrating makes sense when the upgrade means rewriting the theme and modules anyway, and you are missing per-customer discounts, company accounts or a stable ERP integration. Version 1.7 itself is no longer maintained, so leaving it as it is is not an option for a store holding customer data.
Do you migrate from Adobe Commerce or Magento to Medusa?
Yes. Adobe Commerce is built on the Magento Open Source code, so the catalogue, customer groups and order history move the same way. The difference is the licence and the B2B module. On Adobe Commerce we first list the features you use: company accounts, shared catalogues, negotiable quotes and requisition lists, and then cost an equivalent for each. If the licence is your only problem and extensions cover what you need, moving to Magento Open Source can be the cheaper road, and we say so.
Do you migrate stores from Shopware 5?
Yes. Shopware 5 reached end of life at the end of July 2024, and moving to Shopware 6 is itself a migration, because Shopware 5 plugins are not compatible with it. We start with the plugin list: which ones carry logic you still need and which can go. Then we move the catalogue, customer groups, prices and URLs. If Shopware 6 covers your needs and you have a Shopware team, we say so.
Do you migrate stores from Sylius to Medusa?
Yes. Sylius and Medusa have a similar data model: products with variants, channels, price lists and promotions, so the logic carries over well. The biggest work is the storefront and the integrations. Before we start, we check whether the problem is the platform or the lack of a team maintaining it. If finding a Symfony team is the better road, we say so.
Let’s check whether migrating pays off.
Bring the name of your current platform and one change you cannot make today. In 20 minutes, we will work out whether a migration makes sense.