Migrate from Aqilla to Microsoft Dynamics 365 Business Central

Aqilla hierarchical account codes map directly to Dynamics 365 main accounts within the configured account structure. We extract the full account tree from Aqilla including the active/inactive status, account type (revenue, expense, asset, liability, equity), and whether the account carries a posting profile. Dynamics 365 Financial Dimensions (attached at the Aqilla Analysis Code level) require a dimension set design session with the customer before migration so that the relevant analysis dimensions become default posting dimensions in the destination.

Posted journal entries from Aqilla migrate as general journal lines in Dynamics 365 Finance or Business Central. Each line carries the account, financial dimension combination, debit or credit amount in both transaction currency and accounting currency, and the posting date. We preserve the journal batch number and voucher number as reference fields. Unposted or draft journals require the destination period to be open before loading; we flag these separately as a post-migration adjustment batch.

Aqilla inter-company journals cross-reference two or more entities in a single posting. Dynamics 365 Finance handles inter-company through separate legal entities with inter-company journal pairs. We decompose each Aqilla inter-company journal into two or more individual entity postings, generate the corresponding elimination entries using the Dynamics 365 inter-company trading partner setup, and carry a customer-reviewed entity mapping table to the destination. Group-level trial balance reconciliation happens post-load.

Aqilla customer records migrate to Dynamics 365 Customer with contact details, currency settings, credit limit, payment terms, and tax registration number preserved. Open AR items (invoices, credit notes, payments on account) load as open customer transactions using the open transaction import template. Customer number in Aqilla becomes the Dynamics 365 Customer Account number, used as the dedupe key during import.

Vendor records migrate with multi-currency settings, payment terms, and tax codes preserved. Purchase invoices and credit notes currently open in Aqilla AP load as open vendor transactions in Dynamics 365, with the invoice number, posting date, due date, and net amount mapped. Vendor number from Aqilla becomes the Vendor Account number in Dynamics 365.

Aqilla's container/subordinate invoice structure maps to Dynamics 365 Finance purchase invoice header and line rows. We extract every line with quantity, unit price, tax code, and the associated Analysis Codes, then assign each Analysis Code to a corresponding Financial Dimension on the invoice line. Header-level charges and discount codes are decomposed into separate line rows per Dynamics 365 conventions.

Order-to-cash invoices including line items, tax breakdown, and payment terms migrate with header and subordinate detail preserved. Closed and posted sales invoices load as historical invoice records in Dynamics 365. Open sales orders load as open sales order lines with confirmed quantities and prices. Dynamics 365 Finance uses a product dimension (product, variant, configuration) that may require mapping from Aqilla product codes if the two systems use different SKU structures.

Aqilla asset records carry acquisition date, cost, depreciation method, accumulated depreciation, and net book value. We migrate the latest asset balances into Dynamics 365 Fixed Asset records and map the depreciation method to the nearest Dynamics 365 depreciation profile. Mid-period acquisitions are flagged for period adjustment after the first close in Dynamics 365.

Aqilla inventory item definitions with stock valuation, costing method, and on-hand quantities migrate as Released Products in Dynamics 365. Open purchase orders and open sales commitments load as separate transaction records after the item master data is in place. Inventory dimensions (site, warehouse, colour, size) in Dynamics 365 require a mapping review with the customer where the source data uses different dimension labels.

Aqilla bank accounts migrate as Dynamics 365 Bank Account records with the bank account number and currency. Reconciled and unreconciled transaction positions carry forward; unreconciled items are flagged in a reconciliation exception report for the customer's AP team to resolve in the destination. Dynamics 365 bank reconciliation workflows are enabled post-migration.

Aqilla tax codes migrate as Microsoft Dynamics 365 Sales Tax Codes with the relevant rate, applicability, and posting profile. MTD submission history is not migrated to Dynamics 365 as the tax authority holds the record; we provide a submission reference sheet for the customer's admin to re-enroll MTD forVAT in the new system with HMRC. Any pending MTD submissions are filed before the cutover date.

Aqilla users on Core, Business, Pro, and Enterprise seat tiers are mapped to corresponding Dynamics 365 Security Roles. We capture the full user-role inventory from Aqilla including any permission by area patterns, and produce a role-mapping matrix. Access that was controlled via Aqilla's object-level permissions is translated to the nearest Dynamics 365 role duty and privilege structure. Inactive users are provisioned as inactive in Dynamics 365 to preserve historical owner records.

Aqilla supports file attachments on transactions with unlimited storage. We extract linked documents by transaction reference and re-associate them with the corresponding Dynamics 365 record. If the destination uses SharePoint for document management, we map file paths to the SharePoint document library structure and re-link the references in Dynamics 365.

The latest approved budget version migrates as budget register entries in Dynamics 365 Finance, with account code and period-amount detail preserved. Budget models that use Aqilla-native formulas are not migrated as code; the formula logic is documented and the customer's finance team rebuilds the forecast model using Dynamics 365 Budgeting module constructs.