Editorial draft available to read. Factual and language review is pending. Examples are illustrative.
Decision and method
Prepare a table linking each source field, meaning, destination, transformation and owner. Include required status, length, allowed values and behavior when information is missing. Do not infer equivalence from the name: status, customer and amount can represent different concepts depending on each system's process and point in the update cycle.
Illustrative example
Illustrative example: the CRM uses won to mean commercial acceptance, while the ERP uses confirmed after validating the order. Mapping those states directly would skip a required review. The mapping creates an order awaiting validation and preserves commercial acceptance in a separate field visible to the team responsible for delivery.
Acceptance check
Review ordinary examples, length boundaries, characters and unfamiliar categories with owners of both processes. Check whether transformations lose detail and how that loss is explained. Accept when every critical field has a demonstrated mapping, rejections are understandable and no default value disguises missing information that requires a human business decision.
Key takeaways
- Map business meanings and process states as well as field names and formats.