# D365 Data Migration Cutover Duration Calculator > Source: https://netray.co/tools/d365-data-migration-cutover-duration-calculator > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: Free Tools ## Short answer Estimate how many hours your D365 go-live data load will take, including rework and reconciliation, and whether it fits the cutover window. ## Category microsoft-dynamics ## Erp Microsoft Dynamics 365 Finance and Supply Chain Management ## Audience - D365 project manager - Data migration lead - Solution architect ## Tool **Kind:** calculator **Inputs:** #### Total rows to load **Key:** rows **Type:** number **Default:** 2500000 **Min:** 0 **Step:** 50000 **Unit:** rows **Help:** Sum across all entities: customers, vendors, items, open orders, balances. #### Throughput per thread **Key:** rpm **Type:** number **Default:** 1200 **Min:** 1 **Step:** 50 **Unit:** rows/min **Help:** Measured in a mock load, per import thread. #### Parallel import threads **Key:** threads **Type:** slider **Default:** 6 **Min:** 1 **Max:** 24 **Step:** 1 **Unit:** threads #### Parallel efficiency **Key:** eff **Type:** slider **Default:** 70 **Min:** 30 **Max:** 100 **Step:** 1 **Unit:** % #### Rows needing error correction and reload **Key:** err **Type:** number **Default:** 4 **Min:** 0 **Max:** 100 **Step:** 0.5 **Unit:** % #### Reconciliation and validation **Key:** recon_h **Type:** number **Default:** 6 **Min:** 0 **Step:** 0.5 **Unit:** hours **Help:** Balance tie-outs, count checks, sign-off. #### Other cutover tasks **Key:** fixed_h **Type:** number **Default:** 4 **Min:** 0 **Step:** 0.5 **Unit:** hours **Help:** Final extract, configuration switches, user access, smoke tests. #### Planned downtime window **Key:** window_h **Type:** number **Default:** 48 **Min:** 1 **Step:** 1 **Unit:** hours **Outputs:** #### Effective threads **Key:** eff_threads **Expr:** 1 + (threads - 1) * eff / 100 **Format:** decimal #### Initial load time **Key:** load_h **Expr:** rows / (rpm * eff_threads) / 60 **Format:** hours #### Error rework time **Key:** rework_h **Expr:** load_h * err / 100 * 2 **Format:** hours **Description:** Reload cost is doubled to include analysis and correction effort. #### Total cutover duration **Key:** total_h **Expr:** load_h + rework_h + recon_h + fixed_h **Format:** hours **Primary:** true #### Slack against window (negative means overrun) **Key:** slack **Expr:** window_h - total_h **Format:** hours **Primary:** true #### Window used **Key:** used **Expr:** total_h / window_h * 100 **Format:** percent **Chart:** #### Cutover duration vs import threads **Type:** line **X:** threads **From:** 1 **To:** 24 **Steps:** 24 **Series:** - total_h **Disclaimer:** A planning estimate. Dependencies between entities force some loads to run in sequence, so parallelism is rarely perfect. Always base throughput on a timed mock cutover. ## Content **Intro:** A cutover plan lives or dies on the data load estimate. This calculator converts row counts and measured throughput into hours, adds error rework and reconciliation, and compares the total with your downtime window. **Sections:** #### How to use it **Body:** Add up rows for every entity in the cutover load, including open balances and open transactions. Use the throughput measured in your last mock cutover per thread, then set the thread count and an efficiency that reflects entity dependencies. Enter reconciliation and other task hours from the cutover runbook. If slack is negative or under 20 percent of the window, plan more mocks, trim history or loosen the dependency order. #### How the estimate is built **Body:** Load time is rows divided by the throughput of the effective threads. Rework is the share of rows needing correction times load time, doubled to account for investigation. Reconciliation and fixed tasks are added as flat hours. Because entities have dependencies, such as items before open purchase orders, the effective thread count is deliberately lower than the thread count. **Bullets:** - Effective threads = 1 + (threads - 1) x efficiency - Load hours = rows / (rows per minute x effective threads) / 60 - Total = load + rework + reconciliation + other tasks #### Reducing the window **Body:** Migrate static data such as customers, vendors and items ahead of go-live and load only deltas during the window. Cut history to what the business needs. Run mock cutovers at production volume and track the timings per entity so the plan improves each time. Validate that data is clean in earlier mocks, because error rework is the most volatile part. #### Common mistakes **Body:** Extrapolating from a small test load, ignoring the time to extract and transform source data, and leaving no time for rollback decisions all shorten the plan on paper only. Agree a go/no-go checkpoint partway through the window. Keep a record of actual versus estimated hours after each rehearsal so you can recalibrate efficiency and error rate. **Cta:** If you need help profiling legacy ERP data quality before the mock loads, Netray can run read-only analysis on the source data with your migration team. **Faq:** #### What throughput should I assume? **Answer:** Do not assume. Time a mock load for each major entity, because rates vary a lot between simple master data and entities with many validations or number sequences. Use the slowest realistic figure for the plan. #### How many mock cutovers are typical? **Answer:** Most projects run at least two or three full-volume rehearsals. Each should be timed, reconciled and followed by a lessons review, so the final estimate is built on measured numbers. #### Does this cover data transformation? **Answer:** Not by default. Add extract and transform time to other cutover tasks if those steps run inside the downtime window. Preparing transformed files in advance is a better approach. #### What if the total exceeds the window? **Answer:** Options include loading static data earlier, delta loading, increasing parallelism where entities allow it, trimming history, or lengthening the window with business agreement. ## Search terms d365 data migration cutover plan, d365 cutover duration estimate, d365 data management import time, dynamics 365 go-live downtime window, d365 f&o data migration planning, d365 cutover rehearsal timing, d365 dmf load performance --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json