A successful ERP inventory migration must preserve the meaning of stock, not merely copy rows. Before importing a file, agree which items, locations, stock states and open transactions the new system will manage. Assign a business owner to approve each dataset.

Separate master data from quantities

Master data describes products, units, warehouses and locations. Transaction data records receipts, shipments and adjustments. Opening quantities describe stock at an agreed cutoff. Importing all three without a sequence can create missing references or duplicate balances.

Create a mapping sheet with the source field, destination field, transformation, owner and validation rule. For example, map a supplier’s carton to the internal base unit only after confirming the conversion for that particular product. Do not assume every carton contains the same number of units.

Clean records before the trial import

  • Resolve duplicate product codes and keep a cross-reference to retired codes.
  • Standardize units and location names without removing meaningful distinctions.
  • Separate available, reserved and blocked stock.
  • Identify inactive items that still have quantities or open orders.
  • Decide how much historical detail must remain accessible and where.

Do not delete unexplained negative quantities simply to make the import pass. Investigate the transaction or timing issue with the process owner and record the agreed correction.

Reconcile at a useful level

Compare quantities by item, warehouse and relevant stock state. A grand total can match even when stock is assigned to the wrong location. Where batches or serial numbers matter, include them in the comparison. Have the responsible finance team separately define and approve any valuation reconciliation.

For an illustrative trial, an old system reports 50 units in warehouse A and 30 in B. An import of 80 into A has the correct overall count but is not acceptable. Keep the comparison file, exception list and sign-off as migration evidence.

Write the cutover sequence

  1. Rehearse the export, transformation, import and reconciliation.
  2. Set a cutoff and document which operations pause or continue.
  3. Capture transactions occurring after the final export.
  4. Load the agreed opening data, then apply those later movements exactly once.
  5. Test receipt, reservation, shipment and return with business users.
  6. Approve launch or invoke the agreed recovery plan.

A recovery plan needs a decision owner, a decision deadline and instructions for reconciling any transactions already created in the new system. A backup alone does not explain how the business returns to a consistent working state.

What should be ready before launch?

Require a signed mapping sheet, resolved exceptions, a successful rehearsal, a named support contact and agreed acceptance evidence. If a critical stock difference remains unexplained, investigate it before expanding the rollout.

Our ERP development service can be scoped around these migration requirements. Share anonymized field examples and the planned transition boundaries through contact.