On this page
E-commerce sites combine content, catalog data and transactions. Each has different migration needs, and mistakes in the transactional parts are felt immediately by customers. Careful planning keeps the shop trading through the change.
Decide what kind of platform comes next
The first decision is architectural. Options include a hosted commerce platform, a self-hosted commerce application, or a modern front end connected to a commerce backend through an API. Each brings different maintenance, flexibility and cost profiles. Choose based on catalog size, how products are configured, required integrations and who will operate the store day to day.
Inventory the catalog
Document product types, attributes, variants such as size or color, pricing rules, stock tracking, categories and collections, and product images. Note any custom fields used for specifications or downloads. Count products and variants so import approaches can be planned realistically.
Customers and accounts
Decide whether customer accounts will move. As with any user migration, passwords generally cannot be transferred directly, so customers may need to set a new password. Communicate this clearly. Keep only the customer data you need and handle it according to your privacy obligations.
Order history
Customers and staff may expect to see past orders. Decide whether historical orders move into the new platform, are archived elsewhere for reference, or remain available in the old system for a period. Accounting and tax record-keeping requirements may influence this choice; ask whoever manages those records.
Payment gateways
Payment gateways connect through credentials, webhooks and return URLs. Plan to configure the gateway for the new platform in test mode first. Confirm how refunds, partial captures and failed payments are handled. Do not copy card data; reputable gateways handle stored payment methods through tokens tied to their own systems, and moving those requires gateway involvement.
Tax, shipping and discounts
Tax rules, shipping zones and rates, and discount codes are often configured in detail. Export or document them, then rebuild and test with real scenarios: different destinations, product combinations and active promotions.
Transactional emails
Order confirmations, shipping notifications and password resets need templates and reliable delivery. Check sender authentication records and test that emails arrive and render correctly.
SEO for product and category pages
Product and category URLs often attract search traffic. Keep paths consistent where possible, and redirect individual products and categories when they change. Discontinued products need a sensible destination, such as a replacement product or category.
Test complete purchase journeys
Before launch, run full journeys in test mode: browse, add to cart, apply a discount, check out, pay, receive confirmation and process a refund. Repeat on mobile. Test inventory updates and any integration with fulfilment or accounting tools.
Launch at a quiet time
Choose a period with lower order volume. Pause or coordinate marketing campaigns around launch, and make sure someone can respond quickly to customer questions.
A steady approach
E-commerce migrations reward patience. Moving catalog content and design is the visible part, but payments, orders and operations are where trust is earned. Planning them deliberately keeps the store open for business throughout. Write each of these areas into the project plan with an owner and a test, and the launch becomes a checklist rather than a gamble.
Turn this topic into a project plan
Use these supporting guides to prepare the details for your integrations discussion.
Put this into practice
Planning a move like this?
Follow the analyze, plan, rebuild, verify and launch stages of a migration project.