Migrate your Acumatica data

Business Account is Acumatica's primary CRM and AR entity. Standard fields map cleanly. Custom fields use the UDF extension framework and require explicit field-level mapping during migration.

Vendor records include AP settings, tax settings, and payment terms. All standard fields migrate directly; UDFs on Vendor require custom field mapping.

Items carry warehouse-specific quantity and availability data. We preserve item categories, units of measure, and stock item attributes. AvailabilityQty is a derived column updated by the system on recalculation.

GL accounts include account class, type, subaccount mask, and active/inactive status. We map account structures to the destination schema, preserving subaccount segmentation.

Project records include budgets, tasks, employees, and change orders. We extract the project hierarchy and associated transaction links. Project attributes and custom fields require mapping.

Sales documents carry line items, fulfillment details, and invoice links. Tax calculation depends on customer and item tax settings. We preserve document status to allow reactivation in the destination system.

PO records include vendor, line items, receipts, and amendments. We extract the full PO lifecycle and map document status. Receipts and amendments have separate schemas and are migrated as related records.

Open invoices carry payment schedules, terms, and aging data. Historical invoices may reference balance tables and require careful sequencing to preserve GL impact.

User-defined fields in Acumatica are stored in extension DACs and serialized under a 'custom' namespace in the REST API. Custom fields on Leads, Accounts, and other entities require explicit field discovery before migration.

Notes are stored in Note and NoteDoc tables linked by NoteID. Files are stored as separate records. We extract note text, related entity references, and binary attachments, then re-link them in the destination system.

Employee records include compensation history, department assignments, and timecard data. We preserve employment status, job titles, and earning codes. Effective-dated rows are migrated as separate records.

Warehouse records define physical locations with bin structures. We map warehouse assignments on inventory items and transfer orders. Multi-warehouse configurations are preserved with location-specific availability.

Tax setup includes categories, zones, and rules. Destination tax engines interpret these differently, so we flag the tax mapping requirement and let the customer decide whether to carry tax configuration records directly.

User accounts include role assignments, company associations, and tenant scope. We export users as contacts or employees in the destination. Role/permission mappings require manual configuration in most target systems.