Migrate from Unit4 ERP to Acumatica

Unit4 GL accounts map to Acumatica Accounts using the account code as the AccountID. Where Unit4 uses multi-segment account codes, Acumatica's subaccount segments must be parsed and mapped to the correct SubID — this requires pre-migration segment configuration in Acumatica's Chart of Accounts screen.

Unit4 dimensions (up to 10 per entity) map to Acumatica subaccount segments. Each Unit4 dimension ID becomes a subaccount with the segment number embedded in its segment mapping. Multi-segment Unit4 accounts split into separate Account + Subaccount records in Acumatica.

Unit4 employee records (name, department, job title, employment status, FTE, hire date) map directly to Acumatica's Employee DAC. HR-specific fields — absence types, sick leave balances, contract hours — migrate as custom fields (Usr-prefixed) since Acumatica Employee does not natively store absence history.

Unit4 customer records (account name, tax ID, payment terms, credit limit, invoice address) map to Acumatica Customer. Where Unit4 stores multiple contacts per customer, Acumatica's Contact subtab holds additional contacts; the primary contact becomes the main Customer record link. If the customer has multiple locations, each location can be added as a separate location record in Acumatica, linked via the Location subtab.

Unit4 vendor records (vendor name, tax registration, payment terms, 1099 flag, remit-to address) map to Acumatica Vendor. Multi-address vendors from Unit4 require separate Acumatica locations configured under the vendor record. When a vendor has multiple remittance addresses, each address should be entered as a separate vendor location in Acumatica, linked via the Locations tab for proper payment processing.

Unit4 projects (cost codes, WIP status, budget, billing rule, funding source) map to Acumatica Projects with the project template carrying the billing rule. Unit4 grant funding codes map as custom fields on the Project DAC — Acumatica's grant management is a separate module available in the Nonprofit and Construction editions.

Unit4 open AR invoices map to Acumatica AR Invoice with original invoice number, due date, and line amounts preserved. AP bills map similarly. Historical paid invoices are migrated as read-only records with a Closed status flag; original posting dates and amounts carry forward for audit continuity.

Unit4 open purchase orders migrate to Acumatica Purchase Orders with line items, quantities, and promised dates. Lines linked to closed Unit4 vendors or inventory items are flagged for admin review before approval. PO status (Open, Closed, Cancelled) carries over exactly.

Unit4 timesheet entries map to Acumatica Time Entry records linked to Employee and Project. Billable vs. non-billable flags from Unit4 translate to the Acumatica TimeEntry Billable field. Approvals and submitted status are preserved in a custom status field since Acumatica uses a different approval workflow engine.

Unit4 expense reports with line items (expense category, amount, project code, receipt flag) map to Acumatica Expense Receipts. Attachment references from Unit4 are preserved as comments; actual receipt files are re-uploaded to Acumatica's file management. Expense categories are mapped to Acumatica Expense Receipt categories, and any project associations are preserved on the receipt lines for accurate project cost tracking.

Unit4 flexi-fields stored in extension tables (linked by entity ID) require creation of corresponding Usr-prefixed custom fields on the target Acumatica DAC before migration. Each flexi-field group-to-attribute mapping from the Unit4 API response translates to an Acumatica custom field definition. Value type mapping: Unit4 string fields become String custom fields; pick-list values become dropdown fields with the same option labels.

Unit4 workflow definitions and approval routing rules have no direct Acumatica equivalent and are not migrated. We export the workflow structure as a PDF and JSON export from Unit4 so your Acumatica admin can rebuild approval chains using Acumatica's Business Events and Screen-Based automation screens.

Unit4 financial reports and FRx-style statement definitions are not transferable. We provide a structured export of report metadata (report name, row/column definitions, filter criteria) so Acumatica report designers can rebuild equivalent Generic Inquiries and Report Designer layouts. We also include sample report templates and mapping notes to accelerate the rebuild process in Acumatica Report Designer.