Products move relatively easily. Metafields, app data, subscriptions, markets, payment history and two stores trading at once make the real scope.
The destination may already contain products, customers, orders, handles, apps and settings. We review both stores before setting the mapping rules.
We decide how duplicates, handle collisions, collections, metafields and metaobjects are resolved. Representative collisions are tested before the full run.
Customer identities and order histories need a merge rule. Passwords and stored payment details do not transfer. We validate sample histories and plan reactivation where required.
App data is not automatically portable between stores. Each vendor path is confirmed. Subscription contracts and payment methods need a specific plan and may require customer action.
We map market and domain changes, preserve existing handles where sensible and create redirects for routes that change. The old domain should remain registered and serve the agreed redirects after the move.
For consolidation, both sources may keep trading during the build. The cutover plan states the full migration point, the delta from each source, the time the streams stop or switch and how duplicate or late orders are checked.
Scoped after reviewing both stores
Data only
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.
Starting price · scoped after discovery
Migration and build
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.
Starting price
Plus, B2B, multi-market
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.
Starting price · scoped after discovery
Both stores are reviewed before a fixed scope, because the destination’s existing configuration matters as much as the source’s data.
Where the requirement is only a change of ownership, transferring the existing store is usually simpler and cheaper than migrating. Migration is the right answer when catalogues are merging, the market structure is changing or the destination store already exists.
Subscription contracts are tied to the store and the payment provider that created them, so they do not transfer. Subscribers have to be re-established with their consent, which makes this a customer communication project first and a data project second.
The values move once the definitions exist on the destination. The definitions, their types and validations, and every place in the theme that reads them have to be recreated deliberately. On a store with a mature metafield model this is a substantial part of the work.
It should stay registered and serving one-hop redirects for a good while after the move. Letting it lapse discards the link equity the business paid to build, and it is the most common avoidable loss in a store consolidation.
A consolidation, ownership transfer and market restructure need different plans even though all three are Shopify-to-Shopify moves.
