Acumatica Data Migration Field Mapping Worksheet
Data migration fails more often on unclear mapping than on tooling. This worksheet gives every legacy field a target screen, a rule, an owner and a status so nothing is loaded on assumption.
| Business object | Legacy field | Acumatica screen | Acumatica field | Transform rule | Record count | Bad data % (%) | Records to fix | Data owner | Status | |
|---|---|---|---|---|---|---|---|---|---|---|
111 | ||||||||||
1,034 | ||||||||||
13 | ||||||||||
496 | ||||||||||
6 |
Screen IDs shown are typical examples. Confirm them in your Acumatica version and edition, and check whether manufacturing screens are present before loading.
Get an expert review of your migration mapping
Send your completed mapping and we will point out missing required fields and cleansing risks.
Optional. The tool and every export work without this. No spam.
How to use the worksheet
Add one row per field or field group that must move. Pick the business object, name the legacy field, then record the Acumatica screen and field where it lands. Write the transform rule in plain words so a second analyst can build the import scenario from it. Estimate record counts and the share you expect to be bad, and the sheet calculates records to fix. Update status after each test load. Export to Excel and circulate it to data owners weekly.
- One row per target field, not per table
- Name a business owner, not just an IT owner
- Record cross reference tables such as terms, UoM and tax codes
- Re-estimate bad data after every test load
How data typically loads into Acumatica
Acumatica loads data mainly through import scenarios (screen based imports driven by Excel or CSV files), the Data Import tools, and the contract-based REST API for programmatic loads. Master data loads before transactions: segments and subaccounts, chart of accounts, customers, vendors, items, then BOMs, then open orders and balances. Because import scenarios mirror the screen, the mapping should name the screen field rather than the database column. Required fields and validation on the screen apply during the import.
Reading the summary
The overall bad data rate is a weighted figure. A rate under about 5 percent across masters usually means cleansing can run in parallel with configuration. Above 15 percent on items or BOMs is a schedule risk, because routings and costing depend on them. Look at which rows contribute most to records to fix and assign extra cleansing effort there before the second test load.
Common mistakes
Teams often map only the fields they use today and miss fields that Acumatica requires, such as posting classes, tax zones or default warehouses. They also forget to map status values, so closed legacy orders reappear as open. Another frequent gap is unit of measure conversions on BOM quantities. Finally, sign off should be by the data owner after reviewing loaded records in Acumatica, not by the analyst who ran the import.
Frequently Asked Questions
Does this worksheet load data into Acumatica?
No. It is a planning and tracking document that runs in your browser. You use it to define mappings and rules, then build import scenarios or API loads in Acumatica from those definitions. Nothing you type is sent anywhere unless you choose to contact us.
How many test loads should I plan?
Most SMB manufacturers plan at least two full test loads before cutover, plus a final dress rehearsal that times the process. Each test load should produce an updated bad data estimate in this sheet so you can see whether cleansing is converging.
Should open transactions be migrated?
Usually only open sales orders, open purchase orders, open AR and AP, inventory balances and GL balances move. History is often archived or loaded in summary. Decide per object and record the decision in the rule column so the scope is visible.
Can I add my own columns?
The browser tool uses a fixed column set, but once exported to Excel you can add columns such as test load date, defect IDs or approver. Many teams keep the exported file as the master and refresh it weekly.
If you are moving from SyteLine, Baan, Epicor or another system and want mapping and cleansing automated with a private model, we can review your extract and suggest an approach.
Related Tools
ERP Cutover Weekend Plan Template (Acumatica and Sage)
A fill-in cutover runbook with freeze times, final data loads, validation steps, go/no-go criteria and a rollback plan. Exports to PDF or Word.
ERP Migration & SelectionSage Chart of Accounts Mapping Worksheet
Map old Sage accounts to a new chart, carry opening balances and check that debits equal credits before you load the trial balance.
Developer ToolsAcumatica Sales Order REST JSON Template
Generate the PUT request URL and JSON body to create a sales order with two lines through Acumatica's contract-based REST API.
Costing & FinanceSMB ERP Implementation Budget Calculator
Estimate year-one and five-year ERP cost from subscription, partner hours, data migration, training, internal staff time and contingency.
More ERP Migration & Selection tools
See all- ERP TCO Comparison Calculator (5-Year)
- ERP Migration Risk Assessment
- Data Migration Effort Calculator
- ERP Selection Scorecard for Manufacturers
- ERP Go-Live Readiness Checklist
- ERP Change Management Readiness Assessment
- ERP Integration Complexity Calculator
- Cloud vs On-Premise ERP Cost Calculator
- ERP Upgrade vs Replace Assessment