3PL Data Migration Checklist: What to Prepare Before Your Fulfilment Go-Live

Before a 3PL go-live, you need clean, agreed data in ten areas: item master, stock snapshot and cut-over counts, open orders, channel mappings, carrier services, customer and returns data, historic order data, user access, a test plan and sign-off. Most go-live problems are data problems that look like warehouse problems. A wrong weight becomes a wrong carrier charge. A missing barcode becomes a stock discrepancy. Preparing the data early is the cheapest way to protect launch week.

Why data decides go-live

A new third-party logistics provider can only pick, pack and ship what its warehouse management system knows about. If the item master is incomplete, stock cannot be booked in accurately. If channel mappings are wrong, orders drop into exceptions instead of picking. Each gap costs time in the first weeks, when customers are least forgiving and your team is most stretched.

Treat data as its own workstream, with an owner on your side and a deadline in the project plan. Ensuring complete data visibility from day one avoids costly inventory reconciliation errors downstream.

The checklist

1. Item master

This is the foundation. For every SKU, prepare:

• SKU code and description, matching your store and marketplaces exactly
• barcode (EAN or UPC) for each unit, and case barcodes where relevant
• dimensions and weight, measured rather than estimated
• batch, lot or expiry flags where the product needs them
• kit and bundle definitions, with the components and quantities for each
• any handling notes, such as fragile or temperature-sensitive

Measured dimensions matter commercially. Carrier charges and packaging choices both depend on them. Proper sku mapping during this phase ensures that your item master data 3PL requirements are fully satisfied before physical inventory is transferred.

2. Stock snapshot and cut-over counts

Take a stock snapshot from your current system, then agree how the physical count at cut-over will work. Decide who counts, when stock stops moving at the old location, and how discrepancies are resolved. For a switch between third-party logistics providers, reconcile what the old provider reports against what arrives. A tightly controlled stock cut-over count prevents inventory shrinkage and financial discrepancies during the transition.

3. Open orders

List orders that will be open at cut-over: unshipped orders, pre-orders, back-orders and any wholesale orders in progress. Agree which system ships each one, so nothing ships twice or not at all.

4. Channel mappings

Map each sales channel to the third-party logistics provider: your webstore, marketplaces, wholesale and retail accounts. Check that SKU codes, shipping methods and order statuses match on both sides. This is where integration errors usually start.

5. Carrier services

Map each shipping option your customers see to a carrier service the third-party logistics provider will use. Include international services, weight bands and any retailer delivery requirements.

6. Customer and returns data

Agree what customer data the third-party logistics provider needs for despatch and returns, and how it is transferred and protected. Set out your returns rules: reasons, grading, what goes back to stock and what does not.

7. Historic order data

Share at least a year of order history by SKU, channel and day if you have it. It helps the provider plan labour, slotting and peak capacity. It is also the baseline you will compare performance against.

8. User access

List who on your team needs access to the provider portal and what each person should see or do. Remove anyone who no longer needs access to your old systems.

9. Test plan

Write the tests before go-live: a single order, a multi-line order, a bundle, an international order, a return, an order amendment and a cancellation, across every channel. Rigorous 3PL integration testing guarantees that data flows smoothly between systems.

10. Sign-off

Agree who signs off each area and what ready means. Go-live should follow sign-off, not a date on its own.

How data handover compares across approaches

Whether you are comparing James & James Fulfilment, Walker Logistics, Zendbox or another provider, ask how data is exchanged and who checks it.

There are several ways to transfer data to a 3PL, and each approach places responsibility for errors in a different area. With a spreadsheet handover, the brand sends files that the 3PL uploads, so errors may only become visible during goods-in or the first picking activity. A self-service portal allows the brand to create SKUs and send pre-advice directly, giving the brand greater control but also making it responsible for data accuracy and following the 3PL’s guidance. With integration and support, API or file feeds move data between systems and are tested jointly, meaning the reliability of the process depends heavily on the quality of that testing.

How we handle it at Fulfil with Synergy

Onboarding at Fulfil with Synergy is led by our highly tenured Onboarding Manager, Bethany Waugh, supported by a cross-functional team, and runs to a joint project plan. Data is part of that plan from the start. We can also work to your timeframes.

We connect through API, flat-file SFTP and SOAP web services, with technical documentation and hands-on support. Our client portal lets you create SKUs and manage pre-advice directly, so the item master and inbound data sit where you can check them. Our technology and automation page covers the systems behind this.

For Boody, we ran a phased onboarding before launch, and orders were picked immediately after go-live. You can read the detail in the Boody case study. Managing 3PL onboarding data effectively is critical for brands transitioning to a new logistics partner.

Common data mistakes

• Estimating weights and dimensions. Estimates lead to wrong carrier charges and packaging choices.
• Different SKU codes in different channels. One SKU with three codes becomes three stock records.
• Skipping kit definitions. Bundles without a bill of materials cannot be picked correctly.
• Testing only the happy path. Returns, amendments and cancellations can fail even when standard orders work.

For the wider sequence, see what a fulfilment onboarding timeline looks like week by week and how to switch 3PL providers without disrupting your customers. Switching 3PL data seamlessly requires adhering to a structured fulfilment go-live checklist.

FAQ

What data does a 3PL need before go-live?

A third-party logistics provider needs a complete item master, a stock snapshot, open orders, channel and carrier mappings, customer and returns rules, historic order data, a list of portal users and an agreed test plan. The item master is the most important: SKU codes, barcodes, measured dimensions and weights, batch or expiry flags and kit definitions for every product. Without it, stock cannot be booked in or picked accurately. Historic order data helps the provider plan labour and space. At Fulfil with Synergy, this data is built into a joint project plan led by our Onboarding Manager, so each area has an owner and a deadline before go-live.

How do you handle stock counts when switching 3PL?

Agree the process before the move. Take a system snapshot from your current provider, set a point when stock stops moving, then count physically when it arrives at the new warehouse. Reconcile the two figures by SKU and, where relevant, by batch. Decide in advance who resolves differences and how, so the count does not delay go-live. If batch or expiry dates apply, check them during the count as well. Plan the timing so stock is booked in and sellable before your channels switch over. A careful cut-over count protects your cash position, because stock that is lost or miscounted during a move is often written off rather than recovered.

How long should 3PL integration testing take?

It should take as long as it needs to pass every agreed test, rather than a fixed number of days. The length depends on how many channels you sell through, how complex your products are and whether you use bundles, international shipping or retail orders. Write the test plan early and include single orders, multi-line orders, bundles, returns, amendments and cancellations for every channel. Testing only standard orders is a common reason for problems after go-live. At Fulfil with Synergy, we integrate through API, SFTP and SOAP web services with hands-on technical support, and testing sits within the joint project plan.

Can I create SKUs myself in the 3PL system?

Often, yes, and it helps keep data accuracy high because the people who know the products enter them. At Fulfil with Synergy, our client portal lets you create SKUs and manage pre-advice directly, as well as monitor inventory, track orders and download reports. Self-service works best alongside clear guidance on required fields, such as barcodes, measured weights and batch flags, so records are complete from the start. For large catalogues, a bulk upload or integration is quicker. Either way, it is worth checking a sample of records together before the first delivery arrives, so errors are fixed before stock is booked in.

A good go-live starts with data that has an owner, a deadline and a sign-off. Work through the checklist early, fix gaps before stock moves, and test the orders most likely to break. Implementing a thorough data cleansing routine prior to migration ensures long-term inventory accuracy across your warehouse management system.

If you want to plan a migration with a team that runs onboarding as a joint project, get in touch.

‍