# D365 Finance and Supply Chain Data Migration Mapping Worksheet > Source: https://netray.co/tools/d365-fo-data-migration-mapping-worksheet > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: Free Tools ## Short answer An editable source-to-target field mapping sheet with transformation rule, owner and load status for D365 F&O data migration. ## Category microsoft-dynamics ## Erp Microsoft Dynamics 365 Finance and Supply Chain ## Audience - Data migration lead - D365 F&O consultant - Technical consultant ## Tool **Kind:** worksheet **Mode:** editable **Columns:** #### Migration object **Key:** object **Type:** text #### Source field **Key:** src_field **Type:** text #### Target data entity **Key:** tgt_entity **Type:** text #### Target field **Key:** tgt_field **Type:** text #### Transformation rule **Key:** rule **Type:** text #### Owner **Key:** owner **Type:** text #### Status **Key:** status **Type:** select **Options:** - Not started - Mapped - Loaded in test - Validated - Signed off #### Source records **Key:** records **Type:** number #### Rejected records **Key:** rejects **Type:** number #### Reject rate **Key:** reject_pct **Type:** number **Expr:** if(gt(records,0), rejects / records * 100, 0) **Format:** percent **Rows:** **Object:** Customers **Src field:** CUST_NO **Tgt entity:** Customers V3 **Tgt field:** CustomerAccount **Rule:** Prefix C-, pad to 8 chars **Owner:** Finance lead **Status:** Loaded in test **Records:** 4200 **Rejects:** 63 **Object:** Vendors **Src field:** VEND_ID **Tgt entity:** Vendors V2 **Tgt field:** VendorAccountNumber **Rule:** Direct map, dedupe on tax ID **Owner:** Procurement lead **Status:** Mapped **Records:** 1850 **Rejects:** 0 **Object:** Released products **Src field:** ITEM_NO **Tgt entity:** Released products V2 **Tgt field:** ItemNumber **Rule:** Strip leading zeros **Owner:** Inventory lead **Status:** Validated **Records:** 12400 **Rejects:** 120 **Object:** Open purchase orders **Src field:** PO_NUM **Tgt entity:** Purchase order headers V2 **Tgt field:** PurchaseOrderNumber **Rule:** Open lines only, re-number **Owner:** Procurement lead **Status:** Not started **Records:** 310 **Rejects:** 0 **Object:** Opening balances **Src field:** GL_ACCT **Tgt entity:** General journal **Tgt field:** MainAccount **Rule:** Map via COA crosswalk **Owner:** Controller **Status:** Mapped **Records:** 940 **Rejects:** 0 **Totals:** #### Total source records **Key:** records **Agg:** sum **Format:** integer #### Total rejected **Key:** rejects **Agg:** sum **Format:** integer #### Mapping rows **Key:** object **Agg:** count **Format:** integer **Summary:** #### Overall reject rate **Key:** overall_reject **Expr:** if(gt(sum_records,0), sum_rejects / sum_records * 100, 0) **Format:** percent **Notes:** Entity names above are examples. Confirm the exact data entity and field names in the Data management workspace of your environment and version before loading. ## Content **Intro:** Most D365 go-lives that slip do so on data. A mapping sheet puts every source field, target entity, rule and owner in one place, so cleansing work is visible long before the first mock load. **Sections:** #### How to use the worksheet **Body:** Add a row for each field mapping or each migration object, depending on how detailed you need to be. Name the target data entity as it appears in the Data management workspace, record the transformation rule in plain words, and give every row an owner from the business. Update status after each mock load and enter source and rejected record counts to see reject rates calculate automatically. **Bullets:** - Map to data entities, not tables - Write rules in plain words a business owner can check - Record counts after every mock load - Keep a separate row for each load sequence dependency #### Load order and dependencies **Body:** Entity load order matters: legal entities, number sequences, main accounts and dimensions precede customers, vendors and released products, which precede open orders and opening balances. Use the data management framework's execution units and sequencing in data projects to enforce order. Staging tables let you validate before copying to target, which keeps errors out of production tables. #### Reading the reject rate **Body:** A reject rate that stays above a few percent after several mock loads usually points to a rule problem, not random bad data. Look at the most common error message in the execution log and fix the rule or the source cleansing. Aim to reach a stable, explainable rate before cutover rehearsal, and have the business sign off each object on the final mock. #### Common mistakes **Body:** Teams map to the legacy structure instead of the D365 data model, forget financial dimensions and default values, and migrate far more history than the business will use. Also avoid loading open transactions without a cutoff plan; document how in-flight orders are handled at the freeze. Keep the sheet under version control, because decisions here become audit evidence. **Cta:** If you are mapping a large legacy ERP, Netray can help build private tooling that proposes field mappings and spots profile anomalies in your source data, with every mapping reviewed by your team. **Faq:** #### Should I map every field? **Answer:** Map every field you intend to load, and explicitly record fields you decided not to migrate with the reason. A short list of excluded fields prevents later debates about missing data and gives auditors a clear decision trail. #### How many mock loads are typical? **Answer:** Most projects run at least two or three full mock loads before cutover, plus a final rehearsal in a production-like environment. The right number depends on data volume and quality, and each mock should reduce rejects and timings. #### Can I use Excel to load data? **Answer:** Yes, for small volumes. The Excel add-in and the data management import can load templates, but for large volumes use package imports with data entities. Always load into a test environment first. #### Who should own each object? **Answer:** A named business owner who can judge correctness, not only a technical consultant. Finance owns balances and customers, procurement owns vendors and open purchase orders, and so on. Sign-off should come from them. ## Search terms d365 data migration mapping template, dynamics 365 data migration excel, d365 fo field mapping, legacy to d365 data mapping, d365 data entity mapping worksheet, d365 data migration checklist --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json