data migration
Products, variants, customers, order history and content moved with scripted, repeatable imports — run as many times as rehearsal needs.
$ storesmith build --scale
StoreSmith replatforms stores to Shopify Plus from Magento and WooCommerce, and builds expansion stores, 10k+ SKU catalogues and B2B + B2C on one Plus organisation. Migrated, rehearsed and switched over with a plan for every URL, order and customer.
01 — what we build
A replatform is a data project, an SEO project and an integration project at once. We scope all three.
Products, variants, customers, order history and content moved with scripted, repeatable imports — run as many times as rehearsal needs.
Every indexed URL mapped to a 301, structured data and metadata carried over, and the redirect map monitored after launch.
10k+ SKU catalogues modelled with metafields and metaobjects, loaded and updated with bulk operations instead of one call per product.
One store with Shopify Markets, or separate expansion stores under one Plus organisation — chosen by how different each region's catalogue, pricing and operations really are.
B2B on Plus alongside your retail store: company accounts, catalogues and price lists per segment, payment terms, one inventory.
ERP, PIM, WMS and CRM integrations rebuilt against Shopify's APIs and webhooks, live before cutover — not in a phase two.
02 — how a cutover runs
Rehearsed until the real one is boring. The live switch is the last step of a plan, not the first test of it.
Inventory the old platform: data, URLs, integrations, extensions and the custom logic nobody wrote down. Decide what moves, what's rebuilt and what's retired.
Store, apps and integrations built in sprints. Migration scripts run against the new store on every sprint, so the data is tested as often as the code.
Full dress rehearsals: final data delta, redirect checks, test orders through every payment and fulfilment path. Rollback plan written and timed.
Short content freeze, final delta, DNS switch, live checks. The redirect map and order flow are monitored in the weeks after.
Past orders imported so customers and support see the full record from day one.
Passwords can't move between platforms. We plan the account-activation emails so returning customers know what to expect.
On Plus, sales and catalogue changes can be scheduled with Launchpad, so launch-day changes don't depend on someone clicking at midnight.
03 — when it's right
If your store is small, a straight theme setup and a CSV import may be all you need — and it isn't what we do.
04 — proof
Work is listed by industry and pattern, with figures rounded — the merchants keep their names.
home & living · magento → shopify plus
Replatformed a national home & living retailer — every indexed URL 301-mapped, structured data preserved, redirect map monitored for 90 days. Revenue up double digits the following year.
wholesale distribution · b2b automation
Several legacy storefronts merged into one Shopify Plus store, with automated wholesale price tiers by customer segment and real-time inventory sync.
05 — questions
Yes, by rehearsing the cutover until it's routine. DNS TTLs are lowered well in advance. A final delta sync moves everything that changed since the last snapshot. DNS switches to Shopify while Magento stays up read-only, so any order placed in the overlap is captured in a final pass. Nobody sees a holding page.
Every indexed URL is mapped to a 301, built from crawls, search console exports and server logs, and checked automatically before cutover. Structured data and metadata are carried over, and the redirect map is monitored after launch.
No. Passwords can't move between platforms, so we plan the account-activation emails so returning customers know what to expect. Past orders are imported, so customers and support see the full record from day one.
It depends on how different each region's catalogue, pricing and operations really are. One store with Shopify Markets suits regions that share most of them; separate expansion stores under one Plus organisation suit regions that don't.
06 — start
Tell us where you are now, how big the catalogue is and what's connected to it. An engineer replies with a migration outline, how long and roughly what it costs.