Migration field notes.
Viewpoints and lessons from the field on industrial data migration: classic pitfalls, methodology and best practices.
- LOG_13
Data migration plan: the four lines everyone leaves out
Four lines to quantify in a migration plan: arbitration time, the delta window, the rollback call, and the targeted iterations and full rehearsals the calendar allows.
Read the article → - LOG_12
Data migration strategy: the decision that is not the cutover
Big bang, phased and trickle describe how you switch over. Another decision shapes the system's working life: carry the source data model into the target, or rebuild for it.
Read the article → - LOG_11
Data migration testing: what a passing test actually proves
An accepted load provides initial technical evidence. Counts, values and business processes complete the four levels of data migration testing.
Read the article → - LOG_10
Legacy data migration: reading meaning nobody wrote down
Use data profiles, source code, reference data and business knowledge to investigate undocumented fields and changing codes before defining migration rules.
Read the article → - LOG_09
SAP data migration: where the standard toolchain stops
Scope SAP migration work against the objects, features and extensions supported by your release. Separate template preparation, configuration, development and business decisions.
Read the article → - LOG_08
Validating a migrated BOM: compare the structure and test the assembly
Validate a migrated BOM with full checks of structures, revisions and effectivity, then targeted CAD resolution and business acceptance tests.
Read the article → - LOG_07
How an asynchronous ETL chain works: optimization and flexibility
Decoupling extract, transform and load supports parallel work and targeted recovery. Throughput, dependencies and replay still need explicit design: a queue does not solve them on its own.
Read the article → - LOG_06
The origins of MigQuest: a failed name, some quests, and a phoenix
Before MigQuest, there was DataMig. And before the phoenix, there was a team that already carried its name. The short story of a brand born from one simple idea: a migration is a rebirth.
Read the article → - LOG_05
The real cost of a failed migration
Revlon, Hershey and the US Navy: three public reports that distinguish lost sales, extra charges and ERP programme costs, then help frame your own risk.
Read the article → - LOG_04
Windchill to 3DEXPERIENCE: verify your migration tool's coverage
Product structures, CAD references, lifecycle states: verify your Windchill to 3DEXPERIENCE migration tool's coverage against real project data.
Read the article → - LOG_03
S/4HANA is not ECC with a new name
S/4HANA changes the data model. Qualifying a migration means checking target constraints, business meaning, relationships and operational processes.
Read the article → - LOG_02
Data audit: the phase everyone overlooks
A migration audit measures source data and delivers a map of risks, dependencies and business decisions to prepare before the migration.
Read the article → - LOG_01
Why so many ERP migrations fail in production
Incomplete audits, narrow tests and difficult corrections: five risks to examine when preparing ERP data migration and production cutover.
Read the article →