Replatforming — for stores on Magento, WooCommerce, BigCommerce or a custom build
Move to Shopify without leaving anything behind.
The catalogue, the customers, the order history, the URLs and the rankings you spent years earning — carried across, not rebuilt from a spreadsheet. We script the migration, rehearse it against a copy of your store, and only then cut over. Seven years of luxury Shopify engineering behind every move, and an honest answer first about whether you should move at all.
Book a discovery callShould you move at all
Platform assessment comes first, and it is costed both ways. Sometimes the right answer is to stay and fix what is there. We have given that answer, and we will give it to you if it is true.
What moving fixes
A platform your team fights instead of runs — patched extensions, a hosting bill that grows with every release, a checkout you cannot change, and a developer bench you cannot find when something breaks.
What moving does not fix
Thin product data, a slow supply chain, or a storefront that does not say what it sells. Those come across with you. We name them in the assessment rather than let you discover them on the new platform.
What it costs to stay
Upgrades, security patches, hosting, the agency retainer that keeps the old platform breathing, and the opportunity cost of every feature you did not ship. Put beside the migration quote, it is usually the number that decides.
Shopify, Plus, or headless
Most luxury stores belong on a Shopify theme. Plus when checkout, B2B or Markets need it. Headless when the brand's design or content ambitions outrun what a theme can hold — and we say so only when it is true, because it costs more to run.
What a migration has to carry
A replatform fails in the details nobody listed. These are the ones we list, map, and reconcile before anything goes live.
The catalogue
Products, variants, options, images, metafields, inventory across locations, and the vendor data that never fitted the old schema — mapped to Shopify's model rather than forced into it.
Customers and their history
Accounts, addresses, tags and segments, and the order history behind them — so a customer who logs in after launch sees the orders they placed before it.
URLs and rankings
A redirect map for every product, collection, page and article, the structured data rebuilt, Search Console handed over cleanly. Rankings can wobble for a few weeks after any move; a full map is what keeps the wobble from becoming a loss.
Integrations
ERP, 3PL, PIM, POS, payments, email and SMS, reviews, loyalty — each mapped to a Shopify equivalent, rebuilt as a custom app, or named as having no equivalent before you sign anything.
The design
Ported faithfully to a theme or headless build, or redesigned while we are in there. Same people either way, so what gets designed is what gets shipped.
The content
Editorial pages, the blog, media, and the odd landing page someone built in 2019 — carried across, or retired deliberately, never lost by accident.
How we run it
Scripted and repeatable, so the cutover is rehearsed before it is real. A one-click export tool exists for every platform, and it is what loses the data.
Assess and map
Every field, integration and URL on the old platform, and what each one becomes on the new. This is where the fixed fee is set.
Script
Migrations written as code, run against a copy of your store, and re-run until the numbers reconcile — product counts, order totals, customer records, all of it.
Build
The theme or headless storefront, the design, the custom apps and the integrations, built while the migration scripts mature.
Rehearse
A full dry run on the real data. Redirects tested, checkout tested with real payment methods, every integration exercised.
Cut over
A planned window, usually the quietest hours you have. DNS moves, redirects go live, and there is a person on the line until the first orders come through cleanly.
Stabilise
Post-launch monitoring, fixes, and Search Console watched for the weeks that matter. Then, if you want it, the support retainer that keeps it that way.
What we will tell you plainly
The things migration pitches leave out, said here so you do not find them out in week six.
Zero downtime is a promise nobody can fully keep
We plan for the shortest window your store allows, and we tell you how long it will be. Anyone promising none is guessing.
Rankings move
Even a perfect redirect map produces a few weeks of movement while search engines re-crawl. We watch it, we report it, and we say what is normal and what is not.
Some apps have no equivalent
The old platform's extension that did one strange thing may have no Shopify counterpart. We find those in the assessment and quote the custom app, or say it is not worth it.
We have recommended staying
When the numbers said the old platform, fixed, would serve for another two years, we said so. It cost us a project. It is why you can trust the assessment.
Who this is for
A good fit
A luxury or premium store of one to fifty people on Magento, WooCommerce, BigCommerce, Salesforce Commerce Cloud or a custom build, where the platform has become the constraint and nobody in-house can move it.
Also a good fit
Brands consolidating several properties — a shop, an editorial site, a custom application — into one build. We have done exactly this.
Probably not a fit
Pre-launch or sub-$1M stores. Start on Shopify directly and spend the migration budget on inventory and traffic.
Not a fit
Anyone who wants the one-click export. It exists, it is cheap, and it is the reason most migrations lose the order history.
Replatforming to Shopify
Quoted as a fixed fee after the platform assessment, against catalogue size, the integrations involved, and how much of the storefront is a port versus a redesign. The number does not move once agreed. A straightforward theme migration runs in weeks; a headless rebuild with an ERP behind it runs in months; the assessment gives you yours.
Book a discovery callNot sure whether to move at all? The audit sprint includes the platform assessment, costed both ways, and its fee is credited against the migration if you go ahead.
Questions
- Will we lose our Google rankings?Not if the redirect map is complete and the structured data is rebuilt, which is most of what we do in the URL work. Expect a few weeks of movement while search engines re-crawl, then recovery. What loses rankings is a migration that drops URLs or ships without the redirects — the one-click export does both.
- How long does a migration take?It depends on the catalogue, the integrations and whether the storefront is ported or redesigned. A straightforward theme migration runs in weeks. A headless rebuild with an ERP and a 3PL behind it runs in months. The assessment gives you a number for your store rather than an average for someone else's.
- Can we keep our current design?Yes. We port it faithfully to a Shopify theme or a headless build. Most brands take the opportunity to fix what they always wanted to, and because design and build are the same people here, that does not add a handoff.
- What happens to our ERP, 3PL, and email platform?Each one is mapped in the assessment to a Shopify equivalent, a custom app we build, or an honest note that there is no equivalent. Nothing is discovered after the contract is signed. The integrations are exercised in the rehearsal before cutover, not on launch day.
- Will the store go down?For a planned window, as short as your store allows, usually in your quietest hours. We tell you how long before we start. Anyone promising zero downtime on a platform move is guessing, and we would rather give you a number you can plan around.
- Should we go headless?Probably not, and we will say so if it is true. Most luxury stores belong on a Shopify theme, with Plus when checkout, B2B or Markets need it. Headless earns its cost when the design or content ambitions outrun what a theme can hold. We build both, so the recommendation is not shaped by what we would rather sell.
- What if you tell us not to move?Then you have a costed plan for fixing what you have, and you keep it. The assessment is part of the audit sprint, which you own whether or not you continue with us. We have given that answer before.
- Do you support the store after launch?Yes. Stabilisation is part of every migration. After that, a maintenance retainer scoped to your store — updates, platform changes, fixes, performance, and someone to call who knows the build.