# Defining Ecommerce Migration Scope

> Move defining ecommerce migration scope safely by defining scope, testing real journeys and reconciling source and destination records.

- Type: Merchant guide
- Level: Intermediate
- Reading time: About 4 minutes
- Audience: Written for store owners, builders, and designers refining high-performance ecommerce stores.
- Last updated: 2026-11-04
- Canonical page: https://academy.getzenbasket.com/merchant-questions/defining-ecommerce-migration-scope/
- Part of: [Merchant Questions](https://academy.getzenbasket.com/merchant-questions/) on ZenBasket Academy

---

## What you need to know

### What ecommerce data should be migrated?

Migrate the data needed to run the new store, serve customers, meet financial and legal duties, and preserve useful reporting. Classify everything else for archive or approved deletion.

### Should all historical data be migrated?

No. Historical data should move only when it has an ongoing customer, legal, financial, reporting or operational purpose and can be protected appropriately.

### How much order history should be migrated?

Retain enough order history to support customer service, returns, accounting, warranties and applicable recordkeeping requirements. Older records may stay in a searchable archive instead of the live commerce platform.

### Should inactive customers be migrated?

Migrate inactive customers only when there is a continuing purpose and an appropriate permission or legal basis. Do not reactivate marketing or accounts merely because the records were copied.

### Should discontinued products be migrated?

Discontinued products may need to remain as order-history references, support records or redirected pages without becoming sellable products. Define their destination status explicitly.

### Should old promotions be migrated?

Do not migrate old promotions as active offers. Preserve only the history needed for orders, finance, or audit, and verify that expired codes cannot be redeemed.

### Should archived content be migrated?

Migrate archived content when it still supports customers, search demand, records, or internal work. Otherwise retain it in a governed archive or remove it through an approved content decision.

### What should be archived instead of migrated?

Archive records that must remain accessible but do not need live storefront behavior, such as old orders, expired campaigns or superseded content. The archive needs ownership, access controls, retention rules, and a retrieval method.

### A quick store check

Classify one source dataset as migrate, archive or delete and record the business reason, owner and retention rule.

---

## Frequently asked questions

### Is archiving the same as deleting data?

No. Archived data remains retrievable under controlled access; deleted data is intentionally removed under an approved rule.

### Should data be migrated just in case?

No. Every transferred dataset should have a current customer, legal, financial, reporting or operational purpose.

## Related articles

- **Evaluating Ecommerce Platforms for Migration**
- **Ecommerce Product Data Migration**