Migrate from Pilot ERP to Acumatica

Pilot ERP customer records map directly to Acumatica Customer. Address, contact info, and payment terms transfer as-is. If the Pilot ERP customer has multiple ship-to addresses, Acumatica's Contact and Address subentities handle this natively — no custom junction table required. Customer-specific attributes like credit limits and tax registration IDs populate the corresponding Acumatica fields. Multiple contact roles per customer are preserved using Acumatica's contact class and purpose flags.

Vendor records from Pilot ERP map to Acumatica Vendor with terms, address, and remit-to info preserved. Multi-address vendors use Acumatica's address book structure with primary and remittance locations tracked separately. Vendor-specific lead times and drop-ship flags become Acumatica custom fields or note text entries. Vendor class assignments determine default accounts for AP aging and payment processing. Tax registration IDs map to the vendor tax info section for jurisdiction-based invoicing.

Pilot ERP inventory items carry warehouse, location, and lot data. In Acumatica these become Stock Items scoped to one or more Warehouses. Items marked as non-inventory in Pilot ERP map to Non-Stock Items used only on purchase documents. Lot/serial attributes preserve via Acumatica's lot/serial classes.

Pilot ERP BOMs with multi-level structures map to Acumatica BOMs by material line and overhead. Each BOM revision in Pilot ERP becomes a separate BOM version in Acumatica, versioned by effective date. Phantom BOMs translate to Acumatica's phantom BOM designation.

Pilot ERP work orders map to Acumatica Manufacturing Orders. The work-order header (part number, quantity, priority) becomes the MO header; the operation sequence maps to Acumatica's production物料 (material) and production operations. If the customer uses project costing, work orders map to Project Tasks with labor and material allocations.

Pilot ERP phases within a work order translate to Acumatica Project Tasks under the corresponding Project record. Each phase's labor and material costs map to Project Task cost codes for granular expense tracking. Phase budget amounts become Project budget lines in Acumatica's budget tracker with variance tracking enabled. If phases contain sub-phases in Pilot ERP, each nested level creates a corresponding sub-task hierarchy in Acumatica Projects. Original phase start and end dates transfer as task planning dates for production scheduling continuity.

Open Pilot ERP sales orders migrate to Acumatica Sales Orders with line items, quantities, promised dates, and warehouse allocations preserved. Order statuses map by Acumatica's hold, open, and completed states. Completed orders are migrated as historical records with no open balance.

Pilot ERP POs map to Acumatica Purchase Orders. Vendor, line items, quantities, and expected delivery dates transfer directly. Open POs retain their pending status; received or invoiced amounts reflect in Acumatica's receipt and AP modules. Partially received POs carry forward receipt balances and expected quantities. Vendor confirmations and rush flags map to Acumatica PO text notes for buyer visibility.

Pilot ERP invoices and credit memos map to Acumatica AR invoices with original posting dates preserved in the reference fields. Open invoices carry outstanding balances; paid invoices become historical. Tax jurisdiction settings are applied based on Acumatica's tax zone configuration.

Pilot ERP AP records map to Acumatica Bills. Vendor, amount, due date, and GL account allocations transfer. Open AP items carry payables balances; historical paid records are migrated for audit continuity. Prepayments and credit memos link to the corresponding vendor in Acumatica.

Pilot ERP GL accounts map directly to Acumatica's chart of accounts by account code. Account type (Asset, Liability, Expense, Income) and Active/Inactive status transfer. Subaccount segments in Pilot ERP become Acumatica subaccounts keyed to the chart. Account descriptions, cash-flow classifications, and rounding limits also migrate to ensure consistent financial reporting. Historical account balances carry forward as opening balances in Acumatica's first active financial period.

Pilot ERP custom properties on customers, vendors, items, work orders, or any other entity become Acumatica user-defined fields. FlitStack AI creates the UDF definition on the correct screen/DAC and populates the field values during migration. Drop-down style custom properties become Acumatica combo or list fields with the same value set.