Migrate from Falcon ERP to Acumatica

Falcon account codes map to Acumatica AccountCD. Account description maps to AccountDesc. Falcon's Account Type (Asset, Liability, Expense, Income) sets the Account Class in Acumatica's segmented GL structure. Sub-accounts from Falcon map to Acumatica's Subaccount segment — each segment appears as a separate column in Acumatica's GL entry screen.

Falcon customer records become Acumatica Customer records. Falcon's single address and contact block maps to Acumatica's default Customer Location. Falcon Customer Type codes require mapping to Acumatica Customer Class records, which define payment terms, credit limit, and tax zone. Additional Falcon address records become additional Acumatica Customer Location entries per customer.

Falcon vendor records map to Acumatica Vendor. The primary address and contact from Falcon become Acumatica's default Vendor Location. Falcon's Vendor Type or Category codes require pre-creation of Acumatica Vendor Class records, which govern payment terms, remittance advice settings, and 1099 / tax form assignments. Multi-location vendors from Falcon require additional Vendor Location records in Acumatica.

Falcon item codes map to Acumatica InventoryID. Falcon's Item Description maps to Acumatica's Description. Falcon Stock Category codes require pre-created Acumatica Item Class records that define the cost method (Average, Standard, FIFO), UOM set, and posting settings. Falcon's stock quantity per item maps to Acumatica's on-hand quantity by Warehouse, created via an initial inventory receipt if no formal opening balance exists.

Falcon Sales Order headers map to Acumatica Sales Order records with OrderNbr, OrderDate, and CustomerRef. Falcon OrderNbr becomes CustomerOrderNbr in Acumatica. Each Falcon order line becomes an Acumatica Sales Order Detail line with the InventoryID reference, OrderQty, and UnitPrice. Falcon order total maps to Acumatica's order amount fields.

Falcon Purchase Order headers map to Acumatica Purchase Order records with OrderNbr, VendorRef, and OrderDate. Falcon line items map to Acumatica Purchase Order Details with the InventoryID, VendorID, and Extended Cost. Falcon purchase order totals map to Acumatica's line amount totals. If Falcon PO status was Open, Acumatica's Open status is set accordingly.

Falcon AP invoice headers map to Acumatica AP Invoice records with VendorRef, InvoiceNbr, InvoiceDate, and DueDate. Falcon line amounts map to Acumatica's Extended Price field per line. Falcon's VAT amount or tax amount is mapped to Acumatica's separate Tax Amount field. Falcon invoice totals map to Acumatica's document total. Falcon's vendor reference number becomes Acumatica's VendorRefNbr.

Falcon AR invoice headers map to Acumatica AR Invoice records with CustomerRef, InvoiceNbr, InvoiceDate, and DueDate. Falcon line items map to Acumatica Details with InventoryID, Quantity, and Unit Price. Falcon tax amount maps to Acumatica's Tax Amount field on the invoice. Falcon invoice reference numbers become Acumatica's CustomerRefNbr.

Falcon inventory adjustment records map to Acumatica Inventory Adjustment documents with the InventoryID, adjusted Warehouse, and the Delta Qty (positive for additions, negative for reductions). Falcon's adjustment reason code maps to Acumatica's Reason Code field, which must be pre-created in Acumatica's Reason Code list. Adjustment dates from Falcon are preserved in Acumatica's TranDate.

Falcon fixed asset records map to Acumatica Fixed Asset records with AssetCD, Description, AssetClass, and AcquisitionDate. Falcon's current book value maps to Acumatica's Depreciation Method and Accumulated Depreciation fields. Falcon's asset location maps to Acumatica's Building / Location fields. Falcon's acquisition cost maps to Acumatica's Cost basis field.

Falcon employee records map to Acumatica Employee records with EmployeeID, FirstName, LastName, and Department. Falcon's employment status maps to Acumatica's Employee Status (Active, Inactive). Pay Rate or salary fields from Falcon are mapped to Acumatica's Salary and Compensation Rate fields. Falcon branch or cost-center assignment maps to Acumatica's Department and Branch fields.

Falcon stores user-defined fields as custom properties on standard records (e.g., a custom field on the Customer record). Acumatica has no direct equivalent — custom fields must be created as DAC extension fields with a Usr prefix in the Acumatica Customization Project Editor. Each custom property requires a separate DAC extension field with a matching data type. We deliver a field specification document listing each Falcon custom field, its type, and the recommended Acumatica field definition for your admin to create before the import run.