Migrate from Aqilla to Epicor Prophet 21

Aqilla's hierarchical account structure maps to Epicor GL Account records with account codes preserved where possible. Analysis Codes (up to 20+ per transaction in Aqilla) require mapping to Epicor's cost dimension model. We capture the full account hierarchy during discovery and produce a matrix mapping each Aqilla account code and analysis code to the equivalent Epicor GL Account or cost dimension field. Where the destination uses a flatter chart, we collapse the hierarchy into parent-level accounts and flag the dimensional detail for the customer's admin to configure in Epicor's reporting layer.

Aqilla journal entries consist of a header with effective date and reference number, and line-level debits and credits with analysis codes. We migrate all posted journals with their effective dates, reference numbers, and line-level amounts. Unposted journals require period-status coordination before migration; we extract a period-status checkpoint and carry forward any late adjustments as a post-migration journal batch. Epicor's journal entry model requires a fiscal period to be open before posting; we coordinate with the customer's Epicor admin to confirm period-status settings at each phase.

Aqilla's multi-entity mode posts inter-company journals that cross-reference two or more entities in a single transaction. Epicor does not natively support inter-company journal posting across separate company codes in the same transaction. We decompose each inter-company journal into individual entity-level journal entries and generate elimination entries to zero out the inter-company balance. The elimination logic is documented and validated against the group-level trial balance post-load.

Aqilla customer records include contact details, currency settings, credit limits, and tax registration. We map customer records to Epicor Customer, preserving credit limit, payment terms, and currency settings. Open AR invoices migrate as Epicor AR Invoice records with line-item detail. Multi-currency customer settings carry forward where Epicor's currency configuration supports the same currency set.

Aqilla vendor records include multi-currency settings, payment terms, and tax codes. We map vendor records to Epicor Supplier, preserving payment terms and tax registration. Purchase invoices and credit notes migrate as Epicor AP Invoice records with full line-item detail. Epicor's supplier model supports the same multi-currency and tax code structures used in Aqilla.

Aqilla exposes container/subordinate invoice structures natively via its API. We extract purchase invoice headers and all associated lines, preserving quantity, unit price, tax code, and analysis codes on each row. Epicor AP Invoice records are created with matching line-level detail. Invoice status (posted, unposted) maps to Epicor's AP Invoice approval workflow, and any AQILLA-specific approval routing is documented for rebuild in Epicor.

Order-to-cash invoices including line items, tax breakdown, and payment terms migrate with full header and subordinate detail preserved to Epicor AR Invoice. Epicor's AR Invoice model requires a customer and invoice date; we map these from the Aqilla invoice header and preserve the original transaction reference for audit. Tax breakdown migrates to Epicor's Tax Detail records.

Aqilla asset records include acquisition date, cost, depreciation method, and book values. We map depreciation schedules to Epicor's Asset module and flag any mid-period acquisitions for period-adjusted depreciation entry. Where Aqilla uses a depreciation method not natively supported in Epicor, we document the method and carry the book value schedule for manual configuration post-migration.

Aqilla inventory items include stock valuation, costing method, and on-hand quantities. We migrate item definitions and current stock positions to Epicor Part records with PartBin entries for warehouse locations. Epicor's PartTran transaction history does not carry forward; open purchase orders and sales commitments migrate as Epicor PO and SO records, and the customer reviews any partially-received or partially-shipped orders before cutover.

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 Epicor. Epicor's cash management module requires bank account configuration including bank code and currency; we map these from the Aqilla bank account setup.

Tax codes migrate to Epicor Tax Code records with the same rates and jurisdictions. Aqilla's Making Tax Digital submission history migrates as an archive of submission records. Epicor does not have a native MTD API integration; the customer confirms any live HMRC obligations before migration and documents any third-party MTD filing tool they plan to use post-migration.

Aqilla assigns users to Core, Business, Pro, or Enterprise seat types with feature access gated by tier. We capture the full user-role inventory before migration and produce a role-mapping matrix to Epicor's user security model. Epicor uses company-code-level and module-level permissions; we map Aqilla's area-level permissions to the nearest Epicor security configuration and flag any access patterns that cannot be directly reconstructed.

Aqilla budget versions and forecast models store calculation logic specific to its reporting engine. We extract the latest approved budget values and migrate them as Epicor GL Budget records with period granularity. Budget formulas and forecast models that rely on Aqilla-native calculation logic are converted to destination formula equivalents where supported, and the customer receives a written inventory of any budget models that cannot be fully reconstructed from the raw data alone.

Aqilla provides unlimited file storage and automated document delivery. We extract linked documents by transaction reference and re-associate them with the corresponding Epicor record where the document management system supports the same file type and reference linkage. Epicor's DocStar ECM integration or native document storage receives the migrated files; we flag any attachments that cannot be linked programmatically and provide a file-indexed handoff for manual re-association.