Migrate from ERP Mark 7 to Acumatica

ERP Mark 7 customer records map 1:1 to Acumatica Customer entities. Each record carries customer name, class, status, payment terms, credit limit, and primary contact info. Acumatica's CustomerClassId field determines the default payment terms and GL accounts — FlitStack maps ERP Mark 7's customer class codes to Acumatica Customer Class records created before the migration runs.

ERP Mark 7 vendor master records map to Acumatica Vendor entities with direct field correspondence for vendor name, address, payment terms, and tax ID. ERP Mark 7's vendor status (active/inactive) maps to Acumatica's Vendor Status field. Remit-to addresses stored as separate ERP Mark 7 records import as VendorLocation records in Acumatica.

ERP Mark 7 stock items map to Acumatica StockItem records. The inventory valuation method (standard, average, FIFO) stored in ERP Mark 7 transfers as the ValuationMethod field on the StockItem. Primary warehouse assignment from ERP Mark 7 maps to the DefaultWarehouse field. Unit of measure conversions between ERP Mark 7's UOM definitions and Acumatica's UOM classes require a UOM class pre-created in Acumatica before item migration.

ERP Mark 7 non-stock items (services, freight, special charges) map to Acumatica Non-Stock Items. These records do not carry inventory quantities but do carry default account assignments for revenue and cost. FlitStack maps ERP Mark 7's revenue account and cost account from each non-stock item to Acumatica's SalesAccount and COGSAccount on the Non-Stock Item.

ERP Mark 7 BOMs with single or multi-level structures require decomposition into Acumatica's BOMRevision (which holds the revision number, effective date, and status) and BOMLine records (which link each component StockItem, quantity per, and scrap percentage). Multi-level ERP Mark 7 BOMs with sub-assemblies require recursive BOM creation in Acumatica — the top-level finished good becomes one BOM Revision whose lines reference sub-assembly BOMs.

ERP Mark 7 open sales orders map to Acumatica Sales Orders with separate SOLine records per line. Partially fulfilled lines from ERP Mark 7 (where shipped quantity is less than ordered quantity) require the open quantity to be computed and set as the OrderQty on the Acumatica SOLine with a ShippedQty of zero — the remainder ships after go-live using Acumatica's shipment confirmation flow. Order dates, promised dates, and customer PO numbers map directly.

ERP Mark 7 open purchase orders map to Acumatica Purchase Orders with POLine records per line. Receipts already completed in ERP Mark 7 do not re-import — the received quantity on each line is set to match ERP Mark 7's receipt total, leaving only the open quantity to be received through Acumatica's AP bill entry after go-live. Vendor and terms data cross-references the vendor mapping completed earlier in the migration.

ERP Mark 7 GL account codes and descriptions map to Acumatica Chart of Accounts records. Account type (asset, liability, equity, revenue, expense) from ERP Mark 7 determines the AccountType field in Acumatica. Subaccount segments in ERP Mark 7 map to Acumatica's subaccount dimension structure — your Acumatica implementation team configures the subaccount mask before the migration validates.

ERP Mark 7 open AP invoices import as Acumatica AP Bills. Invoice number, vendor reference, invoice date, due date, and total amount map directly. Line-level detail for items, miscellaneous charges, and taxes requires the POLine cross-reference from the purchase order mapping. ERP Mark 7 payment terms drive the DueDate calculation on each APInvoice record.

ERP Mark 7 open AR invoices import as Acumatica AR Invoices. Customer reference, invoice number, invoice date, due date, and amount map directly. Cash applications already recorded in ERP Mark 7 (payments matched to invoices) do not re-import — the invoice lands with a zero open balance in Acumatica and the applied payment history is preserved as a reference note.

ERP Mark 7 open manufacturing work orders map to Acumatica Production Orders. The BOM reference from ERP Mark 7's work order resolves to an Acumatica BOMRevision during import. Material issues already completed in ERP Mark 7 are not replicated — the production order lands with the remaining material demand and labor hours to be recorded through Acumatica's production entry screens post-go-live. Order status (released, in process, completed) maps directly.

ERP Mark 7 user-defined fields on customers, vendors, and items have no native equivalent in Acumatica's standard schema. Each custom field requires an Acumatica customization project with a matching data type (string, number, date, picklist). FlitStack delivers a custom field creation plan specifying the field name, data type, and which DAC it extends before migration data lands, so Acumatica's validation rules fire correctly.

ERP Mark 7 maintains separate cost layers per lot or per receipt for average-cost and FIFO items. These import as INItemCostDetail records in Acumatica, one per layer with quantity, unit cost, and receipt date. Standard-cost items import the current standard cost as a single cost record. Lot-controlled items link cost layers to the specific lot number in Acumatica's INLotSerial class.

ERP Mark 7 approval chains and conditional workflow rules (e.g., PO approval thresholds, order-hold logic) are internal business process automation. They do not transfer to Acumatica — Acumatica's approval workflow engine (based on Business Events and automation screens) requires separate configuration. FlitStack exports ERP Mark 7 workflow definitions as a structured reference document your Acumatica admin uses to rebuild the logic.