Migrate from Xledger to Acumatica

Xledger's multi-entity hierarchy maps to Acumatica's company record structure. Each Xledger entity becomes an Acumatica company. If Xledger uses deep intercompany hierarchies, the structure may need flattening or translation to Acumatica branch records. We deliver an entity-to-company mapping plan before migration so the Acumatica organizational structure is defined first.

Xledger account codes and descriptions map directly to Acumatica AccountCode and Description fields. Account groups from Xledger map to Acumatica Account Groups for financial statement grouping. The complexity arises when Xledger embeds segment values in account codes — we extract those and either flatten them into subaccounts or use Acumatica's segment codes feature, depending on your accounting team preference.

Xledger vendor records map to Acumatica Vendor DAC with all payment terms, tax registration IDs, and RemitAddress details preserved. Xledger vendors assigned to multiple entities require decisions about consolidation or intercompany configuration in Acumatica before migration, since Acumatica vendors are tied to one company record.

Xledger customer records migrate to Acumatica Customer DAC with name, class, credit limit, and tax registration fields. As with vendors, Xledger's multi-entity customer assignments require restructuring in Acumatica's single-company model — we map one primary company per customer and surface the multi-entity assignments as a reference field for reconciliation.

Xledger bank account configurations and payment methods map to Acumatica CashAccount records and PaymentMethod settings. Subaccount numbering alignment is verified before migration since mismatched subaccount structures can cause bank reconciliation failures post-migration. We cross-reference Xledger's bank account assignments against Acumatica's cash account chart to ensure all payment flows route correctly through the appropriate accounts and branches.

Xledger GL batches and journal lines with full line-level descriptions and reference document numbers map to Acumatica Batch and GLTran records. BatchNbr in Acumatica corresponds to Xledger's batch identifier; RefNbr maps to the journal entry or source document reference. We preserve all debit and credit line amounts with original transaction dates and descriptions.

Xledger AP documents migrate to Acumatica APInvoice DAC with original invoice dates, due dates, vendor references, and line-level amounts. Open AP documents map with status Open; fully paid invoices migrate as Closed. The batch structure from Xledger is flattened into individual Acumatica invoice records during import.

Xledger AR documents migrate to Acumatica ARInvoice DAC with customer references, invoice dates, due dates, and line-level amounts preserved. Invoice type and status map from Xledger document states to Acumatica's Open/Closed status field. We verify outstanding AR totals match between systems before and after migration.

Xledger inventory items with stock item flag, unit of measure, and standard cost map to Acumatica InventoryItem DAC. Unit-of-measure conversions are preserved through Acumatica's UOM conversion table. Warehouse assignments in Xledger are mapped to Acumatica branches, which requires clarification on how Xledger's entity-level warehouse configuration should translate.

Xledger project records and cost entries map to Acumatica's Project Management module — PMProject for project headers and PMTran for individual cost transactions with cost code, cost type, and amount. Project templates in Xledger become Acumatica project templates. We preserve original cost entry dates and cost code assignments for project billing continuity.

Xledger custom object values defined through its object value schema map to Acumatica custom fields on the relevant DAC extension. These require a customization project in Acumatica to be defined before migration runs. We audit Xledger's custom field usage and produce an Acumatica customization project specification as part of the migration plan.

Xledger workflow definitions for approval chains, posting approvals, and intercompany workflows have no direct equivalent in Acumatica. Acumatica uses its Automation Engine and generic inquiry framework for similar logic, but workflows must be redesigned and built manually in Acumatica. We export Xledger workflow definitions as a reference document to support the Acumatica rebuild effort.

Xledger custom reports and dashboards built on its flex screen and reporting module do not transfer to Acumatica, which uses its own report designer, Generic Inquiries, and BI connector. Underlying data migrates so reports can be rebuilt in Acumatica's framework, but the report objects themselves require manual recreation.

Files attached to Xledger records (vendor documents, invoice attachments, project files) are re-uploaded to Acumatica's Note and Attachment DAC linked to the corresponding migrated record. File size limits per Acumatica's attachment configuration apply, and inline images in notes are extracted and rehosted.