# Acumatica Data Migration Field Mapping Worksheet

> Source: https://netray.co/tools/acumatica-data-migration-field-mapping-worksheet
> Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems.
> Section: Free Tools

## Short answer

Map each legacy field to its Acumatica screen and field, record the transform rule and owner, and track cleansing status. Exports to Excel.

## Category

erp-migration

## Erp

Acumatica

## Industry

Discrete Manufacturing

## Audience

- ERP consultant
- Implementation lead
- Data migration analyst

## Tool

**Kind:** worksheet

**Mode:** editable

**Columns:**

#### Business object

**Key:** object

**Type:** select

**Options:**

- Customer
- Vendor
- Stock Item
- Non-Stock Item
- BOM
- Routing
- Open Sales Order
- Open Purchase Order
- GL Balance
- Open AR
- Open AP
- Employee

#### Legacy field

**Key:** src_field

**Type:** text

#### Acumatica screen

**Key:** acu_screen

**Type:** text

#### Acumatica field

**Key:** acu_field

**Type:** text

#### Transform rule

**Key:** rule

**Type:** text

#### Record count

**Key:** records

**Type:** number

**Format:** integer

#### Bad data %

**Key:** bad_pct

**Type:** number

**Unit:** %

#### Records to fix

**Key:** bad_records

**Type:** number

**Expr:** records * bad_pct / 100

**Format:** integer

#### Data owner

**Key:** owner

**Type:** text

#### Status

**Key:** status

**Type:** select

**Options:**

- Not started
- Mapped
- Cleansing
- Loaded in test
- Signed off

**Rows:**

**Object:** Customer

**Src field:** CUST_NAME

**Acu screen:** Customers (AR303000)

**Acu field:** Customer Name

**Rule:** Trim, title case, max 60 chars

**Records:** 1850

**Bad pct:** 6

**Owner:** Sales ops

**Status:** Cleansing

**Object:** Stock Item

**Src field:** ITEM_NO

**Acu screen:** Stock Items (IN202500)

**Acu field:** Inventory ID

**Rule:** Strip spaces, upper case, apply segment mask

**Records:** 9400

**Bad pct:** 11

**Owner:** Materials

**Status:** Mapped

**Object:** Vendor

**Src field:** VEND_TERMS

**Acu screen:** Vendors (AP303000)

**Acu field:** Terms

**Rule:** Map NET30 to Terms ID in cross reference

**Records:** 420

**Bad pct:** 3

**Owner:** Purchasing

**Status:** Loaded in test

**Object:** BOM

**Src field:** COMP_QTY

**Acu screen:** Bill of Material (AM208000)

**Acu field:** Quantity Required

**Rule:** Convert to stocking UoM

**Records:** 6200

**Bad pct:** 8

**Owner:** Engineering

**Status:** Not started

**Object:** GL Balance

**Src field:** ACCT_BAL

**Acu screen:** Journal Transactions (GL301000)

**Acu field:** Debit/Credit Amount

**Rule:** Trial balance as of cutover date, by subaccount

**Records:** 640

**Bad pct:** 1

**Owner:** Controller

**Status:** Mapped

**Totals:**

#### Total records

**Key:** records

**Agg:** sum

**Format:** integer

#### Records needing fixes

**Key:** bad_records

**Agg:** sum

**Format:** integer

**Summary:**

#### Overall bad data rate

**Key:** bad_rate

**Expr:** sum_bad_records / sum_records * 100

**Format:** percent

**Primary:** true

**Description:** Share of records that need cleansing before the load.

**Notes:** Screen IDs shown are typical examples. Confirm them in your Acumatica version and edition, and check whether manufacturing screens are present before loading.

## Content

**Intro:** 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.

**Sections:**

#### How to use the worksheet

**Body:** 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.

**Bullets:**

- 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

**Body:** 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

**Body:** 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

**Body:** 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.

**Cta:** 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.

**Faq:**

#### Does this worksheet load data into Acumatica?

**Answer:** 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?

**Answer:** 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?

**Answer:** 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?

**Answer:** 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.

## Search terms

acumatica data migration template, acumatica import scenario mapping, erp data mapping worksheet excel, legacy to acumatica field mapping, acumatica data cleansing checklist, erp data migration mapping template, acumatica implementation data load plan

---
Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json