Data & ERP readiness
Before an ERP move, give your item data an owner and a test.
Start with a representative sample, define who can resolve exceptions, and verify that the migrated records support the work your team needs to perform.
An export can look complete while still leaving important decisions unresolved. Two descriptions might refer to the same part. A purchasing unit might be unclear. An item may depend on a supplier reference that only one person understands.
Before preparing a large migration file, we would use a small, representative sample to expose those decisions. The sample gives operations and the implementation partner something concrete to review together.
Choose records that reveal the difficult work
Include a routine purchased item, something received in packs and used in eaches, an item with similar descriptions, and a record with an unresolved supplier or location question. Select examples from the workflows your business actually uses.
Write down what each record needs to support. Can a buyer identify the right supplier and purchase unit? Can receiving distinguish the item from a similar part? Can a counter understand the inventory unit?
Separate source facts from proposed changes
Keep the original values available alongside the proposed target values. Give each unresolved question an owner who can confirm the business meaning. Someone should be able to explain why a description, unit, or reference is changing.
| Record or decision | Review responsibility |
|---|---|
| Source item identity | Confirm the retained item and its relationship to similar records |
| Units and pack quantities | Verify how the item is purchased, stocked, and used |
| Target field mapping | Agree the destination and transformation with the implementation partner |
| Unresolved exception | Name the decision maker and the evidence needed |
Test what people need to do with the data
A successful file import is one check. The next question is whether the record supports the intended task. In an agreed test environment, have the relevant users work through representative business scenarios with the migrated sample.
For example, ask a buyer to locate a part and interpret its purchasing unit. Ask receiving to distinguish two similar items. Record what the user expected, what happened, and which source or mapping decision needs another review.
Coordinate these checks with the implementation partner’s test plan. The partner needs to confirm the target system behavior, supported corrections, and the wider dependencies around each record.
Define the handoff before expanding the sample
A useful preparation package includes the retained source, proposed values, agreed mapping, exception log, decision owners, and test results. Agree who can accept the package and what would send it back for correction.
Take ten representative item records, assign the open decisions, and define one operating test for each. Review that package before committing to the full cleanup or migration scope.
The result should help everyone see the work that is ready, the questions still open, and the responsibilities for the next stage.