# D365 Data Management Framework Import Worksheet Template > Source: https://netray.co/tools/d365-dmf-import-worksheet-template > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: Free Tools ## Short answer Track every D365 DMF import by entity, sequence, legal entity, rows loaded and errors, with an automatic error rate for cutover reporting. ## Category microsoft-dynamics ## Erp Microsoft Dynamics 365 Finance and Supply Chain ## Audience - D365 F&O consultant - Data migration lead - Project manager ## Tool **Kind:** worksheet **Mode:** editable **Columns:** #### Seq **Key:** seq **Type:** number #### Entity **Key:** entity **Type:** text #### Legal entity **Key:** company **Type:** text #### Source format **Key:** format **Type:** select **Options:** - CSV - Excel - XML - Package #### Skip staging **Key:** skip **Type:** select **Options:** - No - Yes #### Rows in file **Key:** rows **Type:** number #### Rows in error **Key:** errors **Type:** number #### Error rate **Key:** errpct **Type:** number **Expr:** if(gt(rows,0), errors / rows * 100, 0) **Format:** percent #### Run date **Key:** run **Type:** date #### Status **Key:** status **Type:** select **Options:** - Not started - Loaded - Loaded with errors - Signed off #### Owner **Key:** owner **Type:** text **Rows:** **Seq:** 10 **Entity:** Legal entities / calendars **Company:** usmf **Format:** CSV **Skip:** No **Rows:** 4 **Errors:** 0 **Run:** 2026-11-02 **Status:** Signed off **Owner:** Functional lead **Seq:** 20 **Entity:** Products V2 **Company:** dat **Format:** Package **Skip:** No **Rows:** 5200 **Errors:** 38 **Run:** 2026-11-03 **Status:** Loaded with errors **Owner:** Data lead **Seq:** 30 **Entity:** Released products V2 **Company:** usmf **Format:** Package **Skip:** No **Rows:** 5200 **Errors:** 12 **Run:** 2026-11-04 **Status:** Loaded with errors **Owner:** Data lead **Seq:** 40 **Entity:** Bill of materials headers **Company:** usmf **Format:** CSV **Skip:** No **Rows:** 1900 **Errors:** 0 **Run:** 2026-11-06 **Status:** Loaded **Owner:** Engineering **Seq:** 50 **Entity:** Bill of materials lines **Company:** usmf **Format:** CSV **Skip:** No **Rows:** 14800 **Errors:** 210 **Run:** 2026-11-06 **Status:** Loaded with errors **Owner:** Engineering **Seq:** 60 **Entity:** Vendors V2 **Company:** usmf **Format:** Excel **Skip:** No **Rows:** 640 **Errors:** 5 **Run:** 2026-11-08 **Status:** Loaded **Owner:** Procurement **Totals:** #### Total rows **Key:** rows **Agg:** sum **Format:** integer #### Total rows in error **Key:** errors **Agg:** sum **Format:** integer **Summary:** #### Overall error rate **Key:** overall **Expr:** if(gt(sum_rows,0), sum_errors / sum_rows * 100, 0) **Format:** percent **Primary:** true #### Data project steps **Key:** lines **Expr:** count **Format:** integer **Notes:** Track each data project execution, not just the final load. Record the data project name and execution id in your notes column outside this table when you export. Keep a separate log of mapping and defaulting decisions for each entity. ## Content **Intro:** A Dynamics 365 data migration succeeds or fails on discipline: load sequence, row counts reconciled to source and a clean record of errors. This worksheet gives you the tracking table most project managers build by hand, with an error rate calculated per entity. **Sections:** #### How to use the worksheet **Body:** Add one row per entity load in sequence order. After each execution in Data management, record row counts from the source file and the number of rows in error from the execution summary. The error rate column and the overall rate update automatically. Export to Excel to share with the project team or attach to cutover sign-off. **Bullets:** - One row per entity per legal entity - Lower sequence numbers load first - Record the owner who signs off each load - Re-run counts after every correction pass #### How DMF imports work **Body:** In the Data management framework, a data project holds entities, each with a source format and a sequence. Files are first loaded into staging tables, validated, and then copied to target tables. Staging gives you an error view before data lands in the live tables, which is why skipping staging should be limited to cases you have tested. You can also set parameters such as the number of tasks for parallel processing on large entities. #### Reconciliation after the load **Body:** Row counts are not the end of reconciliation. Compare business totals: on-hand quantity and value, open order value, count of active BOMs, vendor and customer counts. Record deviations and the decision on each. For cutover rehearsal, store the timings for each entity so you can build a realistic downtime plan from measured data. #### Common mistakes **Body:** Frequent failures include loading dependent entities before their parents, ignoring warnings that become errors later, loading in the wrong legal entity, and fixing errors in the target instead of the source so the next rehearsal repeats them. Treat the source file as the master and correct there. **Cta:** If you want help automating the checks and reconciliation between your legacy ERP and D365 data, we can scope that with you. **Faq:** #### What is the Data management framework in D365? **Answer:** It is the built-in toolset for importing and exporting data through data entities. You create data projects, add entities with a source format, upload files, and run import or export jobs. Data lands in staging tables first, then moves to target tables after validation. #### How do I choose the load order? **Answer:** Use the dependency order of the data: organization and calendars, product and units, resources and routes, BOMs, then partners and open transactions. Within a data project, set sequence numbers on entities so parents load before children. #### Should I skip staging? **Answer:** Only for tested, high-volume loads where you accept less visibility into errors. Staging gives you an error view and the chance to correct and re-run. Most teams keep staging on for rehearsals and decide on exceptions with evidence. #### What error rate is acceptable? **Answer:** For master data cutover the target is zero unresolved errors or explicit, signed-off exclusions. Early rehearsals often show a few percent, which is normal, as long as each error category is understood and the rate falls with every pass. ## Search terms d365 data migration template excel, d365 dmf import tracker, d365 data management import checklist, dynamics 365 data migration plan template, d365 data project template, d365 cutover data load sequence, d365 import error tracking, d365 data entity load order spreadsheet --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json