Keep useful customer history when moving your store
By Stackmodo
Our assisted migration work can preserve readable purchase history and selected incoming links, with a first controlled rollout rather than a one-click migration promise.

October 10, 2026 product update · Limited rollout
Moving a store should not mean losing the information customers rely on. Our latest assisted migration work adds a controlled way to retain readable purchase history, alongside an initial preview of legacy-link preservation.
Preserve the facts of an earlier purchase
The first historical-order release preserves original order numbers, dates, purchased items, totals and recorded payment or shipment facts. Authorized customers can read their own retained history through the existing account experience, with other customers' records kept private.
History should not trigger new activity
Imported historical records are kept separate from active purchase processing. Reading or importing an earlier order does not replay its charge, submit another fulfillment request, send another order notice or reserve current stock. The record explains what happened previously rather than pretending the purchase just took place.
Give selected old links a useful destination
A related migration preview supports configured redirects for selected old product, category, policy and account paths. This helps approved incoming links reach the appropriate destination on the same storefront. The first route-preservation release has been checked on a migration staging site, not rolled out automatically to every store.
Historical-order support is deployed on one selected environment, and legacy-path support remains a controlled migration preview. These are assisted capabilities with source mapping and site-specific verification, not a self-service importer, a guarantee that every legacy field is supported or a promise about search rankings.