Migrate from Accura to Acumatica

Accura customer records contain billing and shipping in one structure. FlitStack AI splits these into Acumatica's Customer header and one or more Location records linked by LocationID. The primary contact email and phone migrate to the Contact tab on the Customer screen.

Accura vendor data maps to Acumatica's Vendor screen (AP303000). Remit-to and Remit-to Location records are created based on the source vendor's payment address. Tax ID and 1099 settings are translated to the corresponding Acumatica Vendor fields. Vendor references in purchase orders and bills resolve to the migrated vendor records.

Accura inventory items map 1:1 to Acumatica Inventory Items (IN202500). Item class assignments are preserved as Inventory Item Class records in Acumatica. Stock items, non-stock items, and service items are distinguished by Item Type on the General tab, ensuring proper inventory type classification in the target system.

Accura chart-of-accounts entries become Acumatica GL Accounts (GL202500). Each account requires assignment to an Account Group (which defines the financial statement section) and must be marked Active and Posted allowed. Branch access is configured if Acumatica's multi-branch model is in use.

Accura sales orders migrate to Acumatica Sales Orders (SO301000) with customer and line-item references resolved to Acumatica Customer and Inventory Item records. Order types map to Acumatica order types. Status and fulfillment data is preserved as custom fields if source values exceed Acumatica's standard pick-list.

Accura purchase orders map to Acumatica Purchase Orders (PO303000). Vendor references are resolved to Acumatica Vendor records. Line-level details including item, quantity, unit cost, and extended amounts migrate with the order header. Receipts and bills are not created automatically — those remain as Acumatica-side transactions created post-migration.

Accura AR invoices migrate to Acumatica AR Invoices. Open invoices become AR301000 documents; historical paid invoices are migrated as read-only records to preserve financial history. Invoice lines map to detail lines with Inventory ID or GL Account lines as appropriate.

Accura vendor bills map to Acumatica Bills (AP301000). Vendor references resolve to Acumatica Vendor records by vendor ID or name matching. Due date, payment terms, and hold status are preserved from the source. Historical paid bills migrate as completed records for audit continuity and reporting purposes.

Accura project or job records map to Acumatica Projects (PM301000). Project status, customer link, budget amounts, and project manager assignments migrate. Task structures in Accura map to PM Tasks under the Acumatica Project. Billing rules, rate tables, and approval workflows require Acumatica-side configuration after migration completes.

Accura custom fields are recreated as Acumatica custom fields (Usr-prefixed) on the relevant Data Access Class. Field type mapping converts text, numeric, and date custom fields to Acumatica's corresponding field types (string, decimal, datetime). Required-field flags are preserved, and custom field registration is validated against the DAC schema before data loads.

Accura user records split into Acumatica Employee records (for payroll and time tracking) and Acumatica User accounts (for login and role assignment). Email addresses are used to match Acumatica users to existing accounts; unmatched records are flagged for admin assignment.

File attachments associated with Accura records are downloaded and reattached to the corresponding migrated record in Acumatica using the Attachments feature available on each screen. The file name, description, and content type are preserved during the migration. File size limits follow Acumatica's attachment constraints per record type.