Migrate from Jeeves ERP to Acumatica

Jeeves Customer maps to Acumatica Business Account. Acumatica requires the customer class to be defined first (Configuration → Customer Management → Customer Classes) to serve as the template for payment terms, GL accounts, and credit limits. Default terms and credit limit from Jeeves migrate as Customer Class overrides on each account record. We create any missing customer classes in Acumatica before importing customer data.

Jeeves stores multiple addresses per customer (billing, shipping, plant). Acumatica uses the CR.Address DAC linked by AddressID to handle address records across all entities. Primary billing address lands on the main Customer screen; additional addresses attach via the Shipping Rules or Location sub-screen. Each address type in Jeeves maps to the corresponding Location record in Acumatica with address validation performed during import.

Jeeves Vendor maps to Acumatica Vendor. Vendor class, payment terms, and default GL accounts for AP subledger (liability account) migrate as Vendor Class overrides. We create missing vendor classes in Acumatica's Configuration → Purchasing → Vendor Classes before import. Remit-to addresses use the same CR.Address DAC pattern as customer addresses, allowing consistent address management across the vendor master.

Jeeves items marked as stocked map to Acumatica Stock Item with Inventory ID, Description, Item Class, and posting class. Non-stocked items (services, expenses) map to Non-Stock Item. Jeeves' unit-of-measure groups map to Acumatica's UOM definitions before items can be imported.

Jeeves BOMs with multi-level component structures migrate to Acumatica Manufacturing BOMs using the Bill of Materials screen (AM201000). Each BOM revision becomes a separate Acumatica BOM revision with effective and expiration dates, preserving full revision history. Phantom BOMs in Jeeves map to Acumatica's phantom BOM flag, maintaining the same exploded kit behavior at the production level.

Jeeves work centres and machine groups map to Acumatica Work Centres under Manufacturing → Work Centres (AM200100). Machine hour rates and labor rates from Jeeves carry forward as the cost basis for production order variance reporting in Acumatica. We validate that each work centre in Jeeves has a corresponding work centre in Acumatica before importing production orders that reference those resources.

Open Jeeves sales orders migrate as Acumatica Sales Orders with the same order number preserved in the external reference field. Status mapping: Jeeves Draft/Confirmed/Backordered map to Acumatica On Hold / Pending / Confirmed. Lines with Kit items resolve to the kit's exploded BOM in Acumatica.

Open Jeeves purchase orders migrate to Acumatica PO with vendor, line items, quantities, and promised dates preserved. Receipts linked to Jeeves POs require separate receiving records in Acumatica — we map Jeeves receipt status to determine whether an Acumatica receipt is required at go-live.

Jeeves invoices and credit memos migrate to Acumatica AR invoices with original invoice number stored in the External Ref field for audit traceability. Jeeves payment records attached to invoices map as Acumatica payments applied to the same AR document via the Payments and Applications screen.

Jeeves projects migrate to Acumatica Projects (PM301000) with PM.EnterTimeSpent and PM.EnterActualRevenue toggled per project type to control time and revenue entry. Each Jeeves project sub-task or case maps to an Acumatica Project Task with the same name, budget, and billing rule from Jeeves carried forward. We preserve the project template structure in Acumatica's Project Templates screen to maintain consistency across similar project types.

Jeeves GL accounts migrate to Acumatica with the same account code, description, and account type (Asset, Liability, Equity, Revenue, Expense). Subaccount segments from Jeeves map to Acumatica's subaccount dimension — we validate segment count against Acumatica's active segment configuration before import.

Every Jeeves UDF per entity requires an Acumatica Customization Project entry: a DB column (UsrFieldName), a DAC field declaration with PXString/PXInt/PXDecimal attributes, and a screen control in the appropriate form. We deliver the full customization project XML package as part of the migration package.

Jeeves process automations (triggers, state-change rules, notification templates) have no Acumatica equivalent at the data level. We export the automation definitions as structured reference documentation and deliver them alongside the migration so your Acumatica admin can rebuild each rule using Acumatica's Automation Schedules and Business Events.

Jeeves file attachments and document links on customers, orders, and projects are re-uploaded to Acumatica's Note and Files system attached to the corresponding record. We preserve the original file name and attach date for audit continuity. The file library structure in Acumatica's SM202520 screen maintains the same folder hierarchy as Jeeves where applicable, ensuring users can locate documents in familiar locations post-migration.