We inspect how your current platform stores products, customers and orders, then test a sample move before pricing the full migration.
Fields may be overloaded, relationships may live in code and historic records may not match the current schema. We inspect the database, exports and routing code available to us. The mapping records source fields, transformations, destination fields and exceptions. A repeatable extraction is proven before the full scope is fixed.
Pricing, stock, fulfilment and customer rules may be application logic rather than data. We trace who reads and writes the system, inventory connected tools and decide what belongs in Shopify, an app, an integration or a separate application. We do not force operational software into the storefront when it does not fit.
A crawl cannot see routes called only by external systems, while code alone may not reveal legacy routes still receiving traffic. We use the routing code, live crawl, Search Console and referring-link data where available, then map route families and direct system calls deliberately.
Records and schemas may change while the new store is being built. The plan defines repeatable extraction, source and destination snapshots, the agreed delta, validation checkpoints, the point at which writes switch and the rollback route supported by the source and destination setup. If the old platform cannot support a safe rollback, that limitation is stated before cutover rather than hidden.
Scoped in stages, after source access
One bounded piece
£1,500$2,000
One bounded improvement: landing pages, a template rebuild, an analytics implementation, or a build-readiness review credited against a larger project.
Fixed price
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
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
Discovery is bounded and priced separately, then credited against the migration where the project proceeds. Fixed scope follows the sample stage rather than preceding it.
Usually, provided the data can be reached. A database replica, a read-only account or a scheduled export is enough to work with. What matters more than support is whether extraction can be repeated, because a one-shot export cannot be rehearsed.
That is the normal case. Schema meaning is recovered by reading the code that writes the data and by validating assumptions against a sample. It takes longer than a documented source, which is exactly why discovery is a separate, bounded stage.
We do not. Discovery is quoted on its own and credited against the migration if the project proceeds. Anything quoted as a fixed migration price before source access has been reviewed is a guess that will need revising.
Not always. Bespoke platforms sometimes contain genuine application behaviour that has no business being a storefront. In those cases the honest recommendation is a store plus a separate application, rather than forcing everything into a commerce platform.
A sample of real data tells us more than a specification written from memory.
