Count more than products
A valid CSV row can still lose a variant, image or business rule.
We inventory products, variants, SKUs, GTINs, categories, translations, images, prices, tax, stock and extension fields.
The register separates portable, transformable and non-portable data. Rejected records remain visible instead of disappearing behind an “import complete” counter.
- Products, variants and identifiers
- Categories, media and languages
- Prices, tax and stock
- Custom fields and rejected records
Separate history from active commitments
An old order is a record. A subscription or open refund is still a promise.
Customers, orders, credit notes, coupons, reviews, gift cards and returns each receive a migration rule. Subscriptions move with their product, customer, payment gateway and renewal schedule.
Payment data is never assumed portable. The provider confirms what can move; otherwise the plan includes a transition or fresh customer authorisation.
- Open orders and refunds
- Coupons, reviews and gift cards
- Subscriptions and renewals
- Customer access and consent
Preserve each product’s commercial identity
Google must find the same product, not merely a page that looks similar.
Every old product, variant, category and guide URL receives an equivalent destination. Products remain reachable through real category links; a crawler does not search the internal catalogue to discover them.
Product, ProductGroup, price and availability data match the page and Merchant Center feed. The new domain is claimed and its product pages can be purchased from before requesting a review.
- Product-level redirects
- Variants with stable URLs and IDs
- Structured data in initial HTML
- Feed and Merchant Center domain aligned
Close one till and open the other
Two stores accepting changes create divergent stock and duplicate orders.
We choose a quiet window, briefly freeze writes, replay the last delta and reconcile orders, stock, customers and queued work.
Test orders cover success, decline, refund, cancellation, partial fulfilment, tax, shipping and customer messages. The rollback plan also states what happens to orders received after cutover.
- One named writer
- Final delta reconciled
- Complete order journey tested
- Rollback includes new orders
Decide before cutover
What migration does your store actually need?
- Catalogue and fields inventoried
- Active commitments isolated
- Product URL plan approved
- Merchant Center prepared
- Orders and refunds tested
- Delta and rollback rehearsed
Official sources