Migration guides, written by the people who did the work
Practitioner accounts of moving a live store onto Vendure, written with the partner who ran that project and fact-checked by us. Each guide says what ports as data, what gets rebuilt, and what you should retire on the way. More guides follow as partners deliver them; until then, every platform has a comparison page.
Migration guides
Shopify Plus
Felipe Arango of iDeum on when to leave Plus and when to stay. Sort the theme, apps, Functions, Flow and metafields into retire, redesign and adopt, move the catalogue as data, rebuild the storefront and checkout as their own project, and prove the pipeline on B2C before B2B.
Magento and Adobe Commerce
Pinelab on moving a large-format print shop whose products are configured and priced by area. Customers, orders, content and slugs imported cleanly. Pinelab rebuilt the configurator, the pricing calculations and the storefront, and left the old Magento promotions behind on purpose.
WooCommerce
Haus on moving a Swedish plumbing member organisation off WooCommerce without rebuilding the website. Product data, pricing and checkout went to Vendure; WordPress, Elementor and the member companies editing their own pages stayed exactly where they were.
Shopware
A reference migration of Shopware's demo shop, checked value by value: the catalogue through the Admin API, customers and orders as finished records with their passwords, and rule prices and Rule Builder logic rebuilt as code.
What these migrations took
The partners' own figures, one project each, so read them as planning anchors rather than a price list. Keep three costs apart when you budget: the plan price, which is the same as starting new; the implementation, which is one-off and done by your team or a partner; and running costs, self-hosted or on Vendure Cloud.
Magento
Pinelab · Martijn van de Brug
- hours, backend to storefront
- 0hours, backend to storefront
- months elapsed
- 0months elapsed
- developers
- 0developers
A large-format print shop with products priced by area.
WooCommerce
Haus · Jonas Landgård
- weeks for a comparable retrofit
- 6–12weeks for a comparable retrofit
- variants in Vendure today
- 0variants in Vendure today
- content pages moved
- 0content pages moved
Commerce moved off WordPress; the website stayed.
Shopify Plus
iDeum · Felipe Arango
- months, driven by integrations
- 4–7months, driven by integrations
- passwords Shopify exports
- 0passwords Shopify exports
His planning view for a mid-market store.
Shopware
SpaceParrots · Kevin Mattutat
- variants checked value by value
- 0variants checked value by value
- orders moved as finished records
- 0orders moved as finished records
- of 151 passwords kept
- 0of 151 passwords kept
A reference migration of Shopware's demo shop.
Where 400 hours went
- Backend: configurable products and integrations40%
- Storefront40%
- Data migration20%
What drives the effort
Across the four guides, largest first
- Integrations you re-pointThe timeline moves with how many you re-point, not with catalogue size. iDeum
- The storefrontUsually the largest part: page scope, CMS, designs and team. SpaceParrots
- Custom pricing and product logicQuick to write, slow to test until prices match exactly. Pinelab, SpaceParrots
- Customers and order historyLonger than the catalogue: states, discounts and guest accounts. SpaceParrots
- Catalogue sizeHours to days. Moving the data was the small part. Pinelab, iDeum
What every guide covers
A migration is a sorting exercise before it is a build. Every guide answers most of these questions, in the author's own structure.
- The sort: retire, redesign, rebuild
- Which of your customisations are still earning their keep, which need rethinking, and which only exist because the old platform made you build them?
- What moves as data
- Catalogue, customers, companies, prices and order history: what exports cleanly, what needs mapping, and what you leave behind.
- What gets rebuilt
- Storefront, plugins and custom logic: what is rewritten against the GraphQL API, and where the B2B storefront included from Scale is the starting point.
- Integrations
- ERP, PIM, payments, search and tax: which connections re-point, which are replaced, and in what order.
- Cutover sequence
- How the author ran the switch: what went live first, what ran in parallel, and how long the old platform stayed on.
- Where cost and risk live
- The parts of the project that took the time, and the decisions the author would make differently.
Partners, not marketing
The Vendure team leads an implementation only as part of an Enterprise contract. Most stores move onto Vendure with official partners, Friends of Vendure or in-house teams, so the people best placed to describe a migration are the partners who have run one.
Written by the partner who ran it
Each guide has a named author and their company on the page. It reads as a project account: what they did, what they would do again, and what they would not.
Fact-checked by Vendure
We check every claim about the platform, tighten the writing, and return the draft to the author before it goes live. Nothing is published that either side cannot stand behind.
The author is your first call
Reading a guide is the shortest route to the team that already knows the migration. Contact them directly, or find another official partner for your region.
Same plans whether you migrate or start new
Plans are flat monthly prices with no fee on gross merchandise value, orders or users, so the store you bring over costs the same as one built new. Vendure Framework stays free and open source underneath every plan.
Planning a move to Vendure, answered
No. Most guides describe a phased cutover: data first, then the storefront, then integrations, with the old platform running alongside until the last dependency is gone. The right sequence depends on where your risk sits, which is exactly what each guide is written to show.
Vendure is headless, so the storefront is rebuilt against the GraphQL Shop API or connected from a frontend you already run. From the Scale plan the Vendure B2B Storefront is included: a production Next.js storefront with company accounts, quotes, approvals and quick ordering already wired, to ship as it is or adapt to your brand.
Your own engineers, an official Vendure partner, or both. Partners own delivery end to end. Professional Services puts the engineers who build Vendure alongside your in-house team without taking delivery away from them.
No. A migrated store is on the same plans as a new one: Starter €199, Growth €599 and Scale €2,499 a month on a 12-month term, and Enterprise from €60,000 a year. Implementation is separate, whether your team or a partner does it. See pricing for what each plan includes.
Yes. The list above is where we have a partner with real experience or a written comparison. Vendure imports catalogue data from CSV. Customers and orders move through a script that uses Vendure's own services, as the guides show. The comparison pages explain how it differs from the platform you are on. Talk to us and we will tell you plainly whether Vendure is the right destination.
Ready to plan the move?
Bring the customisations your current platform made you build. A partner who has run this migration, or our own engineers alongside your team, will sort them into retire, redesign and rebuild before anyone writes code.
