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, PrestaShop and others. Before we move anything, we check whether a migration is really needed, because sometimes tidying up the current store is enough.
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 on older Magento versions.
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. With a large unknown, we start with the implementation plan.
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.
Platforms we migrate from
Examples, not a closed list. What matters is how the data and URLs can be exported.
- Shopify
- Shoper
- WooCommerce
- Magento
- PrestaShop
- IdoSell
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.
If you first need to compare migrating with staying on your current platform, we do that as part of the implementation plan: 5 working days, €2,500 net.
See the implementation planQuestions about e-commerce migration
How much does an e-commerce migration cost?
It depends on the amount and quality of data, the number of apps to replace, integrations and how much the store changes. After the audit, we quote the migration at a fixed price. 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?
It depends on the scope and the number of integrations. We provide the timeline together with the quote, and 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.
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.