Prepare a store-data migration to ShopTill-e
A migration includes more than a product CSV. Agree which records, files and existing website addresses must be preserved before moving the catalogue.
Define the scope
- Record the source system, version, shop/store views and intended ShopTill-e account.
- List products, SKUs, variants/options, categories, prices, tax/weight fields, stock by location and images/files that need moving.
- Review customer and order history, balances, vouchers, content pages and integrations separately. A product import does not establish that these will transfer.
- Keep original exports and a checked source backup. Record counts and representative difficult examples.
- Map source columns and identifiers to the current ShopTill-e formats with support.
Prepare a controlled sample
Include a simple product, a variant product, a leading-zero identifier, category paths and an image example. Confirm matching, blank/omitted values, categories and update scope before any import. Plan the specific recovery process and compare actual results with the original source.
Example: existing category work
If staff have already organised ShopTill-e categories, do not overwrite that work with an older source export. Agree whether the migration should preserve, link or replace those relationships before preparing the file.
Plan the final move
Agree when source data will stop changing, how final differences will be handled and who checks the result. Retain old-to-new page addresses and arrange redirects. Check storefront, till, pricing, stock and connected-service journeys before switching customers to the new shop.
If a result differs
Keep the original record, exact working file, matching choice and actual result. Investigate the scope before importing the full catalogue or repeating a destructive replacement.
Catalogue CSV preparation · Keep identifiers exact · Magento/Adobe Commerce product export.
