Migrate from Aqilla to Infor CloudSuite Corporate

Aqilla's hierarchical account structure maps to Infor CloudSuite's account master table. We preserve the account code, description, account type (P&L vs Balance Sheet), and any active/inactive status. Aqilla's analysis codes (up to 20 per transaction) map to CloudSuite dimension or cost-centre fields; if CloudSuite edition uses fewer native dimensions, we map the most-used analysis codes and flag the remainder for manual entry or extension configuration.

Aqilla journal headers with line-level debits and credits map to CloudSuite GL journal entry records. We preserve the journal number, posting date, effective date, reference, and description. Source document references (invoice numbers, receipt numbers) are stored as journal line memo fields. Post-lock periods in Aqilla must be confirmed closed before migration so that entries land in the correct open period in CloudSuite.

Aqilla's inter-company journals cross-reference two or more entities in a single posting. Infor CloudSuite does not natively support multi-entity inter-company posting in the same way. We decompose these into individual entity postings and generate elimination entries as a separate migration phase. We carry an entity-mapping table from Aqilla and produce elimination journal entries that zero out the inter-company balance positions post-load.

Aqilla customer records (contact details, currency settings, credit limits, tax registration) map to CloudSuite customer master data. Open AR items migrate as individual invoice records with due dates, amounts, and payment terms preserved. We flag any partial payments or credit memos for manual review in CloudSuite before finalising the AR aging report.

Aqilla vendor records with multi-currency settings, payment terms, and tax codes map to CloudSuite vendor master data. Open purchase invoices and vouchers migrate as AP records with header and line detail preserved. Tax codes are mapped to CloudSuite tax codes; any Aqilla-specific tax logic (Making Tax Digital compliance) is flagged for review with the customer and their Infor implementation partner.

Aqilla's container/subordinate purchase invoice structure (header with associated line rows) maps to CloudSuite purchase voucher records with line-item detail. We preserve quantity, unit price, tax code, and analysis codes on each line. The purchase invoice number becomes the voucher reference, and the posting date maps to the voucher date. Unposted invoices are flagged separately and require period-status confirmation before migration.

Aqilla order-to-cash invoices with line items, tax breakdown, and payment terms map to CloudSuite AR invoice records. Header and subordinate line detail is preserved. Invoice PDFs and attachments migrate as ContentDocument records linked to the invoice entity in CloudSuite where the document storage API supports it.

Aqilla fixed asset records (acquisition date, cost, depreciation method, book values) map to CloudSuite fixed asset module. We preserve depreciation schedules and flag mid-period acquisitions for period adjustment. If Aqilla uses a depreciation method not supported in CloudSuite, we document the variance and carry the net book value as the opening balance in the destination asset record.

Aqilla inventory items with stock valuation, costing method, and on-hand quantities map to CloudSuite item master data. We migrate item definitions and current stock positions. Open purchase orders and sales commitments require separate purchase and sales order migration; these are handled as transactional records after the item master is established and validated.

Aqilla bank accounts with imported transactions and cash-matching data map to CloudSuite bank account records. Reconciled and unreconciled positions carry forward; unmatched items are flagged in a reconciliation exception report for the customer's AP/AR team to resolve post-migration in CloudSuite's bank reconciliation module.

Aqilla user seats (Core/Business/Pro/Enterprise) are tier-gated permission models that do not map directly to Infor CloudSuite role constructs. We extract the full user inventory with their permission scopes, map active users to CloudSuite roles and security groups, and produce a role-mapping matrix. Any Aqilla permissions that have no CloudSuite equivalent are flagged for manual configuration.

Aqilla documents linked to transactions migrate as file attachments associated with the corresponding record in CloudSuite. We extract by transaction reference and re-associate in CloudSuite where the document management API supports it. Document types (invoices, receipts, contracts) map to CloudSuite document category or content library structures.

Aqilla budget data (period granularity, account association) migrates as numeric budget values attached to the corresponding account and period in CloudSuite. Budget formulas specific to Aqilla's reporting engine cannot be reconstructed in CloudSuite's formula syntax. We migrate the latest approved budget version and flag forecast models requiring rebuild in CloudSuite's budget entry or Birst planning layer.