Migration field notes.
Viewpoints and lessons from the field on industrial data migration: classic pitfalls, methodology and best practices.
- 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
Migration expertise costs between €200,000 and €1M. A fiasco runs into tens, sometimes hundreds of millions. The real question isn't the price of expertise. It's the price of going without it.
Read the article → - LOG_04
Windchill to 3DEXPERIENCE: native tools move your files, not your data
Migrating one PLM to another isn't copying files from one side to the other. It's rebuilding a structure. And that's exactly what native tools can't do.
Read the article → - LOG_03
S/4HANA is not ECC with a new name
Moving to S/4HANA changes the schema under your feet. Migrating your data without understanding that means loading valid content into a model that no longer expects it.
Read the article → - LOG_02
Data audit: the phase everyone overlooks
Before writing a single line of migration code, you have to face the data as it really is. It's the least spectacular phase, and the most decisive.
Read the article → - LOG_01
Why so many ERP migrations fail in production
Migrations almost never derail because of the target system. They derail because of the source data, and the moment its true state is discovered.
Read the article →