Migrate from Aqilla to Acumatica

Aqilla's flat account codes map directly to Acumatica's GL Account table. Each Aqilla account becomes one Acumatica account record with the same AccountCD and Description. Active/inactive status is preserved. Account type (Asset, Liability, Equity, Revenue, Expense) maps to the Account Type field in Acumatica's GL account screen.

Aqilla allows 20+ analysis codes per transaction (e.g., Department, Region, Product Line). Acumatica has six account segments plus three named dimensions (Department, Branch, Project). We map each Aqilla analysis code to an Acumatica dimension or segment value. If there are more than nine distinct analysis codes, the remainder are stored as custom fields (UDFs) on the GL transaction detail screen.

Aqilla customers map 1:1 to Acumatica Customer records. Customer name, address, contact details, tax registration ID, payment terms, and credit limit migrate to the corresponding Acumatica fields. Aqilla's customer class (if used) maps to the Customer Class field in Acumatica. Multiple Aqilla contact records per customer are consolidated into the primary contact with additional contacts stored as Contact records linked via the Relationships tab.

Aqilla vendors map directly to Acumatica Vendor records. Vendor name, address, tax ID, payment terms, and 1099 settings migrate. Aqilla vendor categories or groups map to Acumatica's Vendor Class field. Multi-address vendors are stored as separate Location records in Acumatica, linked to the primary vendor.

Aqilla AR invoices (Sales Invoice, Credit Note) map to Acumatica AR Invoices. Invoice number, date, due date, description, tax zone, and line items (account, amount, description, quantity) transfer. Aqilla invoice-line tax codes map to Acumatica's Tax Zone and Tax Category combination. Retainage amounts become a separate line with the Retainage Tax Category flag. Credit notes are created as Credit Memo type in Acumatica AR.

Aqilla AP invoices (Purchase Invoice, Credit Note) map to Acumatica AP Bills. Line-item mapping mirrors AR above. Aqilla's bill approval status does not migrate — approval workflows are rebuilt in Acumatica separately. Prepaid invoices in Aqilla use a different screen; in Acumatica they are entered as Prepayment bills and applied against standard bills during the payment run.

Aqilla cash receipts map to Acumatica Cash Receipts. Payment method, currency, amount, and reference number transfer. Application to open invoices requires matching on invoice number and customer — we run a pre-application step to generate the application list so the correct AR Invoice documents are referenced at load time. Multi-currency cash receipts carry the original currency amount and applied exchange rate into Acumatica's currency columns.

Aqilla GL journal entries migrate to Acumatica Journal Transactions. Each Aqilla journal line (account, debit, credit, description, analysis codes) maps to a corresponding Acumatica GL batch and detail line. Batch number, batch date, post period, and the source module flag (GL, AR, AP) are preserved. Entries marked as reversing in Aqilla become reversing batches in Acumatica with the correct reversal date calculated from the original entry.

Aqilla's exchange rate table (currency pair, effective date, rate, rate type) migrates to Acumatica's Exchange Rate table. Historical rates are loaded so any GL transactions entered before the migration period retain the correct currency amounts when displayed in Acumatica's multi-currency reports. Active vs. inactive currency status is respected — only currencies in use in Aqilla are enabled in Acumatica.

Aqilla tax codes and tax rates migrate to Acumatica Tax Zones and Tax Categories. Each Aqilla tax code becomes a Tax Category in Acumatica and is assigned to the appropriate Tax Zone. Aqilla tax agencies (for remittance) become Vendor records with the Tax Agency flag set, linked to AP Tax Payable account mapping. Tax exemptions stored per customer in Aqilla are applied as Tax Exemption records on the Acumatica customer.

Aqilla container entities (group entities used for inter-company transactions) map to Acumatica Branches. Each Aqilla child entity becomes an Acumatica Branch under the parent company. Inter-company GL entries in Aqilla become inter-company journal entries or elimination journals in Acumatica, using the Inter-Company Accounting feature if enabled on the tenant.

Aqilla file attachments (invoices, receipts, supporting documents) are downloaded from the Aqilla file store and re-uploaded to Acumatica's file repository linked to the matching transaction or master record. File naming preserves the original Aqilla reference number and document type in the filename. Maximum file size follows Acumatica's 50MB per-file limit.

Aqilla custom fields defined on customers, vendors, invoices, or GL entries are recreated as User-Defined Fields in Acumatica. We create the UDFs in Acumatica before the migration run, matching the data type (text, number, date, list). UDFs are attached to the correct DAC (CR.Customer, PR.Vendor, AR.Invoice) via the UDF assignment screen. List-type UDFs require value-by-value mapping for pick-list consistency.