Migration
Land with better data than you left
Lift and shift copies the product data across exactly as it is, mistakes included. Migration as Transformation is the Enterspeed service that changes the data on the way through, so the budget buys a better catalogue rather than a copy of the old one.
- Legacy data moves across in the shape it was already in, so the new system inherits the old problems.
- You correct the same attribute in three systems, and the old structure follows you into the new one.
- The cutover is a single weekend, and everything has to be ready at once.
- When something arrives wrong in the new system, nobody can say which step did it.
- Units and taxonomy are normalised on the way through, and gaps are recorded rather than silently filled in.
- Your old attribute structure is mapped to the new one, so three legacy systems can become one during the migration.
- Categories go live as they become ready, so the business keeps trading and you can pilot one product family first.
- Every record keeps its lineage from source file to published product, so an error traces back to the original intake.
The new system launches with complete records and a lineage from supplier file to published product, so budget goes into the transformation rather than into moving the same data to a new database.
Two ways to migrate
Transform on the way through
The service takes what your legacy systems hold and delivers it in the shape the new one expects.
1Consolidate
2Normalise
3Check markets
4Fill gaps
One version, ready for every market
Illustrative example, not customer data.
Scope
Your destination system stays authoritative
Enterspeed composes and delivers. Your new e-commerce or PIM system owns the published record.
-
During the migration
Prepared for the destination
The service prepares the data, enriches what is missing, and delivers it in the shape the new system requires.
-
At cutover
The destination owns the record
Once a product has migrated, the destination system is authoritative for it. Replatforming to Shopify, Shopify owns the live product. Consolidating into a new PIM, that PIM is the master once the category has cut over.
-
After the migration
The transformation stays in place
Supplier intake keeps being normalised and readiness keeps being checked per channel, so the new system goes on receiving clean records. Your backends stay decoupled and authoritative, and the data quality work is not thrown away when the project closes.
