ERP / OPERATIONS

Moving from spreadsheets to an ERP: a data migration checklist

A spreadsheet can hide decisions that an ERP needs to make explicit: which customer record is authoritative, what “available stock” means, and who can change a confirmed order. Before importing files, agree on those rules. Otherwise, a successful upload can still produce an unreliable system.

Start with one business workflow

Choose a complete workflow, such as quote → order → stock allocation → delivery. List the people and records involved at each step. This gives the migration a useful boundary: data should support a real task, not merely fill every field in the new system.

Decide separately what must remain operational and what can be kept in a searchable archive. Bringing every historic row into the first release adds work and can preserve old inconsistencies. Agree on retention needs with the people responsible for those records.

Choose an owner and a source for each dataset

Create a register of customer, product, supplier, stock and open-order data. For each dataset, name one business owner who can resolve conflicting values. The latest file is not automatically the most accurate file.

For teams working across the United States and Argentina, document currency and date conventions explicitly. Keep a currency code with each amount. A value such as 1,250 or a date such as 04/10 is ambiguous without a format rule. Preserve business identifiers as text when leading zeros matter.

  • Record the source system, export date, owner and expected row count.
  • Identify stable customer and product IDs; do not match records by display name alone.
  • Define units, time zones, required fields and rules for inactive records.

Write the mapping before the import

A useful mapping has five columns: source field, target field, transformation, validation rule and decision owner. Resolve missing or conflicting values explicitly; do not silently turn an unknown quantity into zero.

Hypothetical example: a stock sheet contains 120 units on hand and 15 reserved. If the new ERP stores both values, map them separately and verify that available stock becomes 105 under your agreed rule. Importing 120 directly as available stock would overstate what the business can sell.

Rehearse with representative records

Use a test environment and a small set that includes normal and awkward cases: duplicate customers, cancelled orders, accented names, empty optional fields and multi-currency transactions. Use synthetic or appropriately protected data, and restrict access to exports.

Then run a full rehearsal. Compare record counts, totals by currency, stock by location and open-order balances. Spot-check relationships: an order should still point to the right customer and its correct line items. Counting rows alone will not reveal those mistakes.

Define the switch and the way back

Name who can authorize the cutover. Decide when edits stop in the old system, how late changes are captured, and what evidence must be signed off before staff begin using the ERP. Keep a recoverable backup and test that it can be restored.

Rollback needs more than “restore the old file.” If users have entered new orders after the switch, decide how those changes will be reconciled before returning to the old system. Set a review window and assign an owner to investigate discrepancies rather than letting two systems drift apart.

Build a reconciliation sheet before choosing a launch date

Agree on the rule and the person who accepts each dataset. The sheet below is a planning example: replace it with your fields and checks. A matching total row count can still hide duplicate identifiers, missing order lines or stock assigned to the wrong location.

Keep rejected records in a review queue with a reason and an owner. Re-running an import should not silently create duplicates. Define stable identifiers and the handling of partial imports before the full rehearsal.

Example ERP migration acceptance sheet
DatasetCheckEvidence / approver
ProductsUnique product IDs, agreed units and required fields.Source-to-target exceptions reviewed by the catalog owner.
StockOn-hand and reserved quantities by product and location.Differences explained and accepted by operations.
Open ordersCustomer links, line items, quantities and remaining balances.Order-level comparison approved by the sales owner.
AmountsTotals separated by currency and agreed rounding rules.Comparison reviewed by the person responsible for the records.
AccessEach role can complete its tasks and cannot perform prohibited changes.Normal-path and access-denied test results.

Try the stock rule in our ERP demonstration

The Linx Labs demo lets you inspect one inventory rule with fictional data. Reset it and use Studio Display (LX-101): it starts with 32 units on hand, 3 reserved and 29 available. Create an order for 2 units: on-hand stock stays 32, reserved becomes 5 and available becomes 27.

Shipping that order produces 30 on hand, 3 reserved and 27 available. Alternatively, cancelling the newly created order returns the state to 32 / 3 / 29. These are separate branches. This demonstrates behavior to agree on before migration; it does not prove that your data has been imported or that a production ERP is ready.

What to include in an ERP migration brief

Start with the systems you use, approximate record counts, locations, user roles and one operational problem. List which history must stay searchable and which records must be active at launch. An anonymized list of column names is sufficient for the first scope discussion; do not send customer records or account credentials through the inquiry form.

Separate data cleanup, migration tooling, business modules, third-party connections and ongoing support in the proposal. Confirm who approves discrepancies, who can stop the cutover, and how orders entered after launch would be reconciled if a rollback becomes necessary.

TAKE IT WITH YOU

Your project checklist

  • Define one complete workflow, datasets, approximate volumes and archive needs.
  • Assign source-of-truth owners and stable IDs; agree units, dates and currencies.
  • Approve field mappings, duplicate handling, rejected-record review and safe re-runs.
  • Reconcile counts, relationships, balances and stock by location in a full rehearsal.
  • Verify stock rules and role permissions; record acceptance evidence and approvers.
  • Agree cutover, late-change capture, rollback reconciliation and post-launch ownership.
Download the checklist (.md)

Use this checklist as a starting point. Adapt it to your systems and responsibilities; it is not a completed implementation plan.

Plan your move from spreadsheets to an ERP

Tell us which tools you use, what is difficult to reconcile and which workflow should come first. We will discuss scope and dependencies before preparing a proposal.

Discuss my ERP project