Migrate from ABRA Gen to Acumatica

ABRA Gen customer records map to Acumatica CR.Customer. Primary address, contact information, and tax ID migrate as fields on the customer. ABRA Gen customer types or categories map to Acumatica Customer Class codes — your admin selects or creates matching class records in Acumatica before migration runs.

ABRA Gen vendor records map to Acumatica AP.Vendor. Remit-to address, payment terms, and tax ID move as fields. Vendor classes from ABRA Gen map to Acumatica Vendor Class codes. One ABRA Gen vendor row becomes one Acumatica vendor with one default location — additional ABRA Gen locations migrate as CR.Location records under the same vendor.

ABRA Gen stock items map to Acumatica IN.InventoryItem. Item code, description, unit of measure, and cost layer data migrate. ABRA Gen item categories map to Acumatica Item Class records — the item class must exist in Acumatica before inventory items load, so FlitStack sequences this load step first in the master-data phase.

ABRA Gen sales orders migrate to Acumatica SO.SalesOrder. Header fields (order number, date, customer reference) and line items (inventory ID, quantity, unit price) map 1:1. Open orders load as active SO.SalesOrder records; completed orders load as historical records linked to the same customer account. Order totals and tax amounts recalculate in Acumatica based on the tax zone assigned to the customer.

ABRA Gen purchase orders map to Acumatica PO.PurchaseOrder. Vendor reference, line items, and expected delivery dates carry over. The Acumatica PO must reference a valid vendor location record — FlitStack resolves this by linking each PO line to the vendor's primary location. Completed ABRA Gen purchase orders load as receipt-linked historical records.

ABRA Gen AR invoices map to Acumatica AR.Invoice documents. The document number, invoice date, due date, and line amounts transfer. Acumatica's AR Invoice links to the customer and currency, and applies the tax zone from the customer's class. Partial payments recorded in ABRA Gen become separate Payment applications in Acumatica linked by document reference.

ABRA Gen AP bills map to Acumatica AP.APInvoice. The vendor invoice number, bill date, description, and line amounts transfer. FlitStack maps ABRA Gen's bill reference field to the Acumatica External Reference field so the link is traceable. Prepaid ABRA Gen entries become AP.Prepayment documents in Acumatica.

ABRA Gen chart of accounts entries map to GL.Account records in Acumatica. Account code, name, type (asset, liability, income, expense), and posting settings migrate. ABRA Gen's cost-centre or analytical dimensions map to Acumatica Subaccount (segment) codes — each dimension requires a corresponding segment in Acumatica's chart of accounts structure to be defined before GL data loads.

ABRA Gen journal entries migrate as GL.Batch records containing GL.Tran lines in Acumatica. Each ABRA Gen posting date becomes the batch date; the journal description maps to the batch description field. ABRA Gen's multi-line journal entries split into individual Tran rows linked to the account and subaccount. Only balanced, posted ABRA Gen entries migrate — draft or unposted entries are flagged for manual review.

ABRA Gen UDFs require pre-creation in Acumatica with the Usr prefix before any entity data loads. FlitStack audits every ABRA Gen UDF name and data type, then generates the Acumatica custom field definition script for your admin to apply in the target tenant. Pick-list UDFs in ABRA Gen map to Acumatica fixed-list or dynamic data field types; free-text UDFs map to string fields.

ABRA Gen analytical dimensions (cost centres, departments, projects as line attributes) map to Acumatica subaccount segments. Each ABRA Gen dimension value becomes a subaccount code in Acumatica — the subaccount must be active and linked to the appropriate account groups. Value-by-value mapping is required because dimension naming conventions differ between ABRA Gen installations.

ABRA Gen multi-company or multi-branch configurations may split into multiple Acumatica Company records or consolidate into one. FlitStack maps inter-company AR/AP postings to Acumatica inter-company settings based on whether the ABRA Gen branches share customers, vendors, or GL. The mapping decision must be agreed before migration because it affects the chart of accounts segment structure.

ABRA Gen currency codes and historical exchange rates migrate to Acumatica CM.Currency and the Exchange Rate table. Active currencies must exist in Acumatica before any transaction loads that references them. ABRA Gen's fixed vs. floating rate settings map to Acumatica's exchange rate upload mechanism.

ABRA Gen tax registration IDs and tax category assignments map to Acumatica Tax Zone and Tax Category configurations. Customer tax IDs become Tax ID fields on the customer record. ABRA Gen VAT rates map to Acumatica Tax IDs linked to the appropriate tax category — FlitStack validates that all ABRA Gen tax rates have a matching Acumatica tax agency and rate before transaction data loads.

ABRA Gen payment and settlement records map to AR.Payment (customer payments) or AP.Payment (vendor disbursements) in Acumatica. The payment amount, date, and reference number carry over. FlitStack resolves the application link by matching the payment's customer or vendor reference to the migrated document number.