Inventory
Platform, catalogue, customer groups, payment and shipping methods, integrations and the URLs that carry traffic or links. Including the pages that only live in a menu.
Service
Migrating to Medusa from WooCommerce, Shopify or Magento
A migration is not an export button. We move products, customers and URLs, and we map out up front which plugin logic will not come along by itself. The goal is a shop that needs less maintenance afterwards, not a copy of the same bottlenecks.
At a glance
- Inventory
- Data mapping
- New shop, in parallel
- Redirects and go-live
Custom quote after a free intro call
What we do
What is included
Data mapping
Which fields land where in Medusa, what needs cleaning, and whether order history moves along or stays in the old system for reference.
New shop, in parallel
We build alongside. The old shop keeps selling until the switch. No big bang on a Friday afternoon without a way back.
Redirects and go-live
Old URLs get a 301 to their new location. Sitemaps, canonicals and the payment flow are checked before DNS changes.
Who it is for
Who this fits
- WooCommerce shops where plugins, updates or a heavy catalogue set the pace.
- Shopify shops hitting the limits of checkout, data or B2B pricing.
- Magento shops that want to keep the complexity but trade the stack for a smaller system they own.
- Teams that take URL structure seriously because links and ads already point to it.
- Brands running separate shops per country that want one engine for all markets.
Honest advice
When we advise against it
- A shop that mainly wants a new look and is otherwise happy with its platform.
- A migration where 'rebuild everything exactly, including every plugin exception' is the goal. Then you move the knot along with you.
Price
What determines the price
A custom quote after a free intro call. These factors determine the price, not a menu.
- Source platform and data quality
- A clean Shopify catalogue is different from a Magento tree with custom attributes or a WooCommerce database full of plugin tables.
- URLs and content
- The more indexed URLs and editorial pages, the more careful the mapping. That work is dull, and it is half the project.
- Order history and customers
- Moving only customers is smaller than wanting years of orders, invoices and returns in the new admin.
- Integrations that need rebuilding
- An ERP plugin rarely has a twin in Medusa. We rebuild the integration around the process, not around the plugin name.
Process
The process
- 01
Audit
We read the current shop: data, URLs, plugins, integrations, and what your team fixes by hand every week.
- 02
Mapping and scope
What moves, what gets cleaned up, what stays behind. Including a redirect plan.
- 03
Build and trial migration
First a trial with part of the catalogue. Data errors show up then, not on launch day.
- 04
Switch-over
Content freeze, final sync, redirects, checkout checks. The old shop stays reachable read-only for a while if needed.
Insights
Further reading
From this service to the articles, and from each article back again.
- ArticleMigrating to Medusa: why, and how to do it rightWhy companies move to Medusa, from which platforms it makes sense, the six steps of a good migration and when you are better off staying.Read more
- ArticleWooCommerce vs Medusa: when WordPress holds the shop backWooCommerce and Medusa compared on extensions, hosting, three-year cost, B2B and multiple shops. With real extension prices and our Shingyo project.Read more
- ArticleShopify vs Medusa: costs, flexibility and when to choose whichShopify and Medusa compared on subscription, revenue fees, apps, hosting, three-year cost and B2B. Prices as of 5 November 2026, and honest about where Shopify wins.Read more
- ArticleMagento (Adobe Commerce) vs Medusa: licence, upgrades and B2BMagento and Adobe Commerce compared with Medusa: licence, upgrades, hosting, three-year cost and B2B. Honest about where Adobe Commerce is stronger.Read more
- All articlesPlatform comparisons and the migration guide, with sources.To the articles
Which platforms do you migrate from?
WooCommerce, Shopify and Magento. Other sources are possible if we can get to the data. We discuss that in the intro call rather than publishing a list.
Will we keep our Google rankings?
We set up 301 redirects from old URLs to new ones. That is the step that keeps existing links working. We do not guarantee rankings; they also depend on the page, the competition and what changes in the content.
Do orders and customers come along?
We usually move customers so people can log in and see their details. Order history is a choice: sometimes the old system is the better archive. We tell you up front which of the two we do.
What happens to blog posts and landing pages?
Pages with traffic are mapped or rebuilt. We do not automatically drag every WordPress post along. An old marketing blog does not automatically belong in a commerce migration.
How long does a migration take?
That depends on the catalogue, the integrations and how much of the storefront is new. After the audit we give a range. We do not promise a fixed number of weeks on a website.
Can we keep selling during the build?
Yes. The new shop runs alongside. We plan the switch for a moment when your team can check it, during our weekday office hours (CET).
Free intro call
What is your challenge?
Twelve shops that need to become one, an ERP that sets the price, or a checkout that does not do what you want. Tell us in one call. You will hear honestly whether Medusa fits.
Based in Nijmegen, the Netherlands, working with companies across Europe. How we work with European teams.