Data inventory, mapping and management rules

The strongest migration file is not the largest, but the one in which every column has a declared origin and every destination has a decided meaning.

The truth is in the mapping

Inventory shows what is available; Profiling shows how it is really filled. The mapping connects source and X-ERP target including data type, length, mandatory value, transformation, reference and error response.

From raw stock to controlled import

1. Record system, table/file, owner, deadline, number, format and protection class.
2. Profile null values, unique values, lengths, character sets, value ranges and duplicates.
3. Define business and technical keys as well as old ID to new ID mapping.
4. Document the source, X-ERP target, rule, default value and check criterion for each field.
5. Determine when writing authority switches from the legacy system to X-ERP.

Evidence instead of gut feeling

• No target field receives an unexplained value.
• Keys remain stable across all import runs.
• Mandatory fields have technically approved rules.
• Excluded data is explicitly stated.

The typical breaking points

• Name as the sole key creates incorrect merges.
• Empty values are generally filled with “0” and change their meaning.
• Field lengths or character sets are only noticed after data has been truncated.

This is what you take with you

You have a verifiable map from the legacy system to the X-ERP data set.

Further information / source

Related topics

1. For migration specialists – transferring and optimizing data from third-party systems › Basics
2. For migration specialists – transfer and optimize data from third-party systems › Cleaning, sequence and references
3. For migration specialists – transfer and optimize data from third-party systems › SQL or CSV?

Frequently asked questions