Migrate from Xledger to Epicor Prophet 21

Xledger Entities are the top-level organisational containers, each owning its own Subledger, Chart of Accounts, and bank connections. Epicor ERP uses Company as the legal-entity container. We map each Xledger Entity to one Epicor Company record, preserving Entity name as Company.Name and assigning a Company.CO cavity code for GL segment alignment. Multi-entity Xledger customers with shared bank accounts must resolve those shared references before Epicor import because Epicor's bank module expects one Company context per bank account.

Xledger Subledgers carry a type classification (AP, AR, Banking, Project) and reference the owning Entity. Epicor ERP does not have a Subledger object but uses Company plus separate AP, AR, and GL modules. We map each Xledger Subledger to its owning Entity's corresponding Epicor module context, preserving the Subledger type classification in a UD field on the Epicor Company record. Fiscal period definitions migrate from Xledger's Subledger calendar to Epicor's Fiscal Calendar for each Company.

Xledger's Chart of Accounts varies significantly by organisation and may include extended account dimensions for non-profits or project-based entities. Epicor ERP uses a flat or segmented account code structure configurable at the Company level. We map Xledger account codes to Epicor Account records, preserving account type (Asset, Liability, Equity, Revenue, Expense) and any Xledger dimension tags as Epicor UD codes on the Account. If Xledger uses multi-dimensional accounts, we configure Epicor's Natural Account + Department/Cost Centre segment model to match.

Xledger Customer records include address, contact, payment terms, tax codes, and Subledger references. Multi-entity Customers shared across Entities require deduplication — we merge records sharing the same tax ID or email into a single Epicor Customer and assign the primary Company context. Payment terms migrate to Epicor's Terms table and link to Customer.TermsCode. Credit limits map to Epicor Customer.CreditLimit fields.

Xledge Supplier records mirror the Customer schema: address, contact, payment terms, tax codes, Subledger reference. Shared Suppliers across Xledger Entities deduplicate to a single Epicor Supplier by tax ID. Remit-to address, one-time supplier flag, and 1099 settings map to Epicor Supplier table fields. Multi-currency supplier records carry the Xledger currency code to Epicor's SupplierRisk.PaymentMETHOD value.

Xledger journal entries span the full transaction lifecycle with posting date, amount, account, and optional dimensions. Epicor stores journal entries as GLJrnHed (header) with multiple GLJrnDtl (detail) lines. We split each multi-line Xledger journal entry into one Epicor header and multiple detail lines, preserving the original posting date, description, journal number, and source module. Detail lines carry the mapped account code, debit/credit amount, and any dimension references as EpicorExt or UD columns.

Xledger stores open AP as Subledger invoice records linked to Suppliers with payment terms and aging data. Epicor AP Invoice (APInvHed/APInvDtl) mirrors this structure with separate header and detail levels. We extract every open Xledger AP Subledger record, map it to one Epicor APInvHed with the Supplier resolved by tax ID, and create APInvDtl lines for each invoice distribution. Payment terms and due dates migrate to APInvHed.Terms and APInvHed.DueDate. Historical closed AP invoices migrate as GL journal entries against the General Ledger, not as open AP records.

Xledger open AR Subledger records link to Customers with invoice amounts, aging schedules, and currency. Epicor AR Invoice uses ARInvoice as the header with ARTran detail lines and ARInvoiceTax for tax. We map each open Xledger AR Subledger record to one Epicor ARInvoice with Customer resolved by tax ID, invoice date and due date preserved, and amount split into ARTran lines by the original distribution accounts. Currency and exchange rate migrate from Xledger's multi-currency Subledger to Epicor's Currency and Rate tables.

Xledger Bank Account records include routing details, account type, currency, and Entity assignment. Epicor BankAcct stores bank account information per Company. We map each Xledger bank account to an Epicor BankAcct record, preserving routing number, account number (masked), currency, and Company context. Bank feed configuration from Xledger (JPMorgan, Wells Fargo, Bank of America) does not migrate; we document the Xledger bank feed settings as a reference for the customer to configure Epicor's bank integration separately.

Xledger Fixed Asset records include acquisition date, cost, depreciation method, useful life, and current depreciation schedule. Epicor Fixed Assets (FaAsset table) with FaLog tracking depreciation entries. We map asset definitions from Xledger to FaAsset with AcquisitionDate, Cost, DepreciationMethod (mapped to Epicor FaAsset.DepreciationMethod values), useful life in periods, and a current net book value. Depreciation log entries carry forward into FaLog from the date of last depreciation in Xledger, with a reconciliation flag if the Xledger depreciation schedule has been modified mid-period.

Xledger budgets are created at the Entity level and linked to specific accounts and dimensions. Epicor ERP stores budgets as GlBudget with GlBudgetDtl detail lines per account and period. We map each Xledger budget version and forecast iteration to a named GlBudget record, with budget amounts distributed across period-linked GlBudgetDtl lines. Budget vs actual comparison reporting requires the same account mapping used for journal entry migration, so account mapping is completed before budget migration to ensure dimensional consistency.

Xledger Project records track billing, revenue recognition, and cost allocation against a project's financial lifecycle, with Subledger and custom field references. Epicor ERP has a Project module for project-based manufacturers and services businesses. We map Xledger Project records to Epicor Project with Phase and Task hierarchies, project status, billing rules, and revenue recognition method. Custom field values from Xledger carry into Epicor Project UD columns. WIP and billing milestones migrate as ProjectPhase records with associated revenue and cost budgets.

Xledger time entries and expense records are linked to Employees and Projects, with expense submissions including receipt data and approval workflow status. Epicor Labour captures time against jobs and projects via LaborHed/LaborDtl; expense reporting uses Epicor ExpenseReport. We map Xledger time entries to Epicor LaborHed records with the Project and Phase resolved from the Xledger Project mapping, preserving hours, cost rate, and entry date. Expense records migrate to Epicor ExpenseReport with line items, amounts, and receipt metadata. Approved status migrates but the approval workflow is not replicated.

Xledger Employee records include payroll, benefits, cost rate, and Entity assignment for multi-entity organisations. Epicor ERP stores employee data in EmpBasic (for Labour purposes) and HrEmployee (for HRM). We map Xledger Employees to Epicor EmpBasic for Labour module context and HrEmployee for HRM context, preserving employee number, name, email, cost rate, and Entity-to-Company mapping. Employee status (active, inactive) maps directly. Xledger expense and time approval hierarchies are not migrated; the Epicor approval chain is configured separately.

Xledger documents and attachments are stored against journal entries, vendors, customers, and assets. Epicor ERP uses DocType and a document management reference model rather than a flat file attachment table. We migrate document metadata (filename, description, attachment date, linked record type and ID) to a migration reference table. Large-volume document archives (over 5,000 files) require chunked migration with a document mapping manifest so that the customer can relink attachments in Epicor's document management system post-migration.