Migrating Inventory to a WMS: A Go-Live Checklist

What moves during a WMS migration?

A WMS migration moves operational records from spreadsheets or an existing application into a new warehouse system. Decide whether the initial scope needs only master records and opening balances or also open orders and historical transactions. These have different validation requirements.

Assign an operational data owner. Developers can validate a file format but cannot decide which conflicting stock balance reflects the warehouse.

Clean SKU records before importing balances

• Use a unique and consistent SKU code.
• Define purchasing and selling units alongside conversion rules.
• Separate inactive items from the initial operational catalog.
• Check bin locations and relevant lot or expiry information.
• Resolve negative balances and missing locations with the process owner.

Do not merge records just because their product names look similar. Confirm specifications and units first.

Run a trial import

Use a copy of the data to check dates alongside decimal formats and required columns. The import should identify rejected rows so the owner can fix them. Preserve the original source file.

Planning example: one SKU sits in two bins. Matching its warehouse total is insufficient when the balance in each bin is wrong. Validate the level of detail needed for picking.

Reconcile and agree on a cutover

1. Compare SKU counts and balances per warehouse against the approved source.
2. Validate valuation only if its method and scope are part of the project.
3. Define when old-system transactions stop and who handles outstanding activity.
4. Import approved final opening balances.
5. Check that receiving and dispatch change stock correctly.

Prepare recovery and sign-off

Agree on conditions for postponing launch and on recovery steps if reconciliation fails. Keep source snapshots alongside import records. After cutover identify one system of record so staff do not maintain competing balances.

Warehouse and process owners should approve readiness. Migration duration depends on data quality and workflow complexity.

Common migration questions

Must every historical transaction move?

Not always. Balance audit and reporting requirements against cleanup effort. An accessible archive may be appropriate if agreed with the responsible team.

Should we count physical stock?

When source balances are unreliable a physical check can form part of preparation. Agree on its scope before approving opening balances.

Next steps

Build a brief with the WMS scope planner and checklist. Explore Nodic WMS development or review WMS budgeting considerations for SMEs.