Migrate from Impact ERP to Acumatica

Impact ERP customers map to Acumatica Business Accounts with the Customer checkbox enabled. Primary contact information moves to the default Contact sub-record. Multiple Impact ERP contacts for one customer split into separate Acumatica Contacts linked to the same AccountCD. Address records migrate with AddressID assigned sequentially per account.

Vendors migrate 1:1 to Acumatica Vendors. Tax ID and W-9 information from Impact ERP maps to the Tax ID field on the Vendor record. Remit-to addresses in Impact ERP become the Vendor's RemitAddress in Acumatica. Payment terms translate via value mapping against Acumatica's terms list (Net 30, Net 60, etc.).

Impact ERP's flat account codes become Acumatica Account records. Any cost-center or department segmentation stored in Impact ERP custom fields maps to Acumatica Subaccounts — a compound key model. Branch assignments in Impact ERP become Subaccount segments keyed to the destination Company/Branch in Acumatica. Account groups in Acumatica (Sales, Purchases, Expenses, Assets, Liabilities, Equity) are assigned based on Impact ERP account type flags.

Stock items in Impact ERP migrate as Acumatica Stock Items with ItemStatus set to Active. The item's default warehouse in Impact ERP becomes the DefaultWarehouseID on the Stock Item. Unit of measure (each, case, pallet) maps via UOM conversion rules between the two systems. Post-processing, lot, and serial number settings on the Impact ERP item carry forward to Acumatica's Inventory tab.

Non-stock items — service items, materials not tracked as inventory — migrate as Acumatica Non-Stock Items. These land in the same item master with the Non-Stock Flag set, meaning they do not consume warehouse capacity. Unit of measure and description fields transfer directly. If the non-stock item is used on purchase orders, Acumatica requires a default vendor link which we populate from the Impact ERP preferred vendor reference.

Open sales orders in Impact ERP migrate as Acumatica Sales Orders with OrderNbr, CustomerOrderNbr (containing the Impact ERP order number), and all line items including quantities, unit prices, and scheduled shipment dates preserved. The Order Type defaults based on the branch/warehouse assigned in Impact ERP. Lines referencing inventory items link to Stock Items; service lines link to Non-Stock Items. Owner/User from Impact ERP maps to the Assigned To field in Acumatica.

Open purchase orders migrate as Acumatica Purchase Orders. Vendor and Remit-to address information comes from the Vendor record already migrated. Line items with stock items create the expected landed-cost and receipt linkages in Acumatica's PO module. The Impact ERP order date and required-by date map to the OrderDate and PromiseDate fields respectively. If Impact ERP PO references an approved workflow status, we preserve that as a custom field until Acumatica's approval map is rebuilt.

Open and recently closed AR invoices (within the retention window — typically 24 months) migrate as Acumatica AR Documents with DocType = Invoice or CreditMemo. Impact ERP invoice numbers populate the RefNbr field. Line items reference migrated Stock or Non-Stock Items. Tax amounts recalculate based on Acumatica's tax zone configuration per branch; original tax codes are preserved as a custom field for tax reconciliation. Payment balances carry over so partially paid invoices show the correct amount due.

AP invoices and credit memos migrate as Acumatica AP Documents. Vendor references link to the migrated Vendor record. Prepayments recorded in Impact ERP migrate as Prepayment documents in Acumatica, preserving the original payment amount and application against open AP items. Tax zone assignments recalculate based on Acumatica's tax configuration per vendor location.

Impact ERP journal entries migrate to Acumatica GL Transactions with BatchID grouping preserved. Each line debit/credit amount transfers to the Amount field with the corresponding Account and Subaccount resolved from the mapping table. Impact ERP's batch reference number becomes the BatchNbr in Acumatica. Recurring journal entries from Impact ERP are exported as a configuration reference for Acumatica's Recurring Schedules.

Contact records in Impact ERP — including name, email, phone, job title, and department — migrate to Acumatica Contacts linked to the corresponding Business Account. The ContactClass assignment in Acumatica is set based on whether the contact is billing, shipping, or general in nature in Impact ERP. Multiple contacts per account preserve their display order as specified in Impact ERP.

Extended attributes on Impact ERP entities — such as credit class on customers, HS codes on inventory items, or custom cost-center values on GL accounts — require custom fields in Acumatica. We create UDF-style custom fields on the matching Acumatica entity using Acumatica's Customization Project framework, preserving the data type and pick-list values from the source field. These fields are available for reporting in Acumatica's Generic Inquiries and Report Designer.

Locations and warehouses defined in Impact ERP map to Acumatica Warehouse records with WarehouseID and Description. Each warehouse's address information transfers as the Receiving Address in Acumatica. If Impact ERP uses bin or bin-location tracking, those migrate as Acumatica Location records within the assigned Warehouse, enabling warehouse-specific picking and receiving workflows in Acumatica's IN module.

Manufacturing BOMs and recipes in Impact ERP migrate as Acumatica BOMs. Component items link to the migrated Stock Item records. The bill type (M, A, S for make-to-stock, assembly, or phantom) maps to Acumatica's BOMType field. Step information in multi-level bills transfers as operation sequences within the Acumatica Manufacturing module. Material and overhead costs recalculate against current standard costs in Acumatica but the historical component quantities are preserved.

Active projects in Impact ERP migrate as Acumatica Projects with ProjectID, Description, and status copied. Budget lines and task structures transfer as Project Tasks with TaskID and budget amounts. Time and expense entries linked to Impact ERP projects migrate as Project Transactions — Labor, Expense, and Material entries — linked to the migrated Project. Completed projects archive with ProjectStatus = Completed and retain all transaction history for reporting.