Migrate from Acumatica to Microsoft Dynamics 365 Business Central

Acumatica Business Account consolidates commercial entity and individual contact points in one record. Dynamics 365 separates Account (the commercial entity: company name, address, industry) from Contact (the individual: name, email, phone, job title). We decompose each Business Account into one Account record and one or more Contact records linked by a PartyID relationship. The Acumatica primary contact flag maps to the Contact's IsPrimary flag in Dynamics 365. Address data splits into the Account's BillTo and ShipTo addresses versus the Contact's address.

Acumatica Vendor records map directly to Dynamics 365 Vendor. AP settings, tax registration, payment terms, and the default GL account assignments migrate as-is. We resolve the Acumatica VendorClass reference to the corresponding Vendor Group in Dynamics 365 and preserve any UDF values stored on the Vendor DAC.

Acumatica Inventory Items map to Dynamics 365 Items with the Item Type determining whether it is an Inventory or Service item. Unit of measure conversions, item categories, and stock item attributes migrate as Item attributes and Item variants. Availability quantities and warehouse-specific data are derived from the inventory posting group and migrate as on-hand snapshots rather than live quantities.

Acumatica GL Accounts map to Dynamics 365 G/L Accounts with account type, posting type, account class, and subaccount segmentation preserved. Acumatica's subaccount mask structure maps to the Dimensions framework in Dynamics 365 Finance/SCM or the Direct Posting category in Business Central. We preserve active/inactive status and retain account number formatting for reconciliation continuity.

Acumatica Project records, including budgets, tasks, employee assignments, and change orders, map to Dynamics 365 Project Management. The project hierarchy, WBS (Work Breakdown Structure) tasks, and cost/billing rate tables migrate as Project tasks with assigned workers and journal lines. Project attributes and custom fields require explicit mapping from the Acumatica UDF namespace.

Acumatica Sales Orders migrate to Microsoft Dynamics 365 Sales Orders with line items, fulfillment details, and invoice links preserved. Document status is carried over to allow reactivation. Tax calculation settings on the order header are resolved against the destination tax setup during migration rather than preserving Acumatica's calculated tax amounts.

Acumatica Purchase Order records migrate to Dynamics 365 Purchase Orders with vendor, line items, and receipt links preserved. Amendments and receipts have separate schemas in Acumatica and migrate as related Purchase Order lines or separate Receipt records depending on the destination edition.

Open and historical AR invoices from Acumatica migrate to Dynamics 365 Customer Invoice. Payment schedules, terms, and aging data are preserved in the invoice header and line distributions. Closed invoices carry forward as historical records with their original GL impact documented for audit trail purposes.

Acumatica AP invoices migrate to Dynamics 365 Vendor Invoice records. Tax information and expense distributions are re-mapped to the destination GL account structure. Open AP aging reports are preserved for payable reconciliation after migration.

Acumatica User-Defined Fields stored under the 'custom' namespace in the REST API are extracted using the entity schema endpoint and mapped to Dynamics 365 custom fields created in the relevant Dataverse extension tables or Business Central custom fields. CustomStringField maps to Text, CustomDateField to Date, and CustomNumberField to Decimal or Integer. We discover all UDF definitions during scoping and pre-create the destination schema before any data load.

Acumatica Note records (text content, EntityID, EntityType) and NoteDoc binaries (linked file storage) are extracted from the separate Note and NoteDoc tables. In Dynamics 365, Note text migrates to the Notes entity linked to the target record (Account, Contact, Item, Project, or Order). Binary attachments migrate to SharePoint document storage with a DocumentLocation record pointing to the file URL.

Acumatica Employee records, including compensation history, department assignments, job titles, and earning codes, migrate to Dynamics 365 Human Resources Worker records. Effective-dated rows (multiple employment periods, pay rate changes) are migrated as separate Worker employment detail records. Employment status maps to the Worker Hire and Termination dates.

Acumatica Warehouse records with bin structures map to Dynamics 365 Warehouse configurations. Location-specific inventory assignments on items are preserved as warehouse-specific data. Multi-warehouse configurations migrate with location-specific posting group assignments.

Acumatica's tax configuration involves separate Tax Category, Tax Zone, and Tax Rule tables with cross-references. Dynamics 365 consolidates tax setup into Tax Groups, Tax Codes, and Tax Posting Setup. We flag the tax mapping requirement during scoping and deliver a written tax configuration guide; the customer's finance team or Dynamics partner rebuilds tax rules in the destination to ensure jurisdictional accuracy post-migration.