Migrate your Xledger data

Entities are the top-level organisational containers in Xledger. Each Entity has its own Subledger, Chart of Accounts, and bank connections. We migrate all Entity definitions and their hierarchical parent-child relationships to support multi-entity consolidation in the destination system.

The Chart of Accounts structure varies significantly between organisations based on industry, entity type, and reporting requirements. Non-profits and project-based businesses use extended account dimensions. We map accounts to destination equivalents using account code patterns and descriptions as the primary matching keys.

Xledger uses Subledgers to segment AP, AR, Banking, and Project data from the General Ledger. Subledgers carry a type classification and reference the owning Entity. We preserve Subledger-to-Entity assignments and flag any Subledger-specific custom fields for manual review.

Customer and Supplier records in Xledger include address, contact, payment terms, tax codes, and Subledger references. Multi-entity customers and suppliers may be shared across Entities. We merge duplicate contacts and preserve Subledger linkage, but custom field mapping depends on the destination system's account structure.

Journal entries in Xledger span the full transaction lifecycle including posting date, amount, account, and optional dimensions. Historical journal lines with complex multi-line distributions and intercompany references require detailed mapping to the destination's posting format.

Open accounts payable and receivable in Xledger are tracked via Subledgers linked to Customers and Suppliers. We extract outstanding invoice balances, payment terms, and aging schedules as open records. These map to the destination's AP/AR module but may require invoice-level re-creation in the target system.

Bank account records in Xledger include routing details, account type, currency, and Entity assignment. Bank API integrations download transactions nightly into Xledger's bank feed. We migrate bank account definitions and their Entity associations, though historical bank feeds are typically not migratable.

Fixed Asset records in Xledger include acquisition date, cost, depreciation method, useful life, and Asset Register entries. We map asset definitions and current depreciation schedules. Depreciation schedules already posted to the General Ledger are handled as historical journal entries.

Xledger budgets are created at the Entity level and linked to specific accounts and dimensions. Budget versions and forecast iterations are preserved. We map budget line items to destination budget structures, but budget locking states and approval workflows do not transfer.

Time entries and expense records in Xledger are linked to Employees and Projects. Expense submissions include OCR-captured receipts and approval workflow status. We migrate entry records, amounts, and project associations; individual receipt images may require separate file transfer.

Project records in Xledger track billing, revenue recognition, and cost allocation against a project's financial lifecycle. Projects reference specific Subledgers and carry custom fields. We map project definitions and their financial associations, but time-tracking allocation rules require destination-specific configuration.

Documents and attachments in Xledger are stored against journal entries, vendors, customers, and assets. We migrate document metadata and link references. Large-volume document archives may require chunked export to preserve the original file naming conventions.