Migrate from inoERP to Acumatica

inoERP customers map directly to Acumatica Business Account (Customer class). Each inoERP customer site becomes an Acumatica Customer Location on the same Customer record. Primary email and billing address migrate as the default location; additional sites map to sub-locations with their own shipping addresses and GL delivery terms.

inoERP vendors map to Acumatica Vendors. inoERP vendor sites map to Acumatica Vendor Locations. Payment terms, tax ID, and remittance address carry forward as Vendor attributes. Acumatica's Vendor class supports both AP-only vendors and customers that are also vendors — flagged from inoERP's supplier_type field.

inoERP items classified as Stock map to Acumatica Stock Items with inventory tracking enabled. Non-stock items (services, materials without stock control) map to Non-Stock Items. The item's cost_method (standard, average, FIFO) maps to Acumatica's Cost Method field on the Inventory Item General tab. Default warehouse and last purchase price migrate as item defaults.

inoERP BOMs map to Acumatica Bill of Materials records. Each inoERP BOM revision maps to an Acumatica BOM revision with an effective date. Component line quantities, scrap percentages, and material issue/overhead costs carry forward. Acumatica distinguishes between BOMs for manufacturing and formulas for batch processing — routed by inoERP's bom_type field.

Open and historical inoERP work orders migrate as Acumatica Production Orders with their current status preserved (On Hold, In Process, or Completed). The linked BOM revision and production steps become the production order's operation list. Actual material consumption and labor bookings from inoERP are recorded as completed production transactions in Acumatica.

inoERP chart of accounts entries map directly to Acumatica GL Accounts with the same account code, description, type (Asset, Liability, Expense, Income), and active/inactive status. inoERP's account segments map to Acumatica's segmented key structure — each inoERP segment becomes an Account Segment in Acumatica's COA configuration.

Historical inoERP GL journal lines migrate as Acumatica Journal Transactions. Original document dates become the transaction date; the source module is stored in a custom reference field. Opening balances for active accounts are loaded as a single opening-balance journal entry rather than individual historical rows to avoid inflating record counts.

Open inoERP sales orders migrate as Acumatica Sales Orders with their line items, quantities, and pricing. Order status (Draft, Open, Completed, Cancelled) maps to Acumatica's status codes. Historical orders with no remaining fulfillment obligation are summarized as completed records in Acumatica without creating active order rows.

Open inoERP purchase orders migrate as Acumatica Purchase Orders. Vendor location, line items, quantities, and unit costs carry forward. inoERP PO approval status is recorded as a custom field in Acumatica because Acumatica handles approval workflows through its internal approval map, not as a data attribute — your Acumatica admin configures the approval map to match inoERP's workflow thresholds.

inoERP employees map to Acumatica Employees with name, position, department, employment status, and hire date. Compensation and payroll data migrates to Acumatica Payroll (if the payroll module is active); otherwise it is exported as a reference file for manual configuration. Leave balances and approval hierarchies become Employee UDFs or are set up manually in Acumatica's HR module.

Open inoERP AR documents (invoices, credit memos, prepayments) migrate as Acumatica AR Documents. The customer location and terms code map from inoERP's payment_term field. Historical paid documents are summarized — full document history is preserved in a reference export file; only open aging items create live Acumatica AR records to avoid inflating document counts.

Open inoERP AP documents migrate as Acumatica AP Documents with vendor, invoice number, date, amount, and terms. Prepayments and credit memos carry their balance-forward amounts. Historical paid AP items are summarized into a reference archive export; open aging items create live Acumatica AP records.

inoERP asset records (fixed assets with depreciation schedules) map to Acumatica Fixed Assets. Asset class, acquisition date, cost, residual value, and depreciation method carry forward. inoERP accumulated depreciation entries migrate as opening balance entries in Acumatica's asset depreciation history. Asset disposal history and revaluation records are preserved as reference notes on the fixed asset record in Acumatica.

inoERP project records migrate as Acumatica Projects with customer association, project status, manager, and budget limits. Line-item budgets map to Acumatica project task budgets. Time and material allocations from inoERP become project transactions in Acumatica's Project Accounting module. Project phases, cost categories, and billing rules are transferred as configuration settings within each project.