Plan a WMS migration cutoff that preserves open warehouse work

Why "export the closing stock CSV on Saturday night" corrupts Monday morning picking

Warehouse management system (WMS) cutovers rarely fail because the database import script misplaces a column header. They fail on Monday morning at 08:30 IST when a picker walks up to rack location A-04-02-B to pick twenty cartons of a fast-moving SKU that the new WMS says are available—only to find the bin empty because those twenty cartons were picked on Saturday afternoon in the legacy system, wrapped onto a pallet in Outbound Staging Lane 3, and are currently waiting for a Monday morning truck. Worse still, when the Monday truck departs, the dispatch clerk confirms the shipment in the ERP, deducting the twenty cartons a second time or leaving the staged pallet orphaned in the new WMS.

A physical warehouse is almost never completely empty of in-flight work at cutover. Even during a planned weekend freeze, the floor holds at least four distinct categories of inventory: available stock in storage bins, stock already allocated and staged against open outbound orders, inbound stock sitting at the receiving dock, and non-sellable stock locked in quarantine or quality hold.

Planning a clean WMS migration cutoff means establishing rules for each of those four states before freezing transactions, verifying bin-level counts—using structured counting practices such as those described in Microsoft Learn — Cycle Counting—and mapping putaway and staging logic cleanly to the target system's location architecture, such as the rules illustrated in Microsoft Learn — Location Directives.

Drain partial transactions before the transactional freeze begins

Forty-eight hours before the legacy WMS is switched to read-only mode, operations and IT should enforce a Cutover Drain Protocol to reduce the number of half-finished floor states:

1. Stop releasing new multi-shift picking waves that cannot be completely picked, packed and staged before the freeze timestamp (T0). Any partially picked wave in the legacy system must either be completed to a clean Staged / Packed state before T0 or reversed back to storage bins and re-released in the new WMS after go-live.
2. Clear the receiving apron: Require inbound trucks arriving in the final four hours before T0 either to complete full unloading, tally and putaway in the legacy system before cutoff, or to hold at the gate/dock as intact unopened ASNs to be received natively in the new WMS after go-live. Never freeze the database with half a truckload put away in legacy bins and the other half sitting un-scanned on the dock.
3. Close open cycle-count adjustments: As noted in Microsoft Learn — Cycle Counting, open counting work or pending variance approvals create ambiguity over the true on-hand figure. Approve or cancel all pending legacy count sheets before extracting the closing snapshot.

Illustrative example: reconciling 5,000 physical cartons across four cutover states

Suppose a regional distribution warehouse executes its WMS migration cutoff at 22:00 IST on Saturday with 5,000 physical cartons inside the four walls of the facility. Instead of importing all 5,000 cartons as generic "available stock", the cutover team reconciles and migrates the inventory across four explicit operational states so that every carton's physical location and allocation status match between the floor, the new WMS and the ERP.

Check the arithmetic across the four physical states:

• 4,400 cartons in storage bins + 320 cartons picked and staged for dispatch + 180 cartons from the inbound ASN completed prior to freeze + 100 cartons in quarantine hold = 5,000 total physical cartons.
• In the ERP financial ledger, total warehouse on-hand is 5,000 cartons (4,400 + 180 = 4,580 free storage cartons, 320 staged awaiting dispatch confirmation, 100 blocked in quality hold).
• In the new WMS, total on-hand is 5,000 cartons, but only the 4,580 free storage cartons (4,400 + 180) can be allocated to new customer orders, while the 320 staged cartons are ready for Monday morning truck loading and dispatch confirmation.

Validate location directives and data-load APIs before cutover night

Even when the opening quantities reconcile on paper, two technical checks are critical during dress rehearsals:

1. Test location directives against migrated stock attributes: As explained in Microsoft Learn — Location Directives, a WMS uses location directives, zone capacities, batch/expiry rules and unit-of-measure conversions to direct putaway and picking. If the migration script imports 4,400 cartons with a blank Packaging UOM or a string-formatted expiry date, the new WMS will display the stock on inquiry screens while refusing to generate a single pick instruction on Monday morning.
2. Secure and audit the migration data pipeline: Migration weekends often involve temporary admin scripts, CSV bulk loaders and elevated API keys. Apply the access and data-integrity principles from the OWASP — API Security Top 10 2023: restrict bulk-load endpoints to authorised migration service accounts, log checksums of exported and imported row counts, and revoke temporary cutover credentials immediately after go-live sign-off.

Run a mandatory four-way Go/No-Go checkpoint before opening the floor

Before unlocking RF scanners for the Monday morning shift, the Depot Manager, Finance Controller, Quality Lead and IT Cutover Lead should sign off a single reconciliation sheet showing:

• Total cartons and value by SKU + Batch + Status in the Legacy Closing Snapshot vs the New WMS Opening Snapshot vs the ERP Inventory Sub-Ledger (Variance must equal 0, or any agreed rounding/UOM adjustment must be explicitly documented and signed).
• 100% physical spot-verification of high-value bins, the entire STAGE-OUT lane (320 cartons in the example) and the QUAR-01 hold cage (100 cartons).
• One end-to-endcanary transaction test in production (or pre-opening validation mode) for inbound putaway, storage replenishment, wave pick and dispatch confirmation.

Next actions

1. Classify all warehouse locations and inventory statuses into the four cutover buckets: free storage, picked/staged, in-flight receiving and quarantine/hold.
2. Enforce a 48-hour pre-cutover drain schedule to finish or reverse partial picking waves and close open cycle counts before freezing the legacy WMS.
3. Run a full mock cutover in staging using a live snapshot of open orders and staged pallets, testing that the new WMS location directives can pick and ship migrated stock.
4. Require joint sign-off from Operations, Finance, Quality and IT on the zero-variance reconciliation table before releasing the first live wave.