CSV

A good CSV appears simple - that's exactly what makes it testable. Each line remains visible, comparable and connected to a key to the origin.

The truth is in the mapping

The X-ERP import sources use, among other things, UTF-8, defined separators and fixed headers. These technical details must match field mapping, mandatory values ​​and reference order.

From raw stock to controlled import

1. Export an unchanged source version and calculate the file hash and line count.
2. Define UTF-8, delimiter, text delimiter, header, decimal and date format.
3. Keep alt ID and external keys as text.
4. Validate the number of columns, mandatory fields, length, value ranges and foreign keys before importing.
5. Write incorrect lines with reason to a separate, reprocessable file.

Evidence instead of gut feeling

• Leading zeros and special characters are retained.
• Each line has unique key.
• Number of lines before and after processing can be explained.
• The error file and import log together make up the entire inventory.

The typical breaking points

• Automatic type conversion turns item numbers into numbers.
• Semicolon in free text moves columns if quoting is incorrect.
• Error lines are changed manually without correcting the rule.

This is what you take with you

The CSV is a controlled exchange package – readable by humans and deterministic for import.

Further information / source

Related topics

1. For migration specialists – transfer and optimize data from third-party systems › Data inventory, mapping and management rules
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 › Test migration, checksums and acceptance

Frequently asked questions