# SAP Business One Data Migration Mapping Worksheet > Source: https://netray.co/tools/sap-b1-data-migration-mapping-worksheet > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: Free Tools ## Short answer An editable tracker that maps legacy data to Business One objects with record counts, cleansing progress and owners. ## Category sap ## Erp SAP Business One ## Audience - B1 consultant - Data migration lead - Project manager - Key user ## Tool **Kind:** worksheet **Mode:** editable **Columns:** #### B1 object **Key:** object **Type:** select **Options:** - Business partners - Items - Bills of materials - Warehouses and bins - Chart of accounts - Opening stock - Open sales orders - Open purchase orders - AR open items - AP open items #### Legacy source **Key:** legacy **Type:** text #### Mapping note **Key:** mapping **Type:** text #### Data owner **Key:** owner **Type:** text #### Legacy records **Key:** records **Type:** number #### Cleansed and ready **Key:** clean **Type:** number #### Ready **Key:** pct **Type:** number **Expr:** if(gt(records, 0), clean / records * 100, 0) **Format:** percent #### Status **Key:** status **Type:** select **Options:** - Not started - Mapping - Cleansing - Test load done - Reconciled **Rows:** **Object:** Business partners **Legacy:** Customer and vendor tables **Mapping:** Split by type, one code per partner **Owner:** Finance **Records:** 1850 **Clean:** 1420 **Status:** Cleansing **Object:** Items **Legacy:** Part master **Mapping:** Item group and UoM group derived from class **Owner:** Engineering **Records:** 6400 **Clean:** 3900 **Status:** Mapping **Object:** Bills of materials **Legacy:** Product structure **Mapping:** Active revisions only **Owner:** Engineering **Records:** 920 **Clean:** 300 **Status:** Mapping **Object:** Opening stock **Legacy:** Stock by location **Mapping:** Count at cutover, by warehouse **Owner:** Warehouse **Records:** 3100 **Clean:** 0 **Status:** Not started **Object:** AR open items **Legacy:** Receivables ledger **Mapping:** Open invoices only **Owner:** Finance **Records:** 410 **Clean:** 410 **Status:** Reconciled **Totals:** #### Total legacy records **Key:** records **Agg:** sum **Format:** integer #### Total cleansed **Key:** clean **Agg:** sum **Format:** integer **Summary:** #### Overall readiness **Key:** overall **Expr:** if(gt(sum_records, 0), sum_clean / sum_records * 100, 0) **Format:** percent **Primary:** true #### Objects tracked **Key:** objects **Expr:** count **Format:** integer **Notes:** 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. ## Content **Intro:** 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. **Sections:** #### How to use the worksheet **Body:** 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 **Body:** 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. **Bullets:** - Agree what history is migrated and what is archived - Load masters before transactions - Reconcile counts and totals after each load #### Reading the percentages **Body:** 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 **Body:** 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. **Cta:** Netray can help profile legacy databases for duplicates and gaps before you load. We work read-only and can run on-premises. **Faq:** #### Which tool loads data into Business One? **Answer:** 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? **Answer:** 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? **Answer:** 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? **Answer:** 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. ## Search terms sap business one data migration template, sap b1 dtw mapping, data migration mapping worksheet excel, erp data migration tracker, sap b1 data transfer workbench, legacy to sap business one mapping, data cleansing tracker template --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json