Logistics migration playbook: how to switch 3PLs without stopping sales
Logistics Migration Playbook: How to Switch 3PLs Without Stopping Sales
Switching 3PLs without disrupting order flow requires three things in sequence: a signed inventory count both parties agree on, a defined cutover method with a hard data freeze date, and a structured handover for open returns and incidents. Miss any one of these and the migration fails at the cutover.
The decision to switch usually comes after something has broken — inventory discrepancies that couldn’t be explained, SLA failures that became routine, a peak season that exposed an operator without real controls. The frustration is legitimate. What makes the migration dangerous is letting that urgency compress the timeline past the point where fundamentals can be verified.
Why Migrations Fail Before They Start
Most 3PL migrations don’t fail during the move — they fail because the starting position was never confirmed. A brand transfers inventory from one provider to another without establishing what the first provider actually holds. The new 3PL receives pallets, conducts a receiving count, and finds discrepancies. Now there are three possible explanations: the old 3PL lost stock, the new 3PL miscounted during receiving, or the brand’s records were wrong from the beginning. Proving which is true — after the fact, with no baseline — is close to impossible.
The second failure pattern is an ambiguous cutover. Orders keep flowing into the old system while stock is mid-transit to the new one. A customer orders at midnight. The old 3PL has already handed over that SKU. The new 3PL hasn’t finished receiving. Nobody ships the order. The customer contacts support three days later. Nobody has a clear answer.
The third failure pattern is inheritance: returns and incidents that were open at the old 3PL are never formally handed over. Months later, those units appear as unexplained inventory differences. Those incidents remain unresolved. The cost arrives long after everyone has stopped looking for it.
3PL migration: The structured transfer of physical inventory, operational responsibility, data records, and open workflows from one logistics operator to another, executed without creating a gap in order fulfillment or inventory accuracy.
A migration that avoids these three failure modes is not fast by default. It is controlled by design.
Inventory Truth Before You Move Anything
Before a single pallet leaves the current 3PL, the inventory position must be established and signed off by both parties. This is the legal and operational baseline. Everything that happens after the migration is measured against this number.
The process starts with a full physical count request at the current 3PL — not a report from their WMS, but a count of every SKU, every variant, every location. The brand or a neutral third party should be present during the count, or at minimum receive the data in raw format: location, SKU, quantity per location. Aggregated summaries can hide discrepancies that location-level data makes visible. A summary that shows “4,800 units of SKU-12A” doesn’t reveal that 200 of them are in a damaged-goods bay no one mentioned.
Once the count is complete, compare it against the brand’s own records. Differences need resolution before the migration begins — not carried forward as a “to be sorted” item. The classic mistake here is accepting a count as “close enough” because the timeline is already under pressure. A 3% discrepancy that seems minor before migration becomes a 3% variance in the new 3PL’s opening inventory, which then compounds with every cycle count afterward. Unresolved discrepancies become disputes that are impossible to adjudicate once both parties have moved on.
Inventory sign-off artifact: A document — typically a spreadsheet — recording the agreed physical count by SKU and location at a specific date and time, confirmed in writing by both the brand and the outgoing 3PL. This document is the baseline against which the incoming 3PL’s receiving count is reconciled.
The incoming 3PL must also conduct a receiving count when stock arrives. That count is reconciled against the sign-off artifact. Any difference between what the outgoing 3PL certified and what the incoming 3PL received is a discrepancy that requires immediate documentation — not a post-launch issue to investigate later when both parties are less motivated to find the answer.
Data Freeze and Cutover Method
With inventory truth established, the next decision is how orders transfer. The cutover date is the moment when the old 3PL stops processing new orders and the new one begins. Everything around this date must be precisely defined, because ambiguity here is exactly what creates the scenario where nobody ships an order.
Data freeze date: A point in time — typically 12 to 48 hours before physical cutover — at which no new orders are accepted into the old 3PL’s system. Orders placed after this point queue for the new 3PL. Orders placed before this point are completed by the old 3PL.
There are two cutover methods. The right choice depends on order volume, catalog complexity, and how much operational overlap the brand can manage.
In a parallel cutover, both the old and new 3PL are operational for a defined overlap window. The old 3PL handles orders placed before the data freeze; the new 3PL handles orders placed after. Both systems run simultaneously — typically 48 to 72 hours — then the old 3PL is fully decommissioned. This reduces the risk of a fulfillment gap, but requires that inventory isn’t split across both locations during the overlap and that integrations are confirmed on both sides before orders go live.
In a hard cutover, the old 3PL fully stops on a specific date and time. All stock is at the new 3PL, order flow switches cleanly, and the old relationship ends. This is simpler to audit. The requirement is confidence that the new 3PL is genuinely ready — not “ready to receive,” but ready to pick, pack, and ship correctly from day one. Most brands underestimate this gap. “We can start receiving your stock” and “we are operationally ready to process live orders on Monday morning” are different commitments.
Sequencing the Physical Move
Knowing the cutover method determines how inventory moves. The timing of physical transfers is not just a logistics question — it’s an inventory accuracy question, because stock in transit is stock that belongs to neither system.
The practical approach is to sequence moves by SKU velocity. Slow-moving and seasonal stock moves first; these have the lowest order risk during transit. High-velocity SKUs — the ones generating daily orders — move last, as close to the confirmed go-live as possible. This minimizes the window when bestsellers are unavailable.
For each batch, the process is consistent: the outgoing 3PL certifies the batch count before loading, the stock moves under carrier custody, the incoming 3PL receives and counts against the certified number, and discrepancies are logged before the batch enters live inventory. Moving stock without transfer documentation means that any discrepancy discovered at arrival has no reference point.
Special stock is the most frequently neglected element: returned units pending disposition, damaged units in a hold bay, stock flagged for QC but not yet reviewed. These need a documented status and a clear decision before they move. Moving them commingled with live inventory transfers unresolved quality problems into the new operation. The questions that were open at the old 3PL become questions the new 3PL will ask — often at inconvenient moments.
Customer Promise Protection During Transition
The customer doesn’t see the migration. Their order was placed with the expectation of delivery within the time shown at checkout. That expectation doesn’t pause for operational events.
The highest-risk window for order fulfillment is immediately before and after the cutover. Three practical controls reduce that risk. First, a backlog review at the outgoing 3PL: all orders placed before the data freeze should be confirmed shipped — with tracking numbers — before the new 3PL is considered the only active operator. Any open order at the old 3PL at cutover needs a disposition decision: will the old 3PL complete it with a defined deadline, or will the new 3PL absorb the stock and complete it as a documented transfer? The worst outcome is an order without an owner.
Second, the new 3PL needs the brand’s full pack specifications before the first order processes. A customer receiving their first post-migration order from a new operator shouldn’t notice anything different. If the pack standard isn’t transmitted before go-live, the first orders reveal the gap — through customer service contacts, not through a pre-go-live check.
Third, escalation clarity must be established before the cutover, not after. The new 3PL team running their first day of live orders is not at full operational rhythm. When an exception occurs — a damaged unit at pick, an address validation failure, an order with missing information — there needs to be a defined escalation contact and a response commitment. The exception path compensates for the performance gap that is normal in week one.
Returns and Incidents in Transit
Open returns and active incidents at the old 3PL don’t resolve because a migration happened. They continue — and if ownership wasn’t transferred explicitly, they become permanent exceptions that no one has authority to close.
The handover protocol for returns has three layers. The first is a list of all return shipments currently in transit: tracking numbers, expected contents, expected arrival dates. These units will arrive at the outgoing 3PL address after the migration. The outgoing 3PL needs a handling instruction for each: forward to the new address, hold and notify, or process according to the returns policy and transfer the disposition record.
The second layer is returns currently held at the outgoing 3PL — graded, pending grade, or awaiting brand decision. These need a physical inventory and a disposition decision before they move. Ungraded returns are particularly problematic: transferring them without grading moves an unresolved quality question into the new operation. The new 3PL will grade them on arrival and may disagree with what the brand assumed about their resalable value.
The third layer is open incidents: carrier claims, damage investigations, shortage disputes. These require formal handover with all supporting documentation — photos, carrier correspondence, exception logs, timestamps. An incident opened at the old 3PL but transferred without documentation typically closes without resolution. The evidence chain breaks, and the claim fails.
Returns handover artifact: A document listing all return shipments in transit, all held return units with their current status, and all open incidents with their documentation. Both the brand and the outgoing 3PL confirm this document before migration completes.
Acceptance Criteria: When Is the Migration Done?
“Done” is a specific state. Brands that don’t define acceptance criteria in advance find themselves managing a migration that technically ended weeks ago but is still generating surprises.
The migration is complete when five conditions are verified. The receiving count at the new 3PL matches the sign-off from the outgoing 3PL, or all discrepancies are documented and resolved. Order flow is routing to the new 3PL correctly — not just accepted, but picked, packed, and dispatched with proof of shipment. All open returns from the handover list have arrived at a defined location and been triaged. All open incidents from the handover list are either resolved or formally transferred with documentation. The old 3PL has no active inventory in their system attributed to this brand.
Until these five conditions are met, the migration is open. The temptation is to declare completion when order flow resumes. But inventory reconciliation, returns processing, and incident closure often trail by two to four weeks. Leaving these open creates the post-migration anomalies — inventory differences that appear without explanation, claims that go stale — that eventually force a re-investigation of the migration itself.
The first week after cutover is not standard operations. It is a monitored pilot with live volume. Exception rates, pick accuracy on the first orders, inbound receipt confirmation for the first new deliveries — these are signals about what the migration missed. Each exception in week one should be investigated as a system signal, not handled as a one-off.
Frequently Asked Questions
Q: How long does switching 3PLs typically take? A: The planning and preparation phase — establishing inventory truth, selecting a cutover method, setting up integration, and documenting open workflows — typically takes four to six weeks. The physical cutover window depends on inventory volume and catalog complexity. A brand with fewer than 50 SKUs and moderate inventory can often complete the physical move in 48 to 72 hours; a larger catalog with high inventory depth may need one to two weeks for sequenced moves. Total elapsed time from decision to live orders at the new operator is typically six to ten weeks for a managed migration.
Q: Can we switch 3PLs without pausing order fulfillment? A: Yes, with a parallel cutover. New orders route to the new operator while the outgoing operator processes its backlog and handles in-transit returns. The brand manages two operator relationships simultaneously during the overlap window, which adds coordination complexity. This is appropriate when order volume is high enough that a fulfillment pause would create real customer impact. The requirement is that integrations are confirmed on both sides before new orders go live at the incoming operator.
Q: What happens to inventory discrepancies found at the new 3PL? A: Discrepancies between the signed departure record and the arrival count at the new operator are investigated against the departure documentation. Units that were confirmed at departure but missing or damaged at arrival were lost or damaged in transit — a carrier claim or dispute with the transit handler, not a new operator error. Units noted as discrepant in the departure record were already documented; those are claims against the outgoing operator. The signed departure artifact is what makes this distinction possible.
Q: What data should I export before leaving my current 3PL? A: Minimum exports: full inventory file by SKU with lot and location data, order history for at least 12 months, open orders with their current status at cutover, an exception log covering the last six months, and returns records. Confirm the format the new operator requires before exporting — a data set exported in the wrong format that requires manual rework at the handover point delays go-live and creates mapping errors.
Q: What is the most common cause of migration failure? A: Treating the cutover as a calendar date rather than a condition. A migration date that’s fixed in the calendar regardless of whether acceptance criteria are met produces a go-live on incomplete data, unconfirmed integration, and unresolved open workflows. The cost of delaying cutover by 48 to 72 hours to confirm readiness is always lower than the cost of recovering from a live operation that started on bad data.
If you’re planning a 3PL migration and want to map the inventory proof, data handshake, and cutover sequence for your specific operation, a structured scope conversation is the right starting point.