Migrate from VAIL-ERP to Acumatica

VAIL-ERP vendor records map to Acumatica Vendors screen. Acumatica requires a VendorClass assignment — FlitStack creates a default class or maps VAIL-ERP's vendor grouping if one exists. Primary contact, payment terms, and tax ID map as-is. Unmatched payment terms default to Acumatica's Net-30 class.

VAIL-ERP customer records migrate to Acumatica Customers. Each customer requires a CustomerClass — FlitStack maps VAIL-ERP's customer segmentation to Acumatica's class structure. Credit limit and terms are preserved; if VAIL-ERP stores a credit limit on the customer record, it maps to Acumatica's CreditLimit field.

VAIL-ERP GL accounts map to Acumatica Chart of Accounts entries. Acumatica separates account code from the branch/subaccount dimension using the Subaccount field — FlitStack extracts VAIL-ERP's branch-level account coding and reassembles it as separate account and subaccount records so each branch gets the correct posting dimension in Acumatica.

VAIL-ERP journal lines map to Acumatica GL Journal Transactions with debits and credits preserved in the original amounts and accounts. Acumatica's multi-currency flag is set per batch — if VAIL-ERP records carry currency codes, FlitStack sets the corresponding Acumatica currency and rate type so historical balances revalue correctly.

VAIL-ERP inventory items migrate to Acumatica Stock Items (if lot/serial tracked) or Non-Stock Items (for procurement-only items). Acumatica requires an Item Class — FlitStack maps VAIL-ERP's item category to an Acumatica item class or creates one. Post-processing requirements, landed cost defaults, and default warehouse assignment carry over as Acumatica settings.

VAIL-ERP purchase orders map to Acumatica Purchase Orders with vendor, line items, quantities, and unit costs preserved. Acumatica's Open status reflects VAIL-ERP's open/closed flag. Lines that were partially received in VAIL-ERP surface as partially received in Acumatica PO screen so the receiving team can continue without data loss.

VAIL-ERP sales orders migrate to Acumatica Sales Orders with customer, line items, quantities, and pricing intact. Tax calculations are not recalculated at migration — original order totals are preserved so financial reconciliation against VAIL-ERP history is accurate. Completed orders land as Closed in Acumatica; open orders remain Open.

VAIL-ERP branch or location records map to Acumatica Branches and, if VAIL-ERP supports multiple legal entities, to separate Acumatica Companies. Multi-company setups require pre-migration planning — FlitStack delivers a branch-to-company mapping plan before migration runs so the correct Acumatica entity receives each branch's transactions.

Acumatica does not include a native HR module in all editions. FlitStack maps VAIL-ERP employee records to Acumatica's HR Workers screen if HR Steps is licensed, or creates a custom Employee DAC with the source fields preserved as User-Defined Fields. Payroll data (salary, deductions) is mapped as custom fields if no native payroll module exists in the destination tenant.

Industry-specific VAIL-ERP modules (hospital management, trading, hospitality) store data in custom tables that have no direct Acumatica equivalent. FlitStack audits these tables, maps each custom field to an Acumatica User-Defined Field on the closest standard DAC, and exports the custom table structure as a reference for Acumatica customizations the customer may want to build post-migration.

VAIL-ERP file attachments associated with vendor records, customer records, or transactions are downloaded, re-uploaded to Acumatica Files, and linked back to the corresponding record. Acumatica's file size limit of 25MB per attachment applies — files exceeding this are flagged before migration for manual handling.

VAIL-ERP approval workflows, automated posting rules, and scheduled job configurations do not have an Acumatica equivalent that can carry over automatically. FlitStack exports the workflow definitions as a structured reference document and delivers it to the Acumatica configuration team so workflows can be rebuilt using Acumatica's Workflow Editor and Business Events framework.