Moves we know by heart
Magento to Shopify
The most common move: catalogue, customers, orders and URL structure rebuilt.
Magento 2Shopify301sWooCommerce to Shopify Plus
For stores outgrowing plugins and hosting, with B2B and multi-store needs.
WooCommerceShopify PlusBigCommerce to Shopify
Products, variants and metafields mapped, apps replaced one for one.
BigCommerceShopifySalesforce Commerce Cloud to Shopify Plus
Large catalogues and custom checkout logic, moved in phases.
SFCCShopify PlusPhasedShopify to WooCommerce
Leaving Shopify for code and hosting you control: apps to plugins, URLs redirected.
ShopifyWooCommerce301sCutover night
Freeze, final export, delta sync, DNS switch and smoke tests, in order.
FreezeDelta syncDNS
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.
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.
| 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. |
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.
Rehearsed, then repeated
The real run has to work first time, so we follow these rules.
- Scripted end to endEvery export and import is a script, so the test run and the real run are the same run.
- Idempotent loadsRecords carry their old ID, so a re-run updates instead of duplicating.
- Redirects testedThe 301 map is checked against the crawl before DNS moves.
- Rollback readyThe old store stays intact and switchable until you sign off.
# 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
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.
Organic traffic drops after launch
Orders lost on the night
Integrations stop working
Customers locked out
Subscriptions and gift cards
Slower store after the move
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 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.
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.
Design
Adapting a ready theme versus building one for your brand.
Catalogue shape
Bundles, wide variants, custom fields. Shape matters more than size.
Languages and regions
Each store view, language or currency adds mapping and URL work.
URL history
Old stores with years of renamed products have more redirects to map.
Archiving before we start
Disabled products, unused attributes and old test orders left behind cost nothing to migrate.
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.
Migration budgets, fixed up front
Typical ranges. Your fixed quote follows the free audit, and nothing is billed before you agree it.
Standard move
from $15k6–8 weeks
- Up to 5,000 products
- Customers and order history
- Every 301 redirect mapped
Full replatform
from $28k8–10 weeks
- Theme rebuilt for the new platform
- Apps replaced one for one
- Two weeks of post-launch watch
Phased migration
Custom quoteScoped after the audit
- Large catalogues or multiple stores
- Custom checkout logic rebuilt
- Phased cutovers by region or brand
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.
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.
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.
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.
Ready to leave
your old platform?
Tell us where you are moving from. An engineer replies within one business day with the risks and a rough plan.
What happens next
- An engineer replies Within one business day, by email.
- A free 30-minute audit On a call with an engineer.
- A fixed quote It follows the audit. Nothing is billed before you agree it.