Migrate from Xledger to Infor CloudSuite Corporate

Xledger Entities map to Infor CloudSuite Operating Units (financial consolidation level) or Companies within the Financials module, depending on the CloudSuite edition deployed. Each Xledger Entity carries its own Subledger, Chart of Accounts, and bank connections. We extract the Entity hierarchy during discovery, map it to Infor's organisational structure, and flag any Entities that are purely holding companies versus operating Entities because Infor handles these differently in consolidation reports.

Xledger Subledgers (AP, AR, Banking, Project by Entity) map to Infor's AP, AR, Cash Management, and Project Accounting modules scoped to the corresponding Operating Unit. Multi-entity Subledgers shared across Entities require Infor intercompany setup that we document during discovery and configure as part of the mapping phase. Subledger type classification (AP, AR, Banking, Project) drives the Infor module assignment.

Xledger's Chart of Accounts varies by Entity and industry; non-profits and project-based businesses use extended account dimensions. We map each Entity's account structure to Infor's Chart of Accounts, preserving account codes, descriptions, and any active dimensions. Multi-segment account codes in Xledger (if configured) map to Infor's dimension structure or cost element hierarchy depending on the CloudSuite edition. Account mapping is validated against Infor's account type requirements before import.

Xledger Customer and Supplier records include address, contact, payment terms, tax codes, and Subledger references. Multi-entity customers and suppliers shared across Entities are de-duplicated by tax ID or registration number and re-linked to the appropriate Infor Operating Unit. We map payment terms from Xledger to Infor's terms codes, and tax codes to Infor's tax configuration. Customer and Supplier migration must complete before any AR or AP open item migration because those records hold lookups to the customer and supplier.

Historical journal lines in Xledger span posting date, amount, account, and optional dimensions. We map journal lines to Infor's GL entry structure, preserving multi-line distributions and intercompany postings as flagged entries. Journal entry numbering conventions from Xledger are retained in Infor's reference fields. Closed periods in Infor are opened as needed for historical imports; Infor CloudSuite requires period status to be set to Open before posting.

Open AP and AR in Xledger are tracked via Subledgers linked to Customers and Suppliers. We extract every outstanding invoice, payment terms, aging schedule, and discount terms, and map to Infor's AP and AR open item records. Closed invoices are migrated as historical journal entries against the General Ledger. Infor's AP and AR modules require the supplier and customer master records to be loaded first, so we sequence AP/AR migration after the Customer and Supplier phase.

Bank account records in Xledger include routing details, account type, currency, and Entity assignment. We migrate bank account definitions to Infor's Cash Management module. Bank feed integrations (Xledger's built-in feeds to JPMorgan, Wells Fargo, Bank of America) stop at cutover; we document the existing bank feed configuration so the customer's Infor administrator can configure equivalent feeds through Infor ION or a supported bank connectivity partner.

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 to Infor's Asset Management module. Depreciation calculations are re-computed in Infor from the last depreciation run date forward using the migrated depreciation method. Assets linked to specific Infor Operating Units are assigned during import. Assets with pending disposals or revaluations are flagged for manual resolution before migration.

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 Infor's budget management structure, maintaining the version hierarchy and dimension assignments. Budget migration is typically scoped to the current and next fiscal year; older versions are migrated as historical records or archived at customer preference.

Time entries and expense records in Xledger are linked to Employees and Projects. Expense submissions include approval workflow status (which does not migrate). We migrate entry records, amounts, project assignments, and cost centre allocations to Infor's time and expense module. Expense receipts stored as document attachments migrate as metadata references; the customer's Infor administrator configures Infor Document Management for storage and retrieval post-migration.

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, billing rules, and cost allocations to Infor's project module. Revenue recognition schedules are migrated as Infor billing milestones or rate-based schedules depending on the CloudSuite edition. Projects without an active Subledger in Xledger are flagged for Infor project type assignment during mapping.

Documents and attachments in Xledger are stored against journal entries, vendors, customers, and assets. We migrate document metadata (filename, type, date, reference) and link references. Full document content migration is scoped at the customer's request; large-volume document archives may require chunked export with Infor IDM (Infor Document Management) configured as the destination repository. The customer's Infor administrator sets up IDM before document metadata migration begins.