Reviews and corrects ledger-to-subledger alignment in D365 by fixing posting configurations, inventory profiles, reconciliation logic, GL mapping, and critical reporting procedures.
Your D365 Cutover Is Green. The Truck Is Still Waiting.
Posted on: October 28, 2026 | By: Heather Zhu | Microsoft Dynamics AX/365, Microsoft Dynamics AX/365|Microsoft Dynamics Manufacturing
The Go-Live Reality Check
Keep orders moving through an ERP changeover by testing what happens between the migration report and the loading dock.
By Logan Consulting | October 28, 2026 | 5-minute read

Conceptual process illustration. An import result is not an end-to-end shipping test.
Picture Monday at 6:10 a.m. The migration dashboard is green. A carrier is at the dock. The customer’s order exists in Dynamics 365, but nobody can release it to the warehouse. Meanwhile, the integration team is wondering whether to resend the file.
This is an illustrative scene, not a client incident. It exposes a useful distinction: transferring an order is not the same as making it shippable. A record count cannot tell a warehouse supervisor what to pick, which customer commitment remains open, or whether a shipment notice reached its destination.
For manufacturers and distributors approaching a D365 cutover, the most useful rehearsal is not another import-only test. It is a controlled journey from a customer purchase order through fulfillment and the required outbound documents.
Logan Point of View
A cutover transfers responsibility for live orders, not just data. Test the handoff the customer depends on.
01 / Protect the Orders in Flight
Freeze the handoff, not the database.
Start with the orders that straddle the switch. Which system finishes existing shipments? Where do incoming orders wait? Who handles a customer’s change while the business is paused? Put a named owner, a cutoff time and a restart condition beside each answer.
|
100 Units Ordered |
60 Shipped + Invoiced |
40 Remaining to Ship |
Illustrative quantity reconciliation. Preserve the 40-unit commitment, not a second 100-unit order.
Consider a simple, illustrative order for 100 units: 60 have shipped and been invoiced before the freeze; 40 remain. The cutover design must preserve that distinction. It must not create another 100 units of demand or bill the first 60 again. The migration method depends on your design; this is a reconciliation requirement, not a universal import recipe.
Reconcile at line level: customer PO reference, legal entity, item, unit, remaining quantity, delivery commitment and the old-to-new order reference. Give each business event one designated processing system. Capture orders and changes arriving during the pause in a controlled holding process, then reconcile that backlog before release.
Microsoft’s cutover guidance calls for owners, verification, sign-off and a rollback plan. Add something concrete to each task: the evidence that the next team can do its job.
The Trap
Two systems containing an order is not continuity. One accountable route for the remaining work is.
|
Before the Freeze Reconcile open lines and outbound documents. |
During the Pause Hold intake with a durable reference and an owner. |
At Restart Reconcile the backlog before releasing work. |
02 / Rehearse in D365
Follow one order all the way to work.
|
01 / Received File reached storage |
02 / Created Correct order + lines |
03 / Executable Shipment + picking work |
04 / Completed Required outbound proof |
Simplified proof chain, not a D365 screen. Evidence must follow the order across systems.
Use a sandbox with representative data and the actual business-role permissions. Keep production trading-partner endpoints isolated. These are proposed tests, not tests performed in your tenant.
Check the import outcome. For cloud deployments using recurring data jobs, open the System administration workspace, then Data Management IT workspace, and select the job under Recurring data jobs. Review its messages and processing status. Enqueued means the file reached storage, not that an order was created. ProcessedWithErrors is not a clean pass. Trace the result to the actual D365 order. This route is not supported for on-premises deployments. Microsoft documentation
Prove warehouse execution. Where Warehouse management processes are used, go to Warehouse management > Release to warehouse > Release sales orders to warehouse. Select the test lines, add them to the lower section and release them. Inspect the resulting shipments and warehouse work. Release creates shipments and load lines; wave processing creates picking work according to your configuration. An existing sales order alone is not that evidence. Release-to-warehouse guidance
Finish the business chain. Verify labels, scans, shipment confirmation, invoicing and any required advance ship notice, or ASN. For electronic data interchange (EDI), distinguish transport receipt from the partner’s required acceptance. Retain evidence from the ERP and the integration provider. Native import status does not certify the whole trading-partner exchange.
“it is critical to test the use of all equipment prior to cutover.”
Originally written for QAD projects. The equipment-test principle applies here; it is not current D365 configuration guidance.
03 / Break It Before Monday
The second delivery is the test.
Now replay the same inbound order in the rehearsal. Then submit an order with an unmapped item. The proposed acceptance criteria are clear: no duplicate fulfillment demand from the replay; a visible, owned exception for the bad item; and a controlled correction that does not create a second order. Agree document identifiers and duplicate-handling rules with your integration provider. They are not guaranteed by a successful D365 import.
Also simulate a downstream outage. Microsoft’s go-live checklist specifically calls for testing external systems that are down and the resulting user experience. Rehearse who stops processing, who contacts the partner, and how pending work resumes without being lost or processed twice.
|
Replay No duplicate fulfillment demand. |
Bad Item Visible exception with a named owner. |
Outage Controlled hold and reconciled restart. |
Proposed acceptance criteria. Configure and verify duplicate handling in the actual integration design.
Keep the evidence together: source document identifier, import result, D365 order and line, remaining quantity, shipment and work references, outbound-document status, and the person who accepted the result. Measure time to a shippable order, backlog age and unresolved exceptions, not only files processed.
Agree the go/no-go thresholds before the rehearsal. If you have already shipped goods or sent documents externally, restoring an ERP backup does not undo those actions. Your recovery plan must reconcile them. A tested pause is better than an enthusiastic restart that creates two versions of the truth.
Logan’s EDI practice and project management services bring the integration and operating teams into the same conversation. Bring one important customer flow, an open-order extract and your cutover plan. Let’s trace the remaining work and identify what must be proven before the first truck is booked.
Remember One Thing
A migrated order is not yet a shippable order.
Sources linked inline and checked October 28, 2026. Scenarios and tests are illustrative editorial guidance, not client results or executed tenant tests. Validate your build, configuration, security and partner requirements before use.














