Migrate from Proteus ERP to Acumatica

Proteus ERP customers map directly to Acumatica's Customer screen. The Customer ID, name, billing address, shipping address, payment terms, and credit limit all have direct counterparts. Any Proteus custom properties on the customer record (e.g., region codes, account classifications) require pre-defined UDFs in Acumatica's Customer screen before migration.

Proteus ERP vendor records are migrated to Acumatica's Vendor screen, preserving vendor name, contact information, payment terms, and GL expense account defaults. Additional attributes such as tax ID, vendor classification, and default shipping addresses also transfer. For vendors operating across multiple sites, each distinct shipping location is created as a separate Vendor Location in Acumatica, allowing granular control over purchase orders and receipts per site.

Proteus ERP has a single inventory item table that covers both stock and non-stock goods. Acumatica separates these into Stock Item (with warehouse quantities) and Non-Stock Item (for services and expense items). FlitStack inspects the Proteus item's stock-on-hand values to route each record to the correct Acumatica item type. Items with warehouse quantities in Proteus become Stock Items; items with no warehouse presence become Non-Stock Items.

The Proteus ERP chart of accounts is transferred to Acumatica's GL Account screen, mapping account number, name, type (Asset, Liability, Equity, Revenue, Expense), and posting class. If the source chart includes subaccount segments, those are recreated as separate subaccount dimensions in Acumatica's segment structure. Historical balances are loaded into GL History to ensure year-end reporting continuity and trial balances reflect the same opening balances as the prior system.

Open Proteus ERP sales orders migrate to Acumatica Sales Orders with all line items, quantities, unit prices, and warehouse assignments preserved. Order status (Quote, Pending, Confirmed, Completed) maps to Acumatica's order status pick-list. Completed orders are migrated as closed records with original order dates maintained.

Open Proteus ERP purchase orders migrate to Acumatica Purchase Orders. Line items with vendor part numbers, ordered quantities, and receipt status map directly. Partially received POs are flagged with receipt percentages so your purchasing team can continue receiving against the existing order number in Acumatica.

Open Proteus ERP AR invoices and credit memos migrate to Acumatica AR Invoices. Document number, customer reference, invoice date, due date, line items, and outstanding amounts all map. Historical paid invoices are loaded as read-only records for financial reporting continuity. Credit memos preserve the original reference to the linked invoice.

Open Proteus ERP AP invoices and vendor credits migrate to Acumatica AP Bills. Vendor reference, invoice date, due date, line items, and amounts map directly. Historical paid bills are migrated as read-only records. Prepayments and retainages recorded in Proteus ERP are mapped to Acumatica's prepayment and retainage application screens.

Proteus ERP customer receipts and vendor payments migrate to Acumatica Payments. Each payment is linked to its corresponding invoice or bill for automatic application. Unapplied cash balances are migrated as unapplied payments so your AP/AR teams can clear them in Acumatica.

Proteus ERP employee records are migrated to Acumatica's Employee screen, preserving contact details, department, employment status, pay group, and employee ID. Additional fields such as employee location, manager hierarchy, cost center, and HR-related custom attributes also transfer when they exist in the source data. Maintaining the original employee IDs ensures continuity for timesheet entry, project billing, and downstream payroll integrations in Acumatica.

Any custom properties stored on Proteus ERP customers, vendors, inventory items, or GL accounts must be pre-defined as UDFs in Acumatica's Customization Project. FlitStack generates a UDF definition manifest listing each custom property's name, data type, and target screen so your Acumatica admin can create them before the migration run.

Proteus ERP warehouse and location records are mapped to Acumatica Warehouses, preserving site ID, address, and active status. Each warehouse can have a default location, and any bin or location-level tracking from Proteus is recreated as Location IDs within the Acumatica warehouse after the necessary UDFs are defined, supporting accurate inventory allocation and picking workflows.