# Ecommerce platform migration

URL: https://intelligizedigital.com/services/platform-migration/
Updated: 2026-10-23
Summary: Store moves between Shopify, WooCommerce, BigCommerce, Magento and Wix with products, customers, orders and redirects intact. 6 to 10 weeks, from $15k.

## Change platforms. Keep every order.

We move your catalogue, customers, order history and every old URL to Shopify, Shopify Plus, WooCommerce or BigCommerce, rehearse the cutover on a test store, and switch over in a short freeze window with a delta sync straight after.

Book a free 30-min audit [See every route](https://intelligizedigital.com/migrations/)

- **6–10 wks** From kickoff to cutover night, test migration included.
- **from $15k** Including every 301 redirect, fixed quote after the audit.
- **1 freeze** A short order freeze, then a delta sync of anything new.
- **2 crawls** Before and after, so you can see nothing went missing.

Use cases

### Moves we know by heart

Popular routes

### Pick your route, either direction

Each route has its own page: what maps, what changes, and how cutover night runs. [See every from → to pair](https://intelligizedigital.com/migrations/).

[WooCommerce Shopify Plugins to apps, WordPress URLs redirected](https://intelligizedigital.com/migrations/woocommerce-to-shopify/) [Magento Shopify Configurables to variants, .html URLs kept](https://intelligizedigital.com/migrations/magento-to-shopify/) [BigCommerce Shopify Custom fields to metafields, apps matched](https://intelligizedigital.com/migrations/bigcommerce-to-shopify/) [Wix Shopify Limited export, planned step by step](https://intelligizedigital.com/migrations/wix-to-shopify/) [Shopify Shopify Plus Same store, checkout and B2B rebuilt](https://intelligizedigital.com/migrations/shopify-to-shopify-plus/) [Shopify WooCommerce Apps to plugins, hosting you control](https://intelligizedigital.com/migrations/shopify-to-woocommerce/) [Shopify BigCommerce Apps checked against native features](https://intelligizedigital.com/migrations/shopify-to-bigcommerce/) [WooCommerce BigCommerce Plugin upkeep swapped for a hosted platform](https://intelligizedigital.com/migrations/woocommerce-to-bigcommerce/) [BigCommerce WooCommerce Custom URLs to WordPress permalinks](https://intelligizedigital.com/migrations/bigcommerce-to-woocommerce/) [Magento BigCommerce Attribute sets and store views mapped](https://intelligizedigital.com/migrations/magento-to-bigcommerce/) [Magento WooCommerce Attribute sets to shared attributes](https://intelligizedigital.com/migrations/magento-to-woocommerce/) [Wix WooCommerce Design rebuilt, every Wix URL redirected](https://intelligizedigital.com/migrations/wix-to-woocommerce/) [All routes Every from → to pair, in one matrix](https://intelligizedigital.com/migrations/)

Decision guide

### Which platform should you migrate to?

We migrate stores onto all four, so we don’t need you to pick one in particular. These are the trade-offs we talk through on the audit call. If none of them is a clear win, staying put is a real option too.

Use this as a starting point. Plan features change, so we check current details for your store in the audit.
| What matters to you | Shopify | Shopify Plus | WooCommerce | BigCommerce |
| Least upkeep | Hosted, updated for you. Apps add features. | Same, with more control over checkout. | You or your agency update plugins and hosting monthly. | Hosted, with more built in so fewer apps. |
| Content-heavy site | A simple blog. Fine for news and short guides. | Same as Shopify. | WordPress is the strongest editor of the four. | A basic blog, or keep WordPress for content. |
| B2B and trade pricing | Wholesale apps. | Native B2B: companies, catalogs, payment terms. | Plugins for roles, pricing and quotes. | Customer groups and price lists; B2B Edition for more. |
| Custom checkout logic | Limited to settings and apps. | Checkout extensions and Functions. | Anything, in PHP, on your server. | Checkout options and its checkout SDK. |
| Monthly cost shape | Plan plus apps. | Higher plan, fewer apps. | Hosting plus plugins plus upkeep time. | Plan tied to sales volume, fewer apps. |

What’s included

### Everything a clean move needs

Every migration ships with these eight things, so cutover night runs from a checklist.

**Data audit** Every entity, field and custom attribute listed before we write a script.

**Field mapping** Old fields to new, including metafields and tags, signed off by you.

**Test migration** A full rehearsal on a staging store you can click through.

**Redirect map** Every old URL mapped to a 301, products, categories and content.

**Freeze plan** A short, scheduled order freeze with customer messaging ready.

**Delta sync** New orders and customers since the export, moved after cutover.

**Crawls** Before-and-after crawls compared, so missing pages show up early.

**Hand-over** Admin training and notes on every app and setting we chose.

Under the hood

### Rehearsed, then repeated

The real run has to work first time, so we follow these rules.

- **Scripted end to end** Every export and import is a script, so the test run and the real run are the same run.

- **Idempotent loads** Records carry their old ID, so a re-run updates instead of duplicating.

- **Redirects tested** The 301 map is checked against the crawl before DNS moves.

- **Rollback ready** The old store stays intact and switchable until you sign off.

redirects.csv (excerpt)

```
# old path, new path, status
from,to,status
/mens/shoes.html,/collections/mens-shoes,301
/runner-x2-blue.html,/products/runner-x2?variant=blue,301
/catalogsearch/result/?q=*,/search?q=*,301
/customer/account/login,/account/login,301
/blog/size-guide.html,/blogs/news/size-guide,301
# 31,552 rows in this example, each checked against the crawl
```

Works with

Magento 2 *from* Adobe Commerce *from* WooCommerce *from* BigCommerce *from* Salesforce Commerce Cloud *from* PrestaShop *from* Wix *from* Shopify *from / to* Shopify Plus *to* WooCommerce *to* BigCommerce *to* Matrixify *import* Screaming Frog *crawl* Google Search Console *seo* Cloudflare *dns*

Risks

### What can go wrong in an eCommerce platform migration

Most failed migrations fail in the same few ways. These are the ones we plan against on every route.

### High Organic traffic drops after launch

What goes wrong Old URLs 404, page titles change, internal links point nowhere. Rankings slide for months and nobody connects it to the move.

What we do Every indexed URL is mapped to a 301 and tested before DNS moves. Titles and meta are copied where they rank. We compare crawls and watch Search Console for weeks after. More on this in our [technical SEO](https://intelligizedigital.com/services/seo/technical-seo/) work.

### High Orders lost on the night

What goes wrong Orders placed between the final export and the DNS switch land on the old store and are forgotten.

What we do A short checkout freeze at your quietest hour, then a delta sync of anything new. Record counts are compared before we call it done.

### Medium Integrations stop working

What goes wrong ERP, email, feeds, accounting and tracking were wired to the old platform. They fail silently.

What we do Every integration is listed in the audit with its new connection, and tested with real orders on staging. Our [ERP integration](https://intelligizedigital.com/services/erp-integration/) team handles the heavier ones.

### Medium Customers locked out

What goes wrong Password hashes can’t move between platforms, so customers try to log in and fail.

What we do Branded invite emails go out the morning after launch, worded as “we’ve moved”, with support ready for questions.

### Medium Subscriptions and gift cards

What goes wrong Subscriber card tokens and gift card balances don’t export like normal data.

What we do Tokens move only where the payment provider allows it; otherwise subscribers confirm cards once. Gift card balances are re-issued, with an email to holders.

### Low Slower store after the move

What goes wrong A new theme stuffed with apps or plugins loads slower than the old one.

What we do We check Core Web Vitals on staging against the old store before launch. See [speed optimisation](https://intelligizedigital.com/services/speed-optimisation/).

The plan

### From audit to cutover, week by week

- Week 0

#### Audit call

30 minutes on what you sell, what you run and what must not break.

Risk list

- Weeks 1–2

#### Map + quote

Every entity and URL mapped, with a fixed price and a cutover date.

Fixed quote

- Weeks 3–6

#### Build + test run

Theme, apps and a full rehearsal migration on staging.

Staging store

- Weeks 7–9

#### Cutover

Freeze, final export, delta sync, DNS switch and smoke tests.

Live store

- Weeks 10+

#### Watch

Crawl comparison, Search Console checks and fixes.

Crawl report

What drives the price

### What makes a migration cost more, or less

We don’t price by product count alone. These are the things that move a quote, so you can see where your store sits before we talk.

Biggest driver

#### Custom code and integrations

A custom product builder, an ERP sync or unusual checkout logic each need rebuilding on the new platform. Two or three of those can outweigh the rest of the project.

Big

#### Design

Adapting a ready theme versus building one for your brand.

Medium

#### Catalogue shape

Bundles, wide variants, custom fields. Shape matters more than size.

Medium

#### Languages and regions

Each store view, language or currency adds mapping and URL work.

Medium

#### URL history

Old stores with years of renamed products have more redirects to map.

Brings it down

#### Archiving before we start

Disabled products, unused attributes and old test orders left behind cost nothing to migrate.

Brings it down

#### One decision-maker

A named person who can answer questions within a day keeps the rehearsal on schedule.

See the price ranges below. Your fixed quote follows the free audit.

Pricing

### Migration budgets, fixed up front

Typical ranges. Your fixed quote follows the free audit, and nothing is billed before you agree it.

Small catalogue

#### Standard move

from $15k 6–8 weeks

- Up to 5,000 products
- Customers and order history
- Every 301 redirect mapped

Scope this

Most chosen

#### Full replatform

from $28k 8–10 weeks

- Theme rebuilt for the new platform
- Apps replaced one for one
- Two weeks of post-launch watch

Scope this

Large or complex

#### Phased migration

Custom quote Scoped after the audit

- Large catalogues or multiple stores
- Custom checkout logic rebuilt
- Phased cutovers by region or brand

Scope this

Before you hire anyone

### Questions to ask any agency before a platform migration

Ask us these too. Vague answers usually mean there is no real plan behind the quote.

-

#### Will you rehearse the whole migration on a test store first?

The answer should be yes, with a staging store you can click through. A one-shot import on launch night is the riskiest way to move.

-

#### How do you build the redirect list?

Look for a crawl of the old site plus Search Console data, not just the sitemap. Old URLs with backlinks are often missing from sitemaps.

-

#### How will we know nothing went missing?

You want record counts per entity before and after, and a before-and-after crawl you can see.

-

#### What happens to orders placed during the switch?

A short freeze and a delta sync. If they can’t explain how late orders move, they haven’t done it often.

-

#### Which of our apps or plugins will you replace, and with what?

Expect a named list with monthly costs, not “we’ll find equivalents”.

-

#### Who watches the store after launch, and for how long?

Someone named, for a few weeks at least, checking Search Console, the 404 log and real orders.

Questions

### About platform migration

Anything else, ask on the audit call.

Ask an engineer

Not answered here? Ask on the free 30-minute audit call. An engineer replies within one business day.

Book a free 30-min audit [Or email hello@intelligizedigital.com](mailto:hello@intelligizedigital.com)

Quick facts

- **Based in Delhi, India** Working across time zones, with written weekly updates.
- **Fixed quote first** Nothing is billed before you agree it.
- **You own it** The code, workflows and accounts are yours.
- **Stores and ERPs** Shopify, BigCommerce, WooCommerce and Adobe Commerce, with NetSuite, SAP Business One, Odoo and Dynamics 365.

[See all questions](https://intelligizedigital.com/faq/)

### Will we lose SEO rankings?

We map every old URL to a 301 redirect, keep titles and content where they rank, and crawl the site before and after. Some movement in the first weeks is normal; we watch Search Console and fix gaps quickly.

### How long is the order freeze?

Usually a few hours, scheduled at your quietest time. Orders placed after the final export are moved by a delta sync straight after cutover.

### Can customers keep their passwords?

No platform can move hashed passwords between systems. We send customers a branded account-activation email so they set a new password in one click.

### What happens to our apps and integrations?

We list every app and integration in the audit, then replace each with an app, plugin or native feature on the new platform, or rebuild it, including ERP and email connections.

### What if something goes wrong on the night?

The old store stays intact and switchable until you sign off. We rehearse the full cutover on staging first, so the real night repeats a run that already worked.

### How much does an eCommerce migration cost?

Our starting points begin around $15k for a standard move, rising with custom code, integrations, design and catalogue complexity. You get a fixed quote after the free audit.

### Can you migrate a store without downtime?

The store stays online throughout. Only checkout pauses, for a short freeze at your quietest hour, while the final orders move.

### Do you work with stores outside India?

Yes. Intelligize Digital is based in Delhi and works with stores in other countries and time zones, with cutover scheduled for your quiet hours, not ours.

### Should we redesign at the same time as migrating?

Often yes, because the theme has to be rebuilt anyway. If the budget is tight, we can rebuild the current design first and redesign later.

### What happens to our order history?

It moves with the customers, as archived or completed orders depending on the platform, so customers still see past orders and your team can still search them.