SAPFree worksheetPDF, Excel, Word exportSAP Business One

SAP Business One Data Migration Mapping Worksheet

Data migration is where Business One projects slip. This worksheet gives each object an owner, a mapping note, record counts and a status, so progress is visible and not a feeling.

Download:

B1 object	Legacy source	Mapping note	Data owner	Legacy records	Cleansed and ready	Ready	Status
						76.8%
						60.9%
						32.6%
						0%
						100%

Total legacy records

12,680

Total cleansed

6,030

Overall readiness

47.6%

Objects tracked

Business One data can be loaded with the Data Transfer Workbench (DTW) or other import tools, depending on your version and partner practice. Always load into a test company first and reconcile counts and values before the production load.

Legacy data profiling

Ask about a read-only profile of your legacy data for duplicates and gaps before migration.

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

How to use the worksheet

Add one row per object and source. Record how many legacy records exist and how many have been cleansed and approved for loading. The ready column calculates the percentage per row and the summary shows overall readiness weighted by record count. Update it weekly in the project meeting and export to Excel for the steering group.

Mapping and loading

For each object, write the mapping rule in plain words: which legacy field becomes which Business One field, which values are translated, which records are dropped. Business One offers the Data Transfer Workbench for bulk loads of objects such as business partners, items and some documents, and partners often use scripted loads for others. Whichever tool you use, run a test load, count records, and compare values before the production load.

Agree what history is migrated and what is archived
Load masters before transactions
Reconcile counts and totals after each load

Reading the percentages

A high average can hide a blocked object. Look at the lowest rows first. Items and BOMs usually lag because engineering must confirm which revisions are active. Opening stock is deliberately last because it depends on the cutover count. The status column tells you whether a row has only been cleansed or actually reconciled.

Common mistakes

Migrating dirty data on the theory that users will fix it later, loading transactions before the master data is stable, and skipping the test load. Another is never agreeing a data owner, so cleansing questions wait in an inbox.

Frequently Asked Questions

Which tool loads data into Business One?

Many projects use the Data Transfer Workbench, the DI API or partner scripts. The right choice depends on the object and volume. Your partner will usually propose one; the mapping worksheet is useful whichever you pick.

How much history should we migrate?

Master data and open items, plus balances. Full transaction history is rarely worth the effort. Keep older history in a read-only archive or the legacy system for audit and reference.

What does reconciled mean?

Counts and values in Business One agree to the legacy source or to an agreed control total, and a named person has signed it off. Loaded without reconciliation is not done.

How do I handle duplicates?

Resolve them in the legacy extract before loading. Decide a survivor record using tax ID, address and activity, and map retired codes so that history references still make sense.

Netray can help profile legacy databases for duplicates and gaps before you load. We work read-only and can run on-premises.

Talk to an Expert Explore More Free Tools

Related Tools

SAP

More SAP tools

See all

Back to All Tools