Migrate from Kinetic to Acumatica

Kinetic Customer table maps 1:1 to Acumatica Customers (AR submodule). Kinetic customer IDs and names import as CustomerCD and Name respectively. Multi-address support maps using Acumatica's address tab; secondary contacts become Contacts attached to the Customer record. All original customer credit terms are preserved in the TermsID field.

Kinetic Vendor records map to Acumatica Vendors (AP submodule). Vendor IDs, names, and payment terms carry over. Remit-to addresses import as separate address records. 1099 vendor flags translate to the Acumatica tax ID field. Vendor class assignments are transferred using value mapping to ensure correct categorization in Acumatica.

Kinetic Part master maps to Acumatica Inventory IDs. Part classes become Stock Groups. Kinematics Unit of Measure (UOM) conversions are preserved in Acumatica's UOM classes. Discontinued parts are set to Inactive on the inventory record. We also map part-specific costing methods to Acumatica's standard or average cost layers to maintain accurate valuation.

Kinetic multi-level BOMs map to Acumatica BOMs with the same structure — parent part, component parts, quantity per, and operation sequence. Alternate BOMs import as separate BOM revisions flagged by Effective Date ranges. For parts with multiple plant-specific BOMs, we generate separate BOM revisions linked to the appropriate Acumatica branch using the revision's effective date window.

Open Kinetic job records map to Acumatica Production Orders in Scheduled or On Hold status based on Kinetic job status. Closed jobs are not migrated; their totals are rolled into the inventory valuation snapshot that transfers at go-live. The mapping preserves original job numbers as the ProductionOrderID so audit trails remain intact.

Open Kinetic POs map to Acumatica POs with line items, quantities, and vendor part numbers. Released vs. pending status is preserved. PO amendments in Kinetic become change order lines in Acumatica. We also map PO carriers and shipping terms to Acumatica's corresponding drop-down lists to maintain fulfillment instructions.

Open Kinetic SOs map to Acumatica Sales Orders. Ship-to addresses, order hold codes, and request dates carry over. Acumatica's multi-warehouse fulfillment can resolve Kinetic's single-warehouse ship-from constraint. We also transfer order-level notes and internal comments to the Acumatica Sales Order detail tab for complete reference.

Open Kinetic AR invoices and credit memos map to Acumatica AR Transactions. Original invoice dates, due dates, and terms are preserved. Unapplied payments become Acumatica Cash Entries matched against the customer account. We also map invoice-level discounts and tax amounts to the corresponding Acumatica distribution lines to preserve financial accuracy.

Open Kinetic AP invoices map to Acumatica AP Bills. Vendor invoice numbers are preserved as Reference Nbr for audit trails. Prepaid AP entries from Kinetic carry over as opening balances on the AP register. We also map payment terms and due date calculations to Acumatica's TermsID to maintain consistent cash flow tracking.

Active period GL journal entries from Kinetic import as Acumatica GL Transactions using the same account code structure. Year-end closing entries are excluded unless the Acumatica chart of accounts needs opening balances carry-forward. We also map subaccount segments to Acumatica's dimension fields to preserve cost center and department detail across the ledger.

Kinetic lot and serial number registries map to Acumatica's lot/serial tracking at the site level. Original receipt dates and expiration dates carry over for FIFO/lot-specific valuation. We also map lot attributes such as supplier lot codes and custom attributes to Acumatica's extended lot fields for full traceability.

Kinetic project records map to Acumatica Projects with project status, billing options, and non-inventory line items. Time and material tracking maps to Acumatica's Project Transactions submodule. We also map project-specific cost codes to Acumatica's allocation rules to ensure accurate project profitability reporting.

Kinetic BAQ (Business Activity Query) custom fields and calculated columns do not have a direct Acumatica equivalent. We export BAQ column definitions as a CSV reference document; your Acumatica consultant rebuilds these as custom fields on the relevant DACs or as Acumatica Generic Inquiries.

Kinetic Epicor Data IO integration packages (used for EDI or third-party data feeds) have no Acumatica equivalent. We provide a mapping document for each package's schema; your Acumatica developer rebuilds the integrations using Acumatica's REST API or import scenarios. The mapping document includes field-level transformations, error handling logic, and suggested Acumatica screen placements for each integration endpoint.