One
Source review
Access to the current platform, a sample export and an inventory of live URLs, integrations and apps. This is what turns a range into a price.
A replatform is a trading change, not a launch date
Data, redirects, integrations, testing and cutover handled as one piece of work rather than four separate jobs that meet on launch day.
What actually goes wrong
Migrations rarely fail on the data
They fail on the things nobody scoped: search, integrations and the week after launch.
Moving a catalogue is the part everyone plans for. The expensive failures are the ones that only appear once the store is live and trading on the new platform.
Search visibility disappears at cutover
Usually missing: a URL inventory taken before the build and a redirect map tested before launch. Rankings earned over years are attached to routes, and routes are the first thing a replatform changes.
Integrations were never in the scope
Usually missing: the ERP, warehouse, accounting, subscription or review systems the old store quietly talked to. They are found when a stock number stops updating, which is a week too late.
Some data has no equivalent
Usually missing: a mapping decision. Custom fields, bespoke app data and pricing rules do not always have a destination, and a transfer tool will not tell you that before it runs.
Nobody planned the trading week
Usually missing: a cutover plan. Orders keep arriving during a migration, customers need to reactivate accounts, and the internal team needs to know what changed before the first support ticket.
Scope the cutover, not just the catalogue.
How a migration runs
Five stages, in this order
Every one of them produces something you keep.
Swipe the stages
Two
Mapping and sample migration
A documented map of what moves, what transforms and what has to be rebuilt, proven on a sample before the full run.
Three
Store implementation
Theme implementation or adaptation, catalogue structure, payments, shipping and the integrations the business trades on.
Four
Validation and redirects
Data checked against source counts, journeys tested, redirect map verified one hop at a time, analytics and pixels continuous.
Five
Cutover and handover
A delta migration for anything that moved during the build, a planned switch, then the documents and the training that let your team run it.
What you keep afterwards
- Redirect map
- Migration plan
- Data mapping record
- Integration map
- Launch checklist
- Decision record
Working documents, produced because the migration needed them. They stay with you at handover.
The move itself
What moves, what is mapped, and where it lands
Read it left to right. Every stage is something the source has to produce before the next one can happen.
Source platform
- WooCommerceFull database access, generally complete exports
- Magento or Adobe CommerceComplete but complex, with deep attribute sets
- BigCommerceGood API coverage of core entities
- Wix or SquarespaceLimited exports, often products only
Source platform to Mapped entities
Exported, where the source platform exposes it. What it will not produce decides the rest of the scope.
Mapped entities
- Products and variants
- Collections
- Customers
- Order history
- Content pages and blogs
- URL structure
Mapped entities to Shopify
Mapped, transformed, or rebuilt where no Shopify equivalent exists. Proven on a sample before the full run.
Shopify
ShopifyThe destination store, with redirects mapped and verified before cutover
Passwords and stored payment details cannot transfer on any platform, so customer accounts need reactivation. Bespoke app functionality, custom fields with no Shopify equivalent, subscription logic and complex B2B pricing are rebuilt as build work rather than moved as data.
Sources
What moving from each platform tends to involve
Priced by what the source can actually export, not by the logo on it.
| Source | Typical data position | Where the work goes |
|---|---|---|
| WooCommerce | Full database access, generally complete exports | Plugin functionality with no Shopify equivalent, and variable product structures |
| BigCommerce | Good API coverage of core entities | Option sets, price lists and customer group logic |
| Wix or Squarespace | Limited exports, often products only | Content and URL reconstruction, and order history gaps |
| Magento or Adobe Commerce | Complete but complex, with deep attribute sets | Attribute mapping, multi-store structures and integration rebuilds |
| Shopify to Shopify | Clean exports on both sides | App data, metafields and keeping redirects intact across domains |
| Bespoke or export-only | Whatever the database will produce | Scoped manually. This is not estimated from a dropdown. |
We add a dedicated page for a source platform only when we can say something specific about it. We do not publish a page per platform with the names swapped.
Source platforms
Choose your current platform
See what moves, what needs rebuilding and how the cutover works.
- WooCommerce to ShopifyPlugin-held data, variable product structures and WordPress URL patterns.
- Magento to ShopifyAttribute sets, multi-store structures, customer groups and the integrations Magento was chosen for.
- BigCommerce to ShopifyOption sets and modifiers, price lists, customer groups and app replacement.
- Wix to ShopifyLimited exports, content that has to be rebuilt, and URL reconstruction from a crawl.
- Squarespace to ShopifyContent-led stores, limited commerce exports and a URL map worth protecting.
- Shopify to ShopifyConsolidation, ownership changes, markets, metafields and application data between two stores.
- Custom platform to ShopifySource access, undocumented schemas, transformation and staged validation.
Source platforms outside this list are still migrated. They route to manual scoping rather than to a page written by swapping a name, because we would have nothing platform-specific to tell you.
Money
What a migration starts at
GBP and USD, excluding VAT. Fixed scope follows source review.
Migration delivery
From-price or scoped after discovery
Migration and build
Shopify launch
From £5,000From $6,500
Moving to Shopify and building the store in one project, so the data and the storefront land together rather than in two disconnected pieces of work.
- Store build, configuration and templates
- Managed data migration within stated limits
- Redirects, analytics and technical SEO baseline
- Launch, training and short post-launch support
Starting price
Data only
Data migration
From £1,000From $1,300
Products, customers, orders and content mapped into a Shopify store that already exists or is priced separately. Fixed once source access and a sample migration are reviewed.
- Documented mapping of the selected entities
- Sample migration before the full run
- Validation against the source records
- Redirect mapping where URLs change
Starting price · scoped after discovery
Plus, B2B, multi-market
Advanced Shopify
From £8,000From $10,500
Shopify Plus, B2B, multi-market, multi-language, custom integrations or headless work. These configurations are sized after discovery, not instant-priced.
- Trade accounts, price lists and B2B rules
- Multi-market and multi-language configuration
- ERP, PIM, WMS and accounting integrations
- Headless or custom storefront work where justified
Starting price · scoped after discovery
Third-party platform, app and migration-tool fees are separate unless listed. Estimator output is indicative and non-contractual.
Questions
Asked before a move is agreed
What can normally be migrated?
Typically products, variants, collections, customers, order history, content pages, blogs and URL structure, where the source platform exposes them. Some data does not map directly and has to be transformed. We confirm exactly what moves after inspecting your export, not before.
Will order history and customer accounts move?
Usually, within the limits of what the source platform exports. Passwords and stored payment details cannot transfer on any platform, so customer accounts need reactivation. That communication is planned with you before cutover rather than discovered afterwards.
How do you protect existing search visibility?
We inventory live URLs, map redirects before launch, carry over metadata and titles where they still apply, and keep analytics and pixels continuous. We do not guarantee rankings, and nobody honest will.
What usually needs rebuilding rather than moving?
Bespoke app functionality, custom fields with no Shopify equivalent, subscription logic, complex B2B pricing and anything held only in a theme. Those are identified during discovery and priced as build work, not as data.
How accurate is the estimator?
It returns a band, not a quote. It is built from platform, data volume, design requirement and special requirements. Scope and price are fixed after reviewing source access, a sample export and your integrations.
Can you migrate from a platform not on your list?
Often, yes. Bespoke platforms and export-only sources route to manual scoping instead of a number, because the work depends entirely on what the source can actually produce.
Send the current platform and rough record counts.
That is enough for a useful range. The fixed scope follows source access, a sample export and your integrations.