72-hour descartes migration cutover covering EDI VAN re-pointing in 3 waves, customs broker handoff for in-flight ACE entries, carrier API credential switches for FedEx/UPS/DHL/ocean carriers, in-flight shipment handling, hour-by-hour checkpoint plan with documented rollback at every level.
A financial-system cutover has a single boundary: the period-close date. A descartes migration cutover has thousands: every EDI trading partner, every customs filing in flight, every carrier API, every truck currently in transit. Coordinating those boundaries is what makes or breaks the weekend.
Logistics businesses don't have period-close as a natural cutover boundary. Shipments cross the cutover window mid-flight — a truck tendered Friday delivers Monday, an ocean container loaded last week arrives at the port of entry next week, an EDI 856 ASN from a quarterly supplier might arrive any day. The descartes migration cutover plan has to handle every one of these in-flight cases without breaking the operational chain. That's why wave-based EDI VAN re-pointing, customs broker handoff coordination and carrier API credential management are mandatory — not optional.
Syntra ETL's descartes migration cutover pattern: 72-hour long-weekend window, EDI VAN re-pointing in 3 waves (Friday evening top 20 partners, Saturday mid-tier 50, Sunday long-tail), customs broker handoff coordinated 72 hours pre-cutover, carrier API credential switches in the Sunday window, in-flight shipments staying on Descartes through POD with the tenant in pass-through mode for 7–14 days post-cutover. Every workstream has hour-by-hour checkpoints and a documented rollback path.
The cutover sign-off pack issued Monday 6am includes shipment count parity, customs filing parity, EDI message control-number coverage, document image hash match rate, freight charge sum reconciliation, in-flight shipment register, EDI VAN re-pointing wave completion log and carrier API switch confirmation per carrier. Internal audit, logistics ops, customs broker and finance lead sign off on the pack. Production cuts to Fusion.
Each workstream has its own coordination team, hour-by-hour checkpoint plan and documented rollback path.
Wave 1 Friday evening: top 20 trading partners by volume. Wave 2 Saturday: mid-tier 50. Wave 3 Sunday: long-tail. Descartes GLN kept in pass-through mode 7–14 days to catch late re-pointing.
Customs filing freeze 72 hours pre-cutover. In-flight ACE entries, ISF filings, ACI declarations drained on source system. Broker workflow re-pointed Sunday with documented rollback if broker can't onboard in time.
FedEx, UPS, DHL, ocean carriers, LTL, ground brokers: credentials re-issued 2–4 weeks pre-cutover, rate cards pre-loaded to Fusion TMS, tracking feeds pre-configured. Switch happens Sunday with parallel-pull validation.
Shipments tendered pre-cutover stay on Descartes through POD. Tracking events flow through MacroPoint into Descartes. Freight invoices AP-feed to Fusion GL via transitional integration. New shipments originate in Fusion only.
Document Services API kept active throughout cutover for in-flight document attachment. Post-cutover, archive moves to immutable read-only mode with continuing access via cross-reference document-id retrieval.
Rollback decision tree pre-agreed: critical-customer EDI break, CBP-impacting customs failure, carrier rate-quote outage >4 hours triggers rollback evaluation. Per-workstream and full-cutover rollback both documented and rehearsed.
Friday 6pm to Monday 6am with hour-by-hour checkpoints. Elevated 24/7 staffing across all stakeholder groups.
Descartes GLN in read-only mode for new bookings. In-flight shipment queue drained. Final EDI message drain. Customs filing freeze active (started 72 hours earlier). Final delta extract from Descartes begins.
Final delta FBDI loads to Fusion. Final reconciliation pass across shipments, customs filings, EDI messages, document images, rate cards. Reconciliation evidence pack draft 1 issued for review.
Wave 1 EDI VAN re-pointing executed for top 20 trading partners by volume. Each partner's technical contact confirms message flow on Fusion B2B Messaging. Wave 2 executed for mid-tier 50 partners. Parallel-pull validation runs continuously.
Wave 3 EDI VAN re-pointing for long-tail partners. Carrier API credential switches per carrier (FedEx, UPS, DHL, ocean, LTL, ground broker) with parallel-pull validation. Customs broker handoff confirmation.
Final reconciliation evidence pack signed by internal audit, logistics ops, customs broker, finance lead. Production cuts to Fusion Monday 6am. Descartes tenant in pass-through mode for 7–14 days. Elevated support staffing continues.
Most descartes migration cutover projects never need rollback. Every project ships with the plan.
If a wave's re-pointing fails (>5 partners can't authenticate to Fusion B2B in 4 hours), Wave-Level rollback: Descartes GLN remains primary EDI VAN, Fusion B2B endpoints deactivated, wave re-scheduled for next maintenance window.
If a carrier API switch fails (rate quote unavailable, tracking events not flowing), Carrier-Level rollback: re-activate Descartes carrier integration, carrier-side credential re-revoked, switch re-scheduled with carrier coordination.
If broker handoff fails (broker can't file through Fusion GTM, Customs Info access lost), Customs-Level rollback: re-activate Customs Info, financial AP feed remains on Fusion, hybrid pattern adopted permanently or until broker re-trained.
Not applicable — in-flight shipments stay on Descartes by design through POD; no rollback needed because shipments never moved.
Triggered only by catastrophic Fusion-side failure: Fusion B2B Messaging outage >8 hours, Fusion GTM data corruption, Fusion TMS rate-calculation systemic failure. Re-open Descartes GLN as primary, route new shipments to Descartes, freeze Fusion.
Most common rollback outcome: Fusion stays primary for shipments and AP, Descartes Customs Info re-activated for filings. Broker onboarding to Fusion GTM re-scheduled for next quarter. Operational continuity preserved.
Descartes migration cutover is the coordinated moment when live shipment processing, EDI message exchange, customs filing and carrier rate management transitions from the Descartes Global Logistics Network (GLN), MacroPoint, Aljex and Customs Info to Oracle Fusion SCM/TMS/GTM. Unlike a financial-system cutover where the boundary is the period-close date, a descartes migration cutover has to coordinate EDI VAN re-pointing across thousands of trading partners, customs broker handoff for in-flight ACE entries, carrier API account re-issuance, in-flight shipment handover for trucks already in transit, and document-image archive continuity. A typical descartes migration cutover is scheduled across a long weekend with hourly checkpoints and a documented rollback plan for every major workstream.
EDI VAN cutover timing is the most complex element of any descartes migration cutover because the Descartes GLN is itself an EDI VAN, and re-pointing thousands of trading-partner connections to Fusion B2B Messaging can't happen all at once. Syntra ETL plans the EDI VAN cutover in waves: Wave 1 (Friday evening) re-points the top 20 trading partners by transaction volume, Wave 2 (Saturday) covers the mid-tier 50 partners, Wave 3 (Sunday) covers the long-tail seasonal partners. Each wave is coordinated with the partner-side technical contact captured during the descartes migration checklist phase. The Descartes GLN endpoint is kept in pass-through mode for 7–14 days post-cutover to catch any partner whose re-pointing didn't complete cleanly.
Customs broker handoff is a critical workstream in descartes migration cutover because in-flight customs filings (ACE entries not yet accepted by CBP, ISF filings awaiting bond confirmation, ACI declarations in review) can't be migrated mid-flow — they have to complete on the source system before the broker switches to Fusion GTM or to a continuing Customs Info subscription. Syntra ETL schedules a customs filing freeze 72 hours before cutover, drains the in-flight filing queue, then re-points the broker's workflow to the new system. For brokers staying on Customs Info as a hybrid (Descartes keeps customs, Fusion takes financial close), the handoff is a financial-integration cutover only — the broker continues filing through Customs Info but the AP/GL feed re-points to Fusion.
Carrier API re-pointing in descartes migration cutover covers FedEx, UPS, DHL, ocean carriers, LTL providers and ground brokers — each with its own API authentication, rate-card refresh schedule and tracking-feed configuration. Syntra ETL coordinates the re-pointing with each carrier's technical contact 2–4 weeks ahead of cutover: new API credentials issued, rate cards pre-loaded into Fusion TMS, tracking-feed endpoints pre-configured. On cutover weekend, the carrier-side credential switch happens during the documented cutover window, with parallel-pull validation in the first hour to confirm rate quotes and tracking events flow correctly. Rollback is documented per carrier in case any single integration fails.
In-flight shipment handling is the operational headache of descartes migration cutover: a truck that's loaded on Friday afternoon and delivers on Monday morning crosses the cutover boundary. Syntra ETL's pattern: shipments tendered before cutover stay in Descartes through delivery and POD (proof of delivery), with the freight settlement happening in Descartes; shipments tendered after cutover originate in Fusion. The Descartes tenant remains live in shipment-execution mode for 7–14 days post-cutover to clear in-flight inventory, then moves to read-only archive mode. Tracking events for in-flight shipments continue flowing through MacroPoint into Descartes; freight invoices for in-flight shipments AP-feed to Fusion GL through a documented transitional integration.
Every descartes migration cutover ships with a documented rollback plan at three levels: per-workstream rollback (EDI VAN re-pointing rollback per wave, carrier API rollback per carrier, customs filing rollback if broker handoff fails), full cutover rollback (re-open Descartes GLN as primary, route new shipments back to Descartes, freeze Fusion SCM/TMS), and partial rollback (Fusion stays primary for shipments but Descartes Customs Info re-activated for filings if customs broker can't onboard to Fusion GTM in time). The rollback decision criteria are pre-agreed: any critical-customer EDI break, any CBP-impacting customs filing failure, any carrier rate-quote outage exceeding 4 hours triggers rollback evaluation. Most descartes migration cutover projects never need rollback, but every project ships with the plan.
A typical descartes migration cutover spans a 72-hour long weekend (Friday 6pm to Monday 6am). Hour 0–4: Descartes GLN in read-only mode for new bookings, in-flight shipments and EDI message draining. Hour 4–12: Final delta extract from Descartes, final FBDI loads to Fusion, final reconciliation pass. Hour 12–36: EDI VAN re-pointing wave 1 (top 20 partners) and wave 2 (mid-tier 50). Hour 36–60: EDI VAN re-pointing wave 3 (long-tail), carrier API credential switches, customs broker handoff confirmation. Hour 60–72: Parallel-pull validation, business-stakeholder walkthrough, sign-off pack issued. Production cut to Fusion Monday 6am with documented elevated-support staffing for the first 7–14 days.
Descartes migration cutover requires elevated stakeholder support across the 72-hour window: logistics ops on-call for shipment-execution issues, customs broker on-call for in-flight customs filings, finance/AP on-call for freight invoice reconciliation, IT integration team on-call for EDI VAN re-pointing and carrier API switches, Syntra ETL cutover team running the reconciliation engine and rollback decision tree. Trading-partner technical contacts (from the descartes migration checklist) are on standby for their wave's re-pointing window. Post-cutover, elevated support continues for 7–14 days to catch late-arriving EDI messages, in-flight shipment POD events and any production issues — typical pattern is 24/7 staffing for the first 72 hours, then business-hours staffing through end of week 2.
Book a 30-minute discovery call. We'll walk you through a sample 72-hour descartes migration cutover plan from a recent project, show you the hour-by-hour checkpoints and rollback decision tree, and explain how we coordinate EDI VAN re-pointing waves with trading-partner technical contacts.