A CMS migration checklist for e-commerce sites is a step-by-step plan for moving products, customers, orders, and content to a new Content Management System (CMS) without breaking sales. It covers data mapping, redirects, payments, shipping, taxes, and testing before launch. Use it to decide scope, assign owners, and set the order of work. A store has more moving parts than a blog, so missed steps can block checkout or hide products from search.
Official resource:
- Follow Google's official site move and migration guidance — Verify redirect mapping, sitemap updates, and monitoring steps to preserve search rankings during replatforming.
Table of Contents
- What should you inventory first?
- How do you move product and customer data safely?
- How do you protect URLs and storefront functions?
- What should you test before launch?
- How do you launch and watch the new store?
- Frequently Asked Questions
What should you inventory first?
List everything the new CMS must carry or replace. Include product types, variants, prices, images, categories, pages, blog posts, customer accounts, order history, coupons, reviews, and forms.
Map each item to a field in the new system. Note where fields do not match, such as bundled products, subscriptions, custom attributes, or wholesale pricing. These gaps drive development time.
- Catalog, content, customers, orders, and redirects
- Payment gateways, shipping rules, tax settings, and emails
- Integrations: inventory, accounting, CRM, help desk, and marketing tools
- Roles, permissions, and publishing workflows
How do you move product and customer data safely?
Export clean data before you import anything. Remove duplicates, fix missing SKUs, standardize options, and confirm which history must move for returns and warranties. Run a small trial import, then check counts, images, prices, stock levels, and customer records.
Passwords usually cannot transfer directly, so plan a reset flow for returning shoppers. Keep the old store readable until the new order and refund lookup is confirmed. Staff need access to past invoices during the changeover period.
How do you protect URLs and storefront functions?
Record every live URL, including products, categories, landing pages, and PDFs. Build one-to-one redirects from old addresses to matching new addresses, and keep URL structure stable where possible. Recreate search, filters, sorting, related products, and checkout steps in the new theme.
Test coupons, gift cards, guest checkout, account login, shipping estimates, tax calculation, and payment approval and failure paths. Check page speed, mobile layout, image sizes, and structured product data. Small losses in speed or clarity can reduce add-to-cart actions.
What should you test before launch?
Use a private staging copy with real data. Place test orders with different products, addresses, shipping speeds, taxes, and payment methods, then refund one to confirm the full cycle.
Ask staff to pack, ship, return, exchange, and edit an order. Confirm emails send correctly for receipts, shipping notices, password resets, and abandoned carts.
- Checkout on desktop and phone
- Search terms, misspellings, filters, and out-of-stock items
- Forms, logins, address changes, and order tracking
- Backups, rollback steps, and who can pause launch
How do you launch and watch the new store?
Freeze catalog changes during final migration, then move the latest orders and inventory. Point the domain to the new CMS during low traffic and confirm payments, redirects, and tracking the same day. Watch checkout completion, payment errors, 404 pages, site search with no results, and support contacts for two to four weeks.
Fix broken redirects, missing images, and wrong tax or shipping rules first. Keep daily backups and a written rollback plan until sales and fulfillment look stable. Assign one owner to triage issues and approve fixes.
Frequently Asked Questions
Should we migrate order history?
Migrate enough history to handle returns, exchanges, warranties, and tax records. Archive the rest where staff can still search it.
What happens to customer passwords?
Most platforms store passwords in a form that cannot move directly. Plan for customers to create a new password on first login.
How long should redirects stay live?
Keep product and category redirects in place long term. Old links appear in bookmarks, emails, and search results for many months.
