Migrate from Finesse ERP to Acumatica

Finesse customer records map 1:1 to Acumatica Customers. Primary address, contact information, payment terms, and credit limit transfer as-is. Multiple ship-to addresses become Acumatica shipping addresses linked by CustomerID. We preserve the original Finesse customer number as an external reference field for traceability.

Finesse vendor records map to Acumatica Vendors with the same address, contact, and payment-term fields. Remit-to addresses and 1099 settings transfer as UDFs or native fields depending on configuration. Finesse vendor codes become Acumatica vendor IDs after de-duplication against existing records.

Finesse item records with part type 'stock' become Acumatica Stock Items. Items without on-hand tracking (services, materials used in project work) become Non-Stock Items. Unit of measure, default warehouse, and valuation method map from Finesse's cost-layer settings to Acumatica's item class. We flag items with no Acumatica warehouse match for branch assignment during migration.

Finesse BOMs transfer to Acumatica Manufacturing BOMs with component lines, quantities per, and revision levels. Routing operations from Finesse work orders map to Acumatica manufacturing BOM operation sequences. We validate BOM explosion against inventory item IDs to ensure component items exist in Acumatica before committing the BOM records.

Finesse work orders split based on project linkage: standalone manufacturing WOs become Acumatica Production Orders; project-linked WOs where costs must track to a specific project become Project Tasks under the appropriate Project in Project Accounting. We require your Acumatica Project structure before migration so WOs route to the correct Cost Code.

Open and historic sales orders migrate with line items, quantities, and pricing. Order statuses map: Finesse 'Open' maps to Acumatica 'Open', 'Completed' maps to 'Completed', and 'Invoiced' maps to 'Closed'. We preserve the original Finesse order number as an external reference on each SO line for reconciliation.

Finesse POs map to Acumatica POs with vendor, line items, quantities, and expected dates. Open POs migrate with their receipt and invoicing status. Closed and fully-received POs migrate as history records. PO line-level GL account allocations transfer as distribution lines on the Acumatica PO.

Finesse labor entries and project cost postings become Acumatica Project Transactions. Each cost type (labor, material, equipment) maps to a distinct Expense Inventory ID or Direct Cost. Employee information resolves by email match to Acumatica employees. We validate that the Project and Cost Code exist in Acumatica before committing each transaction.

Finesse GL accounts transfer to Acumatica Chart of Accounts with account number, description, type, and active/inactive status. Account segments map to Acumatica's account segment definitions — your Acumatica admin pre-configures segment rules before the GL migration runs. Sub-accounts become separate accounts or segment values per your target chart structure.

Finesse inventory adjustment records, receipts, and issues migrate as Acumatica Inventory Transactions with warehouse, item, quantity, and cost. Adjustment reasons map to Acumatica's Reason Code field. We preserve the original transaction date for historical reporting continuity in Acumatica's inventory valuation reports.

Finesse custom fields on any entity become Acumatica UDFs on the equivalent screen (Customer, Vendor, Stock Item, Sales Order, etc.). UDFs with pick-list values transfer as drop-down fields; free-text UDFs become text fields. Your Acumatica admin activates UDF visibility on relevant screen forms after migration.

Finesse workflow rules, approval routing, and notification triggers do not migrate — they are destination-side configuration. We export your Finesse workflow definitions as a reference document so your Acumatica admin can rebuild approval sequences using Acumatica's Workflow Automation and Generic Inquiries.