Migrate from Xledger to Microsoft Dynamics 365 Business Central

Xledge Entities are the top-level organisational containers in Xledge, each holding its own Subledger, Chart of Accounts, and bank connections with live consolidation roll-up across parent-subsidiary hierarchies. When migrating to D365, each Xledge Entity maps to a D365 Legal Entity (Company in Business Central or Legal Entity in Finance and Operations), which holds its own Chart of Accounts, Fiscal Calendar, dimensional structure, and bank account references. We preserve the parent-subsidiary hierarchy as D365 consolidation groups or as a manual consolidation structure, depending on the customer's reporting requirements. Multi-currency Entity configurations are mapped to D365's currency configuration per legal entity.

The Chart of Accounts in Xledge varies significantly between organisations based on industry, entity type, and reporting requirements. Non-profit and project-based businesses use extended account dimensions with custom fields. We preserve the full account hierarchy including account type, posting definitions, and any dimension assignments. In D365, the Chart of Accounts is assigned per legal entity; for multi-entity migrations we configure either a shared/consolidated Chart of Accounts or per-legal-entity accounts with a consolidation entity to combine them.

Xledge uses Subledgers to segment AP, AR, Banking, and Project data from the General Ledger, each carrying a type classification and a reference to the owning Entity. We preserve Subledger-to-Entity as the D365 legal entity assignment. AP Subledgers map to D365 Accounts Payable, AR Subledgers to D365 Accounts Receivable, Banking Subledgers to Bank Management, and Project Subledgers to Project Management and Accounting. Subledger types that have no direct D365 equivalent are mapped to General Ledger cost categories with an explanatory note for the customer's finance team.

Customer and Supplier records in Xledge include address, contact, payment terms, tax codes, and Subledger references. Multi-entity customers and suppliers may be shared across Entities. We merge duplicate cross-Entity records into single Customer and Vendor entities in D365, and resolve the primary Entity as the default site in D365. Multi-currency Customer and Supplier balances are converted to D365's accounting currency using historical exchange rates from Xledge. Tax codes are mapped to D365 tax groups and posting profiles.

Open accounts payable and receivable in Xledge are tracked via Subledgers linked to Customers and Suppliers as invoice-level records, not as balance totals. This is a critical distinction: migrating a balance sheet figure does not recreate the underlying open invoices. We extract every open invoice record with payment terms, due dates, aging buckets, and Subledger references, and re-create them as D365 AP/AR invoice transactions. Closed invoices migrate as historical journal entries against the General Ledger. Voucher number is preserved as a tie-back reference for reconciliation.

Journal entries in Xledge span the full transaction lifecycle including posting date, amount, account, and optional dimensions. Historical journal lines with complex multi-line distributions and intercompany postings are preserved with their original posting dates. In D365, journal entries are created via General Journal lines with account, offset account, financial dimensions, and amount. Multi-currency journal amounts in Xledge are validated against D365 exchange rate tables and mapped to the correct exchange rate at the posting date. Closed-period journal entries are imported with posting restriction overrides handled by the customer's D365 admin.

Fixed Asset records in Xledge include acquisition date, cost, depreciation method, useful life, and Asset Register entries with current accumulated depreciation. We map asset definitions and current depreciation schedules to D365 Fixed Assets. Xledge depreciation methods (straight-line, declining balance, sum-of-years digits, units of production) are mapped to D365 Fixed Assets depreciation methods. Group asset configurations in Xledge are translated to D365 Fixed Asset groups. Depreciation conventions and half-year conventions are noted for manual configuration in D365 Fixed Assets parameters before the asset register is loaded.

Xledge budgets are created at the Entity level and linked to specific accounts and dimensions. Budget versions and forecast iterations are preserved as separate budget register entries in D365. We map budget line items to D365 budget models and preserve the budget amount, period distribution, and dimension assignments. Multi-entity budgets are mapped to D365 budget control configurations per legal entity. Budget versus actual reporting requires reconfiguration in D365 using the budget control module or Power BI.

Project records in Xledge track billing, revenue recognition, and cost allocation against a project's financial lifecycle, referencing specific Subledgers and carrying custom fields. In D365, Project Management and Accounting handles projects as Contracts, Lines, Projects, and Cost Categories. We map Xledge project billing milestones to D365 project contract lines, revenue recognition schedules to D365 revenue recognition parameters, and cost categories to D365 project cost categories. Project dimensions are mapped to D365 financial dimensions. If the destination D365 instance does not include Project Operations, project cost data is mapped to the General Ledger as journal entries against project-specific cost accounts.

Time entries and expense records in Xledge are linked to Employees and Projects. Expense submissions include OCR-captured receipt data and approval workflow status. We migrate entry records, amounts, project assignments, and employee references. In D365, time entries map to the Time Management module (if enabled) or to Project Time and Expense. Expense reports map to Expense Management. Note that Xledge's built-in OCR for receipt capture does not migrate; we document the OCR templates so the customer's team can configure AI Builder or an ISV receipt scanning solution in D365 post-migration.

Bank account records in Xledge include routing details, account type, currency, and Entity assignment. We migrate bank account records to D365 Bank Management under the corresponding legal entity. Account numbers, routing numbers, SWIFT/BIC codes, and currency assignments are preserved. D365 bank account reconciliation setup requires manual configuration of bank statement import formats (BAI2, CAMT, SWIFT) post-migration, as Xledge's built-in bank feeds (JPMorgan, Wells Fargo, Bank of America) stop pulling data when Xledge access ends.

Documents and attachments in Xledge are stored against journal entries, vendors, customers, and assets. We migrate document metadata and link references (file name, type, date, owner). Physical file attachments are exported as a structured archive and linked to D365 records via SharePoint document management or Dataverse attachments depending on the D365 app version. Large-volume document archives may require chunked extraction and separate upload tooling to manage storage during migration. We flag any OCR templates as non-transferable and note them for manual rebuild in D365.

Xledge's automated workflow engine handles expense approvals, cash release, purchase order sign-off, and intercompany posting controls, configured per-Entity and per-module. These do not export as structured data from Xledge. We document each active workflow during discovery, including its trigger conditions, approval chain, routing logic, and escalation paths. We deliver a D365 Workflow configuration guide with screenshots and step-by-step instructions for rebuilding each workflow in D365's Workflow Designer. The customer's D365 admin or a Microsoft partner rebuilds these post-migration. This object mapping entry exists to be explicit about what does not migrate and what documentation we provide instead.