A safe ecommerce replatforming runs on four buckets of checks: migrate the catalog with variants and inventory intact, move customer and order data, 301-redirect every URL, and verify checkout and SEO before you flip the domain. Skip any bucket and you lose either revenue or rankings.
Replatforming a store is higher stakes than a content migration because product pages carry rankings, and checkout carries cash, at the same time. A missed redirect drops a ranking; a broken tax rule drops a sale. This checklist follows the website migration service so nothing slips.
The full replatforming checklist
Work these in order. Each row is a gate you clear before moving to the next phase.
| Phase | Task | Done when |
|---|---|---|
| Catalog | Export products with variants, SKUs, images | Top 30 sellers match source line by line |
| Catalog | Rebuild collections and categories | Every product sits in its intended collection |
| Data | Migrate customer accounts | Login and address book work on 5 test accounts |
| Data | Migrate order history | Past orders visible in customer accounts |
| URLs | Build one-to-one 301 redirect map | Every indexed URL has a new-domain match |
| URLs | Load redirects before launch | Old URLs return 301, not 404 |
| Checkout | Configure payment, shipping, tax | 3 test orders complete across regions |
| SEO | Copy meta titles and descriptions | Top 50 pages match source meta |
| SEO | Submit sitemap, request indexing | New sitemap live in Search Console |
| Launch | Monitor 404s and revenue by page | Zero unexpected 404s after 14 days |
1. Migrate the catalog without silent drops
The catalog is the store. Move it first and verify it hardest.
- Export every product with all variants, SKUs, prices, and inventory counts.
- Confirm images uploaded at full resolution with alt text preserved.
- Rebuild collections, since category structures rarely map one to one between platforms.
Check the top 30 sellers against the source line by line. Import tools drop variants silently, and a missing size or color costs a sale the moment a customer looks for it. For a platform comparison, see website migration service.
Variants are where the silent losses concentrate. A product with five sizes and four colors is 20 buyable combinations, each with its own SKU, price, and stock count. Importers routinely flatten that to a single variant or drop the out-of-stock combinations entirely. Spot-check the combinations, not just the parent product. Confirm that a size medium in navy shows the right price and the right inventory number, then repeat across your best sellers. The store looks fine at the category level and breaks at the exact combination a customer wants.
2. Move customer and order data
Rankings get the headlines, but customer data drives repeat revenue.
- Migrate customer accounts so existing buyers can log in without resetting.
- Move order history so customers see past purchases and can reorder.
- Confirm saved addresses and payment tokens transfer where the platform allows.
Test 5 real customer accounts end to end: log in, view past orders, update an address. A customer who cannot log in on day one often does not come back to try again.
Order history is worth more than it looks because it powers reorders, returns, and support. A customer who wants to reorder a consumable, claim a warranty, or start a return needs to see the original order on the new platform. If that history does not migrate, every one of those requests turns into a support ticket your team has to research by hand. Migrate the orders, then confirm a sample of them display the right line items, totals, and dates in a real customer login, not just in the admin export.
3. Build a one-to-one redirect map
Every indexed URL on the old store needs a 301 to its exact match on the new one.
- Crawl the live store to capture every product, collection, blog, and policy URL.
- Pull Search Console data so you know which URLs earn clicks and sales.
- Map each old URL to its new-domain equivalent, one for one, no homepage funneling.
Load the redirects before the domain flips so they fire at launch. Deeper rules on chains and status codes live in 301 redirect best practices. A product URL that 404s loses both its ranking and its ad landing page at once.
Ecommerce platforms rarely share a URL structure, which makes the map harder than a content site. One platform puts products under a products path, another nests them under their collection, a third appends a numeric ID. Pattern-match where you can with rules that rewrite whole folders, then handle the exceptions by hand. Pay special attention to any URL used as a paid-ad landing page. A 404 there does not just drop a ranking, it burns ad spend on a dead page until someone notices.
4. Configure and test checkout
A store that ranks but cannot take payment is worse than no move at all.
- Set up payment gateways, shipping zones, and tax rules for every region you sell to.
- Place 3 test orders across product types and shipping destinations.
- Confirm order confirmation emails, inventory decrement, and receipts all fire.
Test the failure paths too: a declined card, an out-of-stock item, a discount code. Checkout bugs hide in the edge cases, and they surface as abandoned carts you never get told about.
Run the tests as a real buyer would, on a phone as well as a desktop, since most storefront traffic is mobile. Push a real card through to a real charge, then refund it, so you know the money actually moves and reverses. Check that tax calculates correctly for a taxed region and a tax-exempt one, that shipping shows the right rate at the right cart weight, and that a discount code applies and stacks the way you intend. A checkout that works for the happy path and fails on a declined card still loses the sale.
5. Verify SEO before launch
Rankings transfer only if the signals move with the pages.
- Copy meta titles and descriptions for your top 50 pages exactly.
- Confirm canonical tags point at the new-domain URLs.
- Preserve structured data for products so rich results survive the move.
Keep the new store blocked from indexing on staging until launch. Indexing a staging copy creates duplicate content you then have to unwind while traffic is already at risk.
Product structured data earns the rich results that pull clicks: the price, the star rating, the stock status shown right in the search listing. Those are easy to lose in a replatform because each platform builds the markup differently and some strip it unless a theme or app adds it back. Validate the markup on a sample of product pages before launch and confirm price, availability, and review fields all populate. A product that keeps its ranking but loses its rich result still loses clicks to the competitor that kept theirs.
6. Launch and monitor by revenue, not just rank
Launch during a slow sales window, then watch the metrics that catch redirect gaps.
- Point the domain at the new store; expect a DNS settling window, covered in how long does DNS propagation take.
- Submit the new sitemap and request indexing on top 20 product and collection pages.
- Track 404s daily and revenue by landing page for the first 14 days.
Watch revenue per landing page, not only rankings. A ranking report can look fine while a broken checkout redirect costs sales with nothing in the report to flag it. Reindexing runs 2 to 6 weeks; patch any missed redirect the day it shows up.
A pre-launch dress rehearsal
The checklist tells you what to build; a dress rehearsal proves it works before real customers arrive. Run a full dry run on the new store while it is still on its temporary URL.
- Place test orders across product types, shipping regions, and payment methods.
- Confirm each order records, decrements inventory, and sends a confirmation email.
- Run the failure paths: a declined card, an out-of-stock item, an expired discount code.
- Process a refund on one test order so the reverse path is proven too.
- Log in as five migrated customers and confirm past orders and saved addresses appear.
The rehearsal catches the faults a static checklist misses: a tax rate off by a decimal, a shipping zone with no rate, a confirmation email that never sends. Each of these is a quiet failure that looks fine on the storefront while it silently costs a sale, which is why a real order beats a glance at the settings screen.
The first two weeks after cutover
Launch is the start of the risk window, not the end. The first fortnight tells you whether the redirect map and checkout held.
| Window | Watch | Act if |
|---|---|---|
| First hour | A live order completes end to end | Any step fails, roll back |
| First day | 404 report, top-product revenue | A ranked product 404s, add the redirect |
| First week | Search Console coverage, checkout errors | Coverage drops or orders fail silently |
| Two weeks | Revenue by landing page vs baseline | A specific page underperforms its pre-move level |
Compare revenue per landing page against the same window before the move, because a broken redirect on one product hides inside a healthy daily total. A single top seller returning 404 loses real money while the overall number still looks fine.
Where replatforming projects slip
A few failure points recur on store moves. Confirm each explicitly rather than assuming the import handled it.
- Variants dropped silently on import, leaving a size or color unbuyable.
- Product reviews left behind, removing the social proof that drove conversions.
- Payment gateway still in test mode at launch, so orders never capture.
- Collections rebuilt but products not assigned, leaving category pages empty.
- Images left hotlinked to the old platform, which break when that account closes.
None of these throw an obvious error. The store looks live while a variant is missing or a gateway sits in test mode, which is why each one needs a deliberate check against the source before the domain flips.
Rollback and contingency planning
Every replatform needs a way back. Before you flip the domain, write down the exact steps to point it back at the old store and keep that old store running and paid for through the settling window. If checkout breaks in a way you cannot fix within an hour of launch, reverting is cheaper than bleeding sales while you debug.
Decide the rollback triggers in advance so nobody has to argue about them under pressure. Reasonable triggers are checkout failing for a whole payment method, revenue per session dropping by a set percentage against the prior period, or a spike of 404s on top product URLs that you cannot patch quickly. Assign one person to make the call and give them the authority to make it. A planned rollback executed calmly beats a scramble every time, and knowing the exit exists lets the team launch with less risk.
Related terms
You may see this topic described with related searches like ecommerce migration, ecommerce replatforming agency, ecommerce replatforming consultant, ecommerce replatforming guide, and ecommerce replatforming services. Those phrases are useful when they clarify what the reader needs next, but they should still point back to one clear plan.
Related searches such as ecommerce site migration checklist, ecommerce website replatforming, replatforming ecommerce, replatforming website, and website replatforming are useful when they clarify what the reader needs next. They should support the same plan rather than pulling the page in several directions at once.
Related searches such as what is replatforming are useful when they clarify what the reader needs next. They should support the same plan rather than pulling the page in several directions at once.
Frequently asked questions
What is the biggest risk in ecommerce replatforming?
Losing product rankings to missed 301 redirects, and losing sales to broken checkout. Both carry revenue, so a store move is higher stakes than a content migration. A one-to-one redirect map and full checkout testing address the two biggest risks directly.
How long does an ecommerce replatform take?
A mid-size store takes 4 to 8 weeks: catalog and data migration, redirect mapping, checkout setup, and testing. Reindexing after launch adds 2 to 6 weeks before rankings and revenue fully settle.
Should I migrate customer passwords?
Most platforms cannot transfer hashed passwords between systems, so customers reset on first login. Migrate the accounts, addresses, and order history, then send a clear password-reset prompt at launch so returning buyers are not surprised.
How do I keep rankings when replatforming?
Redirect every indexed URL one to one with 301s, copy meta and structured data exactly, submit the new sitemap, and monitor 404s. Rankings transfer when signals move with the pages and every old URL has a permanent path to its new home.
When is the best time to launch a store move?
During your slowest sales window, and never right before a peak season. Launching in the quiet weeks gives you room to catch redirect gaps and checkout bugs while fewer sales are at risk. Flipping a store the week before a major sale stacks the reindexing dip on top of your highest-revenue days.
Do I need to keep the old platform running after launch?
Yes, for the settling window. Keep the old store live and the old domain redirecting for at least 12 months so backlinks and bookmarks keep working. Keep the old platform itself accessible long enough to confirm all data migrated and to support any rollback, then decommission it once the new store is proven.
Does Wix have an eCommerce platform?
Yes, Wix has ecommerce features for product catalogs, checkout, payments, and basic store management. It can fit smaller stores, while larger catalogs or complex operations often need a more specialized ecommerce platform.
What is an ecommerce platform?
An ecommerce platform is the system that runs products, checkout, payments, inventory, and order management. In a replatforming project, the SEO risk comes from changing URLs, templates, product data, and tracking at the same time.
Which ecommerce platform is most used?
The most-used ecommerce platform depends on how you count it: Shopify is common for dedicated online stores, WooCommerce is common across WordPress sites, and Amazon dominates marketplace selling. For a migration, choose by catalog needs, checkout, integrations, SEO control, and operating fit instead of popularity alone.
What is the #1 ecommerce platform?
An ecommerce platform is the system that runs products, checkout, payments, inventory, and order management. In a replatforming project, the SEO risk comes from changing URLs, templates, product data, and tracking at the same time.
Get help with your replatforming
A store move puts rankings and revenue on the line together, so a checklist beats memory every time. Start with the website migration service. For the full pre-launch review, read the website migration checklist, and if you are still choosing a platform, see website migration service.