Migrating legacy data into Dynamics 365, with the dimensions decided first
Business Central expects masters (Customer, Vendor, Item), documents (Sales Header and Sales Line), a chart of accounts, and dimensions that carry the department, project, or region a legacy system kept in its own columns. Getting the dimensions right is most of the design; getting the opening balances right is most of the risk. Datapace maps the legacy source first, proposes which legacy fields become dimension values and which become attributes, and has your expert validate each decision before the configuration packages are built. Finance and Operations follows the same method against its own model.
Today. Legacy fields pushed into Business Central through configuration packages, with the dimension design discovered at reconciliation time.
With Datapace. The source is resolved into one map, dimension values and masters are proposed with their evidence, and your expert validates the design before a package is built.
What Datapace does here
- Masters first
- Customer, vendor, and item masters are resolved from the legacy tables, duplicates shown, units of measure and posting groups proposed for your expert to confirm.
- Dimensions from legacy columns
- The department, project, cost centre, and region columns a legacy system kept on every row are proposed as dimension values, with the rows that would not fit flagged.
- Documents and history
- Order headers and lines map to Sales Header and Sales Line; what stays behind is marked with its reason, and open items become opening balances.
- G/L accounts and posting groups
- The legacy chart of accounts is crosswalked to G/L Accounts you confirm, and the posting groups the documents need are derived from it.
- Configuration packages from a validated map
- The packages are built from mappings your expert validated, so the reconciliation checks what was decided, not what was guessed.
The target model
What the mapping resolves to. Each row is proposed with its evidence and validated by your domain expert before load.
| Legacy source | Business Central | Decided before load |
|---|---|---|
| Customer master | Customer | Posting groups and payment terms proposed from history |
| Vendor master | Vendor | Duplicates across sources shown for the merge decision |
| Item master, units | Item, Item Unit of Measure | Base unit confirmed by your expert |
| Order header, lines | Sales Header, Sales Line | Open documents move; closed history stays or summarises |
| Department, project columns | Dimension Values | Global and shortcut dimensions decided before load |
| General ledger | G/L Account, opening balances | Crosswalked chart, balances by period |
Questions teams ask
- Business Central or Finance and Operations?
- Both. The method is the same: resolve the source, propose the mapping against the target model, validate with a person. Business Central is the more common target for the mid-size companies Datapace serves, so its model is the one shown here.
- Why decide dimensions before load?
- Because a dimension value that arrives wrong is on every posted entry. Datapace proposes the dimension design from the legacy columns with the rows that would not fit, so the decision is made once, on evidence, before anything is posted.
- What about the Dataverse side, for Sales or Customer Service?
- The same validated map grounds the mapping into Dataverse tables when a project covers customer engagement as well as finance and operations. The partner and account decisions are made once and reused.
Go further
See this on your own data
Bring a use case. We will show you what Datapace reads on your live database, what your experts would confirm, and what the agents would propose first.
Book a call