You didn’t choose to migrate your online store. Your platform chose for you — the shutdown email arrived, or the “upgrade” quote came back at $40,000, or the app you depend on stopped updating and nobody at support is answering. Now you’re staring at years of products, customers, and hard-won Google rankings, wondering how to migrate your online store platform without lighting the business on fire. This is the honest version — what actually moves, what always breaks, and how to keep the phone ringing on launch day.
When to migrate an online store platform: the five real signs
Migration is expensive and disruptive. Don’t do it because a competitor did. Do it when one of these is true:
- The platform is dead or dying. Magento 1 hit end-of-life in June 2020 and hasn’t received a security patch since. If your store runs on unsupported software, every month you wait is another window for a payment-skimmer attack.
- The vendor is shutting the doors. Niche SaaS builders — print-shop tools, industry-specific carts, small platform vendors — get sold off or wound down regularly. When you get an email with a migration deadline in it, that IS the sign.
- Ownership matters now. You’ve grown to the point where the platform holds you hostage — you can’t touch your data, you can’t hire someone outside their partner list, and every custom feature costs $2,000 in “app connectors.”
- The monthly bill is eating the margin. Add up your platform fees, transaction fees, and required apps. If the total is north of $500/month and you’re doing under six figures in revenue, the math has stopped working.
- You can’t build the thing your business actually needs. A custom “design your own product” tool, a bilingual storefront, a wholesale portal. Every SaaS platform has a wall — when your business hits it, that’s the wall.
If none of those apply, don’t migrate. Fix what’s broken, renegotiate the bill, and put the migration energy into marketing.
The five things that always come with you
Every store migration — regardless of source or destination — moves the same five buckets. Miss one and you’ll feel it for a year.
| Bucket | What moves | Where it usually breaks |
|---|---|---|
| Products | SKUs, variants, images, descriptions, categories, inventory | Variant structures don’t map 1:1 across platforms; images lose alt text and lazy-loading behavior |
| Customers | Names, emails, addresses, order history | Passwords are one-way hashes and can’t move — every customer resets on first login |
| Orders | Historical orders, statuses, invoices, refunds | Order numbering resets; support requests referencing old order IDs get confused |
| Reviews | Star ratings, written text, verified-purchase status, photos | Verified-purchase badges vanish unless the migration tool maps them explicitly; conversion drops noticeably |
| SEO & URLs | Every URL Google has indexed, plus meta titles and descriptions | Missing 301 redirects wipe out years of ranking overnight |
The last bucket is where most migrations quietly bleed revenue for months afterward.
The 301 redirect map is the whole SEO story
Every URL Google has indexed on your old store needs a 301 redirect pointing to the equivalent URL on the new store. Not a homepage redirect. Not a “similar category” redirect. The specific product page, mapped to the specific new product page. Skip this and you’ll watch traffic tank the day after launch and stay tanked for six months while Google reindexes from scratch.
The mechanics are boring and non-negotiable:
- Crawl the old store with Screaming Frog or a similar tool and export every live URL.
- Build a spreadsheet: old URL → new URL, one line per product, category, and content page.
- Load those redirects on the new site BEFORE you flip DNS. On WooCommerce this is a plugin (Redirection is the standard). On Shopify it’s the URL Redirects tool in admin.
- Keep the old sitemap accessible for at least 30 days so Google can crawl through and confirm the redirects.
Add 30–50% padding to your timeline estimate for this step alone. Every migration finds URL edge cases nobody remembered — old blog posts, archived campaigns, that PDF someone linked in a 2019 press release.
A real migration: InkSoft to WooCommerce
Last year we replatformed The Hat Store by Cypress — a 28-year-old embroidery shop in South Florida — off InkSoft (a SaaS built for garment decorators) onto WooCommerce. Over 230 products came across, plus a custom design-your-cap tool that InkSoft used to charge a monthly fee for and that the client now owns outright. Monthly platform costs dropped by nearly half.
Nothing about the migration was glamorous. The interesting parts were the redirect map, the variant-structure translation for hat colors and sizes, and running both systems in parallel for a week while we verified orders were flowing correctly. That’s the shape of every real migration — boring, methodical, heavily front-loaded on discovery. The drama only shows up when someone tries to skip a step.
Timelines and cost, honestly
For a typical small-business store — under 500 SKUs, one or two integrations, no wholesale portal — a proper migration takes 6–10 weeks and costs $8,000–$20,000 depending on how clean the source data is. Magento 1 to Magento 2 migrations tend to run 3–6 months for standard stores and 9–12 months for anything complex. Anyone quoting you two weeks and $2,000 for a full-catalog migration is either using a script that skips reviews and redirects, or is planning to send a change-order the day after launch.
Our own WooCommerce development and migration work starts at $5,000, which covers small catalogs (roughly 50 products) and a clean cutover. Bigger stores are quoted after we look at the export — the honest number depends on data shape, not a vendor pricing page.
When it’s genuinely fine to just move to Shopify
Not every store needs a hand-coded WooCommerce build. If your catalog is simple, you don’t need custom features, and you’d rather pay a monthly platform fee than think about hosting or updates, Shopify is a legitimate answer. That’s what we recommend when the shoe fits — the honest test is whether you’ll ever need something Shopify won’t let you build. If the answer is no, keep it simple. If the answer is yes (bilingual storefronts, complex product configurators, wholesale portals, membership gates), you’ll hit the wall inside a year, and the second migration is always more painful than the first.
The one thing that saves every migration
Run both platforms in parallel during cutover. Do not flip DNS on Monday morning with the old store already dark. Keep the old store live on a subdomain for a week or two while the new store takes production traffic. Compare order counts daily. When you’re satisfied the new store is capturing everything the old one did, then — and only then — turn the old one off. Rushing the kill switch is where migrations lose real revenue.
Migrating your online store platform is one of those projects where the difference between “invisible” and “disaster” is entirely process. If you’re staring at a shutdown notice, an unsupported platform, or a bill you can no longer justify — book a free 20-minute call and we’ll tell you honestly whether a migration is worth it right now, what it’ll take, and whether we’re the right team to do it. Sometimes the answer is “not yet.” That’s fine too.