ERP Migration & SelectionFree worksheetPDF, Excel, Word exportSYSPROSouth AfricaAll SYSPRO tools

SYSPRO Data Migration Mapping Worksheet

A migration succeeds or fails on the mapping, not on the load. This worksheet gives you one row per data object with the legacy source, the SYSPRO target, the rules applied, an owner and a status. Export it to Excel to share with the project team.

Free, optional. Reopen it on any device.

Download:

Data object	Legacy source	SYSPRO target	Transform or cleansing rule	Record count	Business owner	Status

Total records in scope

8,590

Objects tracked

Confirm exact target table and field names against your own SYSPRO version and the import methods you use. The targets above are common examples, not a full list.

Get a data quality profile of your legacy files

Optional: we can scan an extract and report duplicates, gaps and bad codes, on your own systems.

Optional. The tool and every export work without this. No spam.

Was this tool useful?

How to use it

Start with one row for every master and open item object you will move: customers, suppliers, stock, bills of material, routings, price lists, open sales orders, open purchase orders and opening balances. Name the legacy source and the target, then write the cleansing rule in plain words. Assign a named business owner, not a team. Update the status as each object moves from mapped to loaded in test, reconciled and signed off.

What good looks like

Each object has a rule that someone outside IT could read and agree to. Record counts are captured before and after, so you can show nothing was lost. Reconciliation is against a trusted figure, such as the audited trial balance for balances or a stock count for quantities. Sign off is by the business owner, with a date, before the object is loaded into the live company.

Count records before cleansing and after loading
Reconcile balances to the trial balance
Load into a test company at least twice before cutover
Keep the legacy extract files for audit

Common mistakes

Teams often migrate everything and clean later, which carries years of dormant customers and obsolete stock codes into the new system. Another frequent problem is changing stock code structure without a cross reference to the old code, which breaks supplier catalogues and historic reports. Finally, open transactions are loaded without agreeing a cutoff, so invoices and receipts are counted twice or missed.

Agree a cutover date and freeze rule
Keep an old code to new code cross reference
Do not load unverified bank details

Frequently Asked Questions

Is this specific to SYSPRO?

The example rows use SYSPRO targets, but the structure works for any ERP migration. Replace the target column with your own system's objects and the rest of the sheet still applies.

How do I choose what to migrate?

Migrate what the business needs to operate and report on, usually active master data, open transactions and opening balances. Keep older history in a read only archive or reporting database rather than loading it all.

Who should sign off each object?

A named business owner, such as the stores manager for stock or the credit controller for customers. IT can load the data, but only the owner can confirm it is complete and correct.

How many test loads should I plan?

Plan at least two full test loads before cutover, plus a final dress rehearsal. The first usually exposes mapping errors, and the later ones prove the fixes and the timing of the real cutover window.

If you have large or messy legacy data, we can profile it and produce a cleansing report before you load anything.

Talk to an Expert Explore More Free Tools