Migrate from Farvision ERP to Acumatica

Farvision stores each legal entity as a separate Company record with its own COA and address. Acumatica models legal entities as separate Tenants or as Branches under one Tenant — we create a Branch record per Farvision Company and map the COA segments accordingly.

Farvision Customers map 1:1 to Acumatica Customers. Address, contact, credit limit, and payment terms transfer directly. Multiple Farvision contacts per Customer collapse to primary contact plus additional contact records in Acumatica. We preserve the customer classification and price class assignments from Farvision as Acumatica Customer Classes to maintain pricing integrity.

Farvision Supplier and Contractor masters both map to Acumatica Vendors. We preserve the Contractor flag as a custom Vendor Class so project-related payables route to the correct Cost Code in PM. Tax registration IDs and remittance addresses carry over to ensure accurate 1099 reporting and payment processing in Acumatica.

Farvision Property Units used in sales or lease billing merge into Acumatica Inventory Items (if sellable) or Non-Stock Items (if cost-only). Unit type, tower, floor, and facing information map to Custom Fields on the item record. The unit's lease status and rental rate schedule are preserved in custom fields for billing integration.

Farvision Projects map directly to Acumatica Projects. Each Farvision Project phase becomes a discrete Task within the Acumatica Project. Phase budgets map to Task budgets in PM301000; we preserve the original phase codes in Cost Codes. Project-level custom fields for developer, location, and permit numbers transfer to custom fields on the Acumatica Project header.

Farvision budget lines contain both a cost category and an amount. We split these into Acumatica Cost Codes (the category dimension) linked to the Project Task, with amounts stored in the Task Budget view. Each Farvision budget line generates a separate Cost Code assignment with the corresponding budgeted amount. Blended-rate budgets are flagged for manual rate table entry.

Farvision's 3-segment COA (Region.Entity.Type) maps to Acumatica's Branch plus Account plus Subaccount structure. We parse each Farvision segment and recompose it into the appropriate Acumatica segment; the Subaccount segment gets split if Farvision uses a compound Type code that encodes both cost center and function. All Farvision GL transactions repoint to the newly created Acumatica accounts.

Farvision sales orders map to Acumatica SO301000. Order type, customer, line items, and due dates transfer directly. Farvision's project-linked orders get the Project ID assigned on the SO line for billing integration. Warehouse and location assignments from Farvision lines populate the Acumatica shipment details, and any project-specific discount schedules are preserved as custom fields.

Farvision purchase orders map to Acumatica PO301000. Vendor, line items, and promised dates carry over. Lines linked to Farvision Projects carry the Project Task reference so receipts post to the correct cost bucket. The Acumatica PO retains the Farvision buyer assignment and approval status, with any held orders flagged for release in Acumatica's approval workflow.

Farvision material receipts map to Acumatica PO302000. Receipt date, vendor, warehouse, and item quantities transfer. Landed costs from Farvision receipt add-ons accrue in Acumatica's Landed Cost application (LM503010). The original Farvision receipt number is stored in a custom field for cross-reference during reconciliation.

Farvision AR invoices map to Acumatica AR301000; AP invoices map to AP301000. Payment terms, due dates, and project references on lines carry over. Prepayments from Farvision post as Advance PM applications in Acumatica. Any retained percentage terms from Farvision transfer as separate hold codes, and the original invoice reference number is preserved for audit trails.

Farvision receipts and disbursements map to Acumatica Payments. Payment method, reference number, and applied invoice references transfer. Cash discounts taken in Farvision are preserved in Acumatica's discount application logic. The payment batch ID from Farvision is stored as a custom reference to assist with reconciliation of historical payment runs.

Farvision inventory items with qty-on-hand map to Acumatica Stock Items. Item class, valuation method, primary warehouse, and last cost pull in as item attributes. Active or inactive status from Farvision sets the Inventory Status in Acumatica. Lead times and reorder points transfer as item planning parameters, and Farvision's lot or serial tracking settings map to Acumatica's lot/serial class assignments.

Farvision Site and Warehouse masters map to Acumatica Warehouses. Address, Is Active flag, and default location class transfer. Farvision's site-specific bin structures are preserved as location names within each Acumatica warehouse. The site contact and phone number from Farvision become the warehouse contact details, and any site-specific expense accounts are mapped to the corresponding Acumatica warehouse cost center.

Farvision Employee records split into Acumatica's employee payroll record (EP203000) and the HR Worker record (HQ101000) if both modules are in use. Salary, department, and employment status map to EP for payroll processing, while benefits, certifications, and emergency contacts map to the HR Worker record. The original Farvision employee ID is preserved in the Employee ID field for system cross-referencing.

Farvision lease agreements have no direct Acumatica equivalent in base ERP — they require the Contracts module or a custom lease management application. We preserve Farvision lease data in a custom Lease record with fields for start/end date, tenant, unit, and rent schedule.

Farvision attachments on Projects, Purchase Orders, and Invoices re-upload to Acumatica Files. File name, MIME type, and parent record reference are preserved. Large files exceeding 25MB are split into multiple parts per Acumatica's file size limit, and a custom metadata field records the total part count and sequence so files can be reassembled after migration or uploaded manually via the Acumatica UI.

Farvision approval chains for PO, Invoice, and Expense workflows have no direct Acumatica equivalent. We export the workflow graph as a JSON file containing each step, approver, threshold amount, and conditional routing logic. This JSON maps to Acumatica's Approval Maps (EP405020) for manual reconstruction by your Acumatica administrator. The export includes a step-by-step guide referencing Acumatica screen IDs and field names for building the corresponding approval sequences.