The dynamics ax migration cutover plan. Period-end timing, in-flight order handling, freeze window communication, AOS quiesce, final delta extract, reconciliation gates, AIF integration rewiring, explicit rollback path. 50–72 hour window with the business operationally unaware on Monday.
Every other phase has the luxury of retry. Cutover doesn't. The Sunday-evening sign-off determines whether business runs in Fusion or back in AX on Monday morning.
A dynamics ax migration cutover is the moment when 14–20 weeks of extraction, transformation, reconciliation and parallel-run gets compressed into a single weekend decision. By Friday 6pm AX is taking its last transactions for the project. By Sunday 6pm finance, supply chain and IT have signed off the reconciliation pack or the rollback is invoked. Monday morning the business is either live in Fusion or operating in extended AX with a redo plan.
Every dynamics ax migration cutover plan starts with timing: period-end of a non-quarter-end month, typically Q2 or early Q3 to avoid statutory closing risk on a first-time Fusion go-live. Six weeks before cutover the freeze plan is communicated to business: no new sales orders Friday 6pm, no AP invoice posting Friday 6pm, no GL adjustments Friday 6pm. Three weeks before cutover the in-flight inventory exercise begins — every business unit reviews open SalesTable orders, open PurchTable orders, open VendInvoiceJour invoices and confirms which ones will close pre-freeze and which carry across to Fusion.
Friday evening the AOS quiesces — user sessions drain, AIF queues drain, batch jobs drain, AOS itself stops, SQL Server reaches a clean transactional state. Saturday the final delta extract runs against the quiesced database. Saturday afternoon and Sunday the delta loads into Fusion with reconciliation gates per domain (master data, AP, AR, GL, inventory). Sunday evening the cross-functional sign-off pack is reviewed, the go/no-go decision is made, AX moves to read-only or rollback is invoked. The dynamics ax migration cutover is designed to be uneventful — months of preparation expressed as a 50–72 hour windowed switch.
Every cutover risk has a pre-built control. No bespoke risk management on top of generic project methodology.
Period-end of a non-quarter-end month, Q2/Q3 preferred. Cutover calendar reviews any statutory deadline conflicts (tax filing, annual report) and surfaces clashes before commitment.
Open SalesTable/PurchTable/VendInvoiceJour/CustInvoiceJour catalogued 3 weeks ahead with per-record sign-off. No surprise in-flight items at cutover Friday evening.
4–6 week freeze communication. Emergency-operations manual procedures pre-defined for 60-hour gap (urgent shipments, customer-facing portal in read-only mode, time entry to separate system).
Quiesce runbook: user-session drain warning, AIF queue drain, batch-server drain, AOS stop. Final extract runs against a quiesced database with zero race-condition risk.
Per-domain reconciliation gates (master data, AP, AR, GL, inventory) with signed sign-off owners. Gate failure stops the cutover at that point with explicit remediation runway.
Explicit rollback plan with pre-signed decision criteria, 6-hour rollback runway built into 60-hour cutover window. AX reverts to read-write, business resumes in AX on Monday morning.
A 60-hour cutover window timeline. Adapt for 50-hour or 72-hour windows depending on scope.
Business stops AX posting per the 4-week-old freeze communication. AOS user-session drain begins (logout warnings issued, 30-minute grace). AIF queues drain. Batch jobs drain. End-of-day AX reconciliation pack pulled — final AX trial balance, AP aging, AR aging, on-hand inventory.
AOS gracefully shuts down. SQL Server reaches transactional consistency. AIF integration ports closed to inbound traffic. Outbound queue drained. Final delta extraction kicks off against the quiesced SQL Server.
Final delta extract completes. Transformation pipeline runs. FBDI payloads generated for each in-flight category (open orders, open invoices, pre-close GL journals). FBDI loads submitted to Fusion ESS. Per-domain reconciliation gates run as each load completes.
AIF integration ports rewired to Fusion REST endpoints. Statutory reporting smoke tests run (period-end TB, AP aging, AR aging, on-hand all match the Friday 6pm AX snapshot). Critical-path UAT (create sales order, post AP invoice, post AR invoice, post GL journal, create PO, receive PO, ship sales order).
Cross-functional reconciliation pack issued: TB vs TB to the cent per LE, AP aging vs aging, AR aging vs aging, on-hand vs on-hand, in-flight order match, integration rewiring evidence. Finance lead, supply chain lead, IT lead, internal audit lead review.
Go: AX moves to read-only archive, Fusion opens for business, communication issued to all users, Monday morning business runs in Fusion. No-go: rollback invoked, AOS returns to read-write, business resumes in AX on Monday morning, redo plan triggered (typically 4–8 weeks to next cutover attempt).
The dynamics ax migration cutover sign-off pack is the single artefact that drives the go/no-go decision.
Friday 6pm AX trial balance vs Sunday 4pm Fusion trial balance, per legal entity per period. Variance heatmap by natural account. Zero-cent tolerance for primary ledger; configurable variance allowance for secondary ledgers.
AP open balance per supplier per ageing bucket: AX Friday 6pm vs Fusion Sunday 4pm. AR open balance per customer per ageing bucket: AX Friday 6pm vs Fusion Sunday 4pm. Per-record variance list.
InventSum on-hand per item per warehouse per dimension: AX Friday 6pm vs Fusion Sunday 4pm. Variance flagged at item-warehouse level. Sign-off owner: supply chain controller.
Open SalesTable / PurchTable / VendInvoiceJour / CustInvoiceJour at Friday 6pm vs equivalent open records in Fusion Sunday 4pm. Per-record match audit.
AIF integration ports rewired to Fusion REST endpoints, end-to-end smoke test results, throughput at projected production volume. Operations team sign-off.
Screenshot/log evidence of create-sales-order, post-AP-invoice, post-AR-invoice, post-GL-journal, create-PO, receive-PO, ship-sales-order successful in Fusion. Functional area sign-off.
A dynamics ax migration cutover is the controlled moment — typically a long weekend at a fiscal-period boundary — when transactional flow stops in AX, the final delta load runs into Oracle Fusion, reconciliation passes, sign-off is obtained, and new business is conducted in Fusion from Monday morning onward. AX moves to read-only archive mode. AIF integration ports are rewired to Fusion endpoints. The dynamics ax migration cutover is the highest-risk moment of the whole project — a poorly designed cutover means orders are missed, AR is suspended, AP is delayed, or finance can't close the period. A well-designed cutover is uneventful: a 50-hour windowed switch from one ERP to another with the business operationally unaware on Monday.
Period-end. Specifically, the end of a fiscal period that finance has already closed in AX — typically end-of-month for monthly closers, end-of-quarter for quarterly statutory reporters. Cutover at period-end means: no in-flight GL postings for that period, AP and AR aging buckets are clean as of period close, inventory balance is settled per period close, and the first Fusion-posted GL period starts fresh on day one. Avoid cutting over: mid-period (creates a split period that no one wants to reconcile), at year-end (too much statutory closing risk for a first-time Fusion go-live), or during peak business windows (holiday retail, manufacturing month-end push). Best windows: month-end of a non-quarter-end month, ideally Q2 or early Q3.
Typical full-scope dynamics ax migration cutover runs 50–72 hours over a long weekend. Friday evening: business stops posting in AX, end-of-day reconciliation pack pulled from AX, AOS gracefully quiesced for the final delta extraction. Saturday: final delta extract, transform, load into Fusion, reconciliation gates per data domain (master data, AP, AR, GL, inventory). Sunday: integration testing, AIF integration port rewiring to Fusion REST endpoints, statutory reporting tests, end-user sanity checks. Sunday evening: sign-off pack issued, go/no-go decision, AX switched to read-only, Fusion opened for business. Monday morning: live in Fusion. Smaller scope (single legal entity, finance-only) can compress to 24–36 hours; multi-legal-entity global rollouts may extend to 96 hours with regional sequencing.
Anything not closed before cutover Friday is an in-flight item. The dynamics ax migration cutover plan addresses each category explicitly: open sales orders (SalesTable open + SalesLine remaining) migrated to Fusion Order Management with remaining quantity and pricing preserved; open purchase orders (PurchTable + PurchLine) migrated to Fusion Procurement with remaining receivable quantity; open AP invoices (VendInvoiceJour with open balance) migrated to Fusion Payables with original document date and supplier; open AR invoices and partial-payment situations migrated to Fusion Receivables; unposted GL journals (LedgerJournalTable in draft) either posted in AX pre-cutover or carried as Fusion draft journals. Each category has a sign-off owner who confirms that what arrives in Fusion matches what was in flight in AX.
The freeze window is the period between business stopping transactional posting in AX and business starting transactional posting in Fusion. Typically Friday 6pm to Monday 6am (60 hours). During the freeze window: no new sales orders, no new POs, no new GL postings, no new AP/AR invoices, no inventory movements. The freeze enables a clean final delta extract without race conditions and guarantees reconciliation integrity. Some flows can stay live during freeze (informational queries, time entry to a separate system, customer-facing portal in read-only mode) but anything that affects ERP state freezes. The freeze plan is communicated 4–6 weeks before cutover to give business sufficient runway to prepare (catch up open invoices, accelerate critical orders pre-freeze, prepare manual processes for emergency operations).
AOS quiesce means cleanly stopping AOS (Application Object Server) operations — no user sessions, no AIF inbound/outbound flows, no batch jobs, no service consumers — so the SQL Server backend reaches a transactionally consistent point for the final delta extract. AOS quiesce is more orderly than just kicking everyone off: user sessions get a logout warning, AIF queues drain, batch server queues drain, then AOS itself shuts down so SQL Server sees no AOS-originated writes. Final delta extract then runs against a quiesced database — every committed transaction is captured, no in-flight transactions to worry about. AOS comes back up post-extract in read-only mode for archive query support during the transition window.
Rollback is the contingency for Sunday-evening no-go. The dynamics ax migration cutover plan includes an explicit rollback path: revert AOS from read-only to read-write, unfreeze AX user sessions, business resumes posting in AX from Monday morning as if cutover had not occurred, the Fusion-side state is left in cutover-test mode for diagnosis. Rollback decision criteria are signed off in advance: critical reconciliation variance (>0.5% on TB by legal entity, >1% on AP/AR aging, missing in-flight orders, blocked statutory reporting), critical integration failure (AIF rewiring to Fusion REST not working at production volume), critical user-facing functionality not working (cannot create sales order, cannot post invoice). 60-hour cutover windows include a 6-hour rollback contingency built into the timeline.
Two patterns. Big-bang: all legal entities cut at the same time in one weekend. Compresses the runway but concentrates risk. Best for small AX deployments (<5 LEs) and customers with low cross-entity operational coupling. Regional / wave-based: legal entities cut in groups over 2–6 monthly cutovers. Each wave is a self-contained cutover with its own freeze, extract, load and sign-off. Lower per-wave risk but longer co-existence period with inter-wave AX-Fusion integration running. Most multi-LE customers (>10 LEs) prefer wave-based with the first wave being a small low-risk LE (pilot validation), subsequent waves being larger production LEs. The dynamics ax migration cutover plan specifies the wave grouping (by region, by business unit, by complexity) and the integration pattern that bridges waves.
Send us your fiscal calendar, statutory reporting deadlines and AX legal-entity list. We will return a cutover calendar with recommended weekend(s), freeze-window plan, rollback contingency and sign-off-pack template — typically within 5 working days.