Source-to-target mapping template
Quick answer
Source-to-target mapping template helps UK SMEs understand what Digital Adaption does, where it fits, and how the process works from first conversation to practical data management, migration, automation or reporting work.
Use this template as the working migration map between old systems and your target ERP, CRM, finance platform or reporting model. A good source-to-target map is more than a list of fields. It captures business decisions, transformation rules, default values, validation checks and the owner who can sign each rule off.
The template is useful before test loads, vendor workshops and cutover planning. It helps stop migration decisions being hidden in emails, spreadsheets or assumptions made by the implementation partner.
Mapping table
| Source system | Source field | Target object | Target field | Rule/default | Validation | Owner | Status |
|---|---|---|---|---|---|---|---|
| Legacy ERP | Customer status | Customer | Account status | Map A/P/I to Active/Prospect/Inactive | No blank status; inactive records reviewed | Sales Ops | Draft |
| Finance | Nominal code | Ledger | Account code | Use new chart of accounts | Trial balance reconciles | Finance | Draft |
| CRM | Lead source | Opportunity | Source campaign | Map free text to controlled list | No unmapped source values | Sales | Needs decision |
What to capture for each field
- Whether the target field is mandatory, optional or calculated.
- Whether values are copied directly, transformed, defaulted or excluded.
- Which source values are invalid and need cleansing before load.
- How exceptions are handled when source records do not fit the target model.
- Who owns the decision and who signs the mapping off before test load.
How to use it
Start with the high-risk entities: customers, suppliers, products, finance codes, open transactions and status fields. Do not attempt to map every field in the first pass. Map the fields that affect reporting, finance reconciliation, operational handoffs and user adoption first. Link unresolved rules back to your ERP data migration checklist and data-quality backlog.