We have run these routes
Magento, WooCommerce and Salesforce Commerce Cloud migrations have all been through this team — not a partner, not a subcontractor.
MAGENTO, WOOCOMMERCE, SALESFORCE AND LEGACY SHOPIFY
Move to Shopify with your URLs, data and revenue intact
We have replatformed brands off Magento, WooCommerce and Salesforce Commerce Cloud onto Shopify and Shopify Plus, including multi-storefront retailers with their own internal systems to reconnect.
IN SHORT
- A Shopify Plus migration typically takes 10 to 16 weeks from discovery to launch.
- Search rankings survive when the redirect map is built from live URL data and tested against staging before go-live.
- Catalogue, customers and order history migrate on every route; passwords never do, so customers reset at launch.
- Platform-specific code — Magento extensions, WooCommerce plugins, SFCC cartridges — is replaced individually, not ported.
- Multi-storefront brands launch one region first and use it as the template for the rest.
- Routes we run
- Magento, Woo, SFCC, legacy
- Typical duration
- 3–6 months
- Data moved
- Products, customers, orders
- URLs
- Mapped from live search data
- Rollback
- Old store stays up until DNS
Which route is yours?
Each platform fails differently, so each migration is a different project. Find yours — every one has its own page with the detail that actually matters for that route.
Magento to Shopify Plus
The route we have run most often — Trunki, Big Shoes and Halcyon Nights all came off Magento. The cost is in the extensions, not the catalogue.
WooCommerce to Shopify
Dekoni Audio took this route. The project is really a plugin audit — what each one does, and whether Shopify does it natively.
Salesforce Commerce Cloud to Shopify
Chicco moved this way. Cartridges, internal systems and several locales, phased so that approval cycles do not block everything at once.
BigCommerce & Legacy Shopify
Two different jobs. A legacy rebuild moves no data at all, which makes it the lowest-risk project on this page.
What a replatform really costs you
Not the quote — the things that decide it. They are the same five whichever platform you are leaving, and only one of them is the catalogue.
- The extensions, plugins or cartridges your store runs on — each needs a decision before the estimate is real, and this is where quotes go wrong.
- The integrations behind the store: ERP, PIM, 3PL, subscriptions. Each has an owner who is not on the project, and coordinating them is a cost line.
- The URLs that actually earn traffic and revenue, which is a much shorter list than the sitemap and is the one that gets individual attention.
- The customisations with no Shopify equivalent, which are modelling decisions rather than transfers — and become permanent if made in a hurry.
- Years of editorial, landing pages and campaign history, which is the line most often forgotten at estimate time.
- Priced by
- Scope, in writing
- Biggest variable
- Extensions and apps
- Settled first
- The URL inventory
- Never moved
- Password hashes
- Old store
- Live until DNS switches
What changes when you move
The platform question is really an ownership question. Not which system has more features on a comparison sheet, but what your team can change on a Tuesday afternoon without raising a ticket — and what you stop paying to keep running.
| Legacy platform | Shopify Plus | |
|---|---|---|
| Hosting and patching | Yours to run, budget and monitor | Included, with PCI compliance handled |
| Checkout | Custom, and expensive to maintain | Maintained by Shopify, customisable on Plus |
| Release cadence | Release windows and regression risk | Theme deploys in minutes, previewable |
| Content changes | Usually a developer ticket | Sections your merchandisers control |
| Extension upgrades | Version-locked, upgrade projects | Apps update themselves |
| Multi-region | A storefront per market | Shopify Markets from one storefront |
| Where budget goes | Keeping the platform running | Merchandising and conversion work |
How a migration runs
Seven stages. The middle three are where the cost of a migration is actually decided.
- 01
Discovery
Two weeks inside your current store, analytics and operations. We map the catalogue, the integrations, the storefront count and the trading calendar, and agree what success means before anything is designed.
- 02
Data map
Every field in your current platform gets a Shopify destination or an explicit decision to drop it. This is where years of attribute drift get resolved, in a document, rather than at launch.
- 03
Replacement plan
Extensions, plugins and cartridges are assessed one by one — native feature, app, Shopify Function or custom code — each with an estimate attached. This is what makes the migration quotable.
- 04
Build
Storefront and integrations built in two-week increments with staging links, performance budgets and QA on real devices throughout.
- 05
Redirect map
Built from your live URL export and Search Console data, then crawled against staging so every indexed URL resolves before DNS changes.
- 06
Dry run
A full timed rehearsal of the data migration against the real dataset, so launch day has a known duration and a known rollback point.
- 07
Launch and monitor
Launch planned around your peak with rollback criteria agreed up front, then two weeks watching rankings, 404s, checkout and integration queues.
The part most migrations get wrong
Redirects are not a launch-week task
The single most expensive migration mistake is treating URLs as something to sort out after go-live. By then the crawl has already happened, the 404s are already logged, and the rankings you spent years earning are already moving.
We build the redirect map from your live URL export and Search Console data — because a sitemap does not always reflect what is actually indexed — then crawl staging against the full map before anyone touches DNS. Titles, meta descriptions, canonical tags and structured data are carried across rather than regenerated from theme defaults.
What migrates on every route
- Products, variants, images and collection structure
- Customers and address books
- Order history with line items and fulfilment status
- CMS pages, blog content and navigation
- URLs, through a tested redirect map
- SEO metadata, canonical tags and structured data
Customer passwords never migrate — no platform carries password hashes across, so customers reset at launch. That is standard, and worth saying in your launch email rather than letting people discover it.
Why brands pick us for a replatform
Quoted before contract
The replacement plan puts an estimate against every extension, plugin and cartridge, so the scope is fixed before you commit.
Rollback criteria agreed
Launch day has a known duration and a known point of no return, decided in advance rather than in the moment.
We stay afterwards
Most of our clients are still with us years later. Launch is the midpoint, not the delivery.
Brands we have migrated
Trunki
Trunki moved from Magento to Shopify Plus, with a configurator for the custom, one-off ride-on designs the brand is known for. We have managed the store since.
Chicco
Chicco moved off Salesforce Commerce Cloud onto Shopify. The same team has handled landing pages and maintenance since launch.
Trunki
Trunki moved from Magento to Shopify Plus, with a configurator for the custom, one-off ride-on designs the brand is known for. We have managed the store since.
Chicco
Chicco moved off Salesforce Commerce Cloud onto Shopify. The same team has handled landing pages and maintenance since launch.
Dekoni Audio
Big Shoes
Halcyon Nights
Migration questions
The questions that decide whether a replatform is worth starting. Anything specific to your data is what the free audit answers.
How long does a Shopify Plus migration take?
Typically 10 to 16 weeks from discovery to launch. Catalogue size, the number of integrations to rebuild and the number of storefronts are what move that number, not the source platform alone.
Will we lose search rankings when we migrate?
Not if redirects are mapped before launch. We build the redirect map from your live URL export and Search Console data, then crawl staging against it so every indexed URL resolves on day one.
Can we migrate in phases?
Yes. Multi-storefront retailers usually launch one region or brand first and use it as the template for the rest, which contains risk and makes every later launch faster.
What does a Shopify migration cost?
It is quoted after a scoping call rather than from a price list, because cost is driven by catalogue size, integrations and storefront count. You get a fixed-scope quote in writing before any contract is signed.
Do we need Shopify Plus, or is Shopify enough?
Plus earns its cost when you need checkout customisation, multiple storefronts, B2B, or higher API limits. Plenty of brands migrate onto standard Shopify first and upgrade when one of those becomes true.
After the migration
Replatforming is the start of the work, not the end of it. The three things brands usually want next are speed optimization, ERP integration and, for anyone selling across borders, Shopify Markets. Ongoing development runs as a retainer.
NEXT STEP
Migration scoping call
Bring your catalogue size, integrations and storefront count. You leave with a phased plan and a timeline in writing.