Migrate your Aqilla data
UK-based cloud ERP for multi-entity, multi-currency finance teams. Built for group consolidation, FX automation, and purchase-to-pay workflows with tiered per-seat pricing.
In its favor
Why people choose Aqilla
The signal that keeps Aqilla on the shortlist. Sourced from G2, Capterra, and customer scoping calls.
Customers migrate from Sage or legacy on-premise systems to Aqilla for its cloud-native, multi-entity consolidation capabilities and real-time financial reporting.
Users value the ability to build custom financial reports on demand, tailoring output to specific business requirements without relying on rigid templates.
Multi-currency and FX automation make Aqilla a practical choice for organisations with international subsidiaries or cross-border transactions.
The platform's integration with Excel and reporting tools like Sharperlight reduces month-end and year-end close timelines compared to older accounting software.
UK-based personal support and structured implementation approach attract finance teams that want guided onboarding rather than self-serve setup.
Aqilla is perceived as expensive relative to competing ERPs, with per-user pricing that scales significantly at the Business and Pro tiers.
User permission configuration is described as confusing — controlling access at granular object and area levels requires effort to get right.
Some customers report that development requests for fine-tuning or bug fixes take extended time to address after the first year of use.
Organisations with simple, single-entity requirements find the multi-company and analysis-code complexity unnecessary overhead for their use case.
Reasons to switch
Why people leave Aqilla
The recurring reasons buyers give for replacing Aqilla. Presented as facts, not knocks.
Platform scorecard
Strengths, weaknesses, and where Aqilla fits
Grades across six dimensions, plus a SWOT-style view of where the platform shines and where it falls short.
SWOT — strengths, weaknesses, and use-case fit
Strengths
Weaknesses
Where it works
Where it struggles
Pricing tiers
Aqilla pricing overview
Aqilla uses per-user, per-month seat pricing across four named tiers ranging from £15 to £92. Feature gating is horizontal — advanced modules like API Integration, Automated FX, and Strategic Management Reporting are sold as add-ons on top of the base tier.
Core
Tier 1 of 4
£15/user/month
What's included
Need help selecting your ERP?
Book a free 30 minute consultationPricing is informational. FlitStack AI does not bill on Aqilla's schedule — see our quote-based pricing →
What gets migrated
Aqilla object support
Object-by-object support for Aqilla migrations. Per-pair details surface during scoping.
Chart of Accounts
Fully supportedAqilla uses a hierarchical account structure with Analysis Codes (20+ per transaction) attached to every posting. We map account codes and analysis dimensions 1:1 unless the destination uses a flat chart, in which case we collapse and tag with a destination custom field.
Journal Entries
Mapping requiredAqilla stores journal entries as a header with line-level debits and credits. We migrate all posted journals with their effective dates and reference numbers; open/unposted journals require period-status confirmation before migration.
Customers / Accounts Receivable
Fully supportedCustomer records include contact details, currency settings, credit limits, and tax registration. We preserve all AR open items and map them to the destination's receivables module.
Vendors / Accounts Payable
Fully supportedVendor records support multi-currency settings, payment terms, and tax codes. Purchase invoices and credit notes are carried over as line-item headers with subordinate rows.
Purchase Invoices (Header + Lines)
Fully supportedAqilla's API natively exposes container/subordinate invoice structures. We extract the header and all associated lines, preserving quantity, unit price, tax code, and analysis codes on each row.
Sales Invoices
Fully supportedOrder-to-Cash invoices including line items, tax breakdown, and payment terms are migrated with full header and subordinate detail preserved.
Fixed Assets
Mapping requiredAsset records include acquisition date, cost, depreciation method, and book values. We map depreciation schedules to the destination's asset module and flag any mid-period acquisitions for period-adjustment after cutover.
Inventory Items
Mapping requiredAqilla supports inventory control with stock valuation, costing method, and on-hand quantities. We migrate item definitions and current stock positions; open purchase orders and sales commitments require separate workflow mapping.
Bank Accounts and Reconciliations
Fully supportedAqilla maintains bank accounts with imported transactions, cash matching, and bank reconciliation workflows. We carry over reconciled and unreconciled positions and flag unmatched items for re-reconciliation in the destination.
Tax Codes and Submissions
Mapping requiredTax codes are tied to Aqilla's Making Tax Digital submission capability. We migrate tax codes and any outstanding submission history; active MTD obligations should be confirmed with HMRC before migration to avoid filing gaps.
Users and Roles
Mapping requiredUser seats are tier-gated (Core / Business / Pro / Enterprise) and permission scopes vary by tier. We map active users to the appropriate seat type and flag any access patterns (e.g., permission by area) that require manual reconfiguration in the destination.
Multi-Company and Inter-Company Transactions
Mapping requiredAqilla's multi-company mode enforces inter-company journals across entities. We sequence inter-company eliminations separately and carry the entity mapping table to the destination.
Attachments and Documents
Mapping requiredAqilla provides unlimited file storage and automated document delivery. We extract linked documents by reference and re-associate them with the corresponding transaction in the destination where the storage model permits.
Budgets and Forecasts
Mapping requiredBudget data is stored with period granularity and account association. We migrate the latest approved budget version; forecast models that rely on Aqilla-specific formulas are converted to destination equivalents or flagged for rebuild.
| Object | Support | Notes |
|---|---|---|
| Chart of Accounts | Fully supported | Aqilla uses a hierarchical account structure with Analysis Codes (20+ per transaction) attached to every posting. We map account codes and analysis dimensions 1:1 unless the destination uses a flat chart, in which case we collapse and tag with a destination custom field. |
| Journal Entries | Mapping required | Aqilla stores journal entries as a header with line-level debits and credits. We migrate all posted journals with their effective dates and reference numbers; open/unposted journals require period-status confirmation before migration. |
| Customers / Accounts Receivable | Fully supported | Customer records include contact details, currency settings, credit limits, and tax registration. We preserve all AR open items and map them to the destination's receivables module. |
| Vendors / Accounts Payable | Fully supported | Vendor records support multi-currency settings, payment terms, and tax codes. Purchase invoices and credit notes are carried over as line-item headers with subordinate rows. |
| Purchase Invoices (Header + Lines) | Fully supported | Aqilla's API natively exposes container/subordinate invoice structures. We extract the header and all associated lines, preserving quantity, unit price, tax code, and analysis codes on each row. |
| Sales Invoices | Fully supported | Order-to-Cash invoices including line items, tax breakdown, and payment terms are migrated with full header and subordinate detail preserved. |
| Fixed Assets | Mapping required | Asset records include acquisition date, cost, depreciation method, and book values. We map depreciation schedules to the destination's asset module and flag any mid-period acquisitions for period-adjustment after cutover. |
| Inventory Items | Mapping required | Aqilla supports inventory control with stock valuation, costing method, and on-hand quantities. We migrate item definitions and current stock positions; open purchase orders and sales commitments require separate workflow mapping. |
| Bank Accounts and Reconciliations | Fully supported | Aqilla maintains bank accounts with imported transactions, cash matching, and bank reconciliation workflows. We carry over reconciled and unreconciled positions and flag unmatched items for re-reconciliation in the destination. |
| Tax Codes and Submissions | Mapping required | Tax codes are tied to Aqilla's Making Tax Digital submission capability. We migrate tax codes and any outstanding submission history; active MTD obligations should be confirmed with HMRC before migration to avoid filing gaps. |
| Users and Roles | Mapping required | User seats are tier-gated (Core / Business / Pro / Enterprise) and permission scopes vary by tier. We map active users to the appropriate seat type and flag any access patterns (e.g., permission by area) that require manual reconfiguration in the destination. |
| Multi-Company and Inter-Company Transactions | Mapping required | Aqilla's multi-company mode enforces inter-company journals across entities. We sequence inter-company eliminations separately and carry the entity mapping table to the destination. |
| Attachments and Documents | Mapping required | Aqilla provides unlimited file storage and automated document delivery. We extract linked documents by reference and re-associate them with the corresponding transaction in the destination where the storage model permits. |
| Budgets and Forecasts | Mapping required | Budget data is stored with period granularity and account association. We migrate the latest approved budget version; forecast models that rely on Aqilla-specific formulas are converted to destination equivalents or flagged for rebuild. |
Gotchas
What to watch for in Aqilla migrations
Issues we've hit on past Aqilla migrations, tagged by severity. FlitStack AI handles every one — surfacing them up front because buyer engineering teams want to know.
API is an add-on gated behind Enterprise tier
Multi-company and inter-company journals require sequencing
User seat tiers do not directly map to destination role models
Open journal periods must be closed before final cutover
Budgets and forecast models use Aqilla-native formulas
| Severity | Issue |
|---|---|
| High | API is an add-on gated behind Enterprise tier |
| High | Multi-company and inter-company journals require sequencing |
| Medium | User seat tiers do not directly map to destination role models |
| Medium | Open journal periods must be closed before final cutover |
| Low | Budgets and forecast models use Aqilla-native formulas |
Leaving Aqilla?
Where Aqilla customers move next
6 destinations Aqilla can migrate to.
How a Aqilla migration works
Four steps, Aqilla-specific
Connect
Not publicly documented — gated add-on behind Enterprise tier into Aqilla. Scopes limited to read-only on the data we move.
Map
We translate Aqilla-specific structures (custom fields, objects, value lists) to the destination's model.
Sample
Test with a 50–200 record subset to validate Aqilla quirks before production.
Migrate
Full migration with Aqilla rate-limit handling. Rollback available throughout.
FAQ
Aqilla migration FAQ
Answers to the questions buyers ask most during Aqilla migration scoping. Not seeing yours? Book a call.
Can't find your answer?
Walk through your Aqilla migration with a real engineer — 30 minutes, free, written quote within 24 hours.
Book a free 30 minute consultationReady when you are
Migrate Aqilla.
Without the rebuild.
Free scoping call with a migration engineer. Tell us about your Aqilla setup and destination — written quote back within a business day.