Migrate from SoftLedger to Epicor Prophet 21

SoftLedger Locations are top-level entities with independent currency, COA, and address. Each Location maps to an Epicor ERP Company (the legal entity level). If the customer operates multiple co-located divisions within one legal entity, we split the Location into one Company plus multiple Epicor Sites under that Company. The mapping decision is made during scoping based on whether the customer needs separate legal-entity financials or shared-entity management reporting.

SoftLedger's per-Location COA (account number, name, type, tax code, status) maps to Epicor GL Account records under the destination Company. We extract the full account range per entity and create corresponding Epicor accounts in the same number/name/type structure. Active/inactive status maps to the Epicor AcctFlag. Accounts used only in specific SoftLedger dimensions are flagged as restricted by Plant or Division in Epicor.

SoftLedger Customers (name, email, address, payment terms, currency, custom fields) map to Epicor Customer records. The customer number in Epicor is assigned from a configurable range; we preserve the SoftLedger customer ID in a User-Defined field for reference. Payment terms map to Epicor's Terms of Payment table. Multi-currency customers carry their billing currency through to the Epicor AR invoice currency field.

SoftLedger Vendors (name, email, address, payment terms, 1099 eligibility, currency) map to Epicor Supplier records. The 1099 eligibility flag maps to the Epicor 1099 Code field on Supplier. We preserve all vendor metadata including any custom field values in Epicor UD fields. Outstanding AP balances transfer as open PO receipts or unmatched bills depending on the destination payables workflow.

SoftLedger Journal Entries carry lines with account ID, amount, currency, dimension tags, and source references. Multi-currency entries require explicit exchange rate extraction: we pull the effective rate at posting date and any manual override stored as journal metadata, then apply the same rate type in Epicor GL. Epicor supports multiple rate types (Actual, Budget, Historical) and we assign the equivalent type based on the SoftLedger source. We chunk large journal batches to respect the SoftLedger 200 req/min API limit and load them via Epicor DMT using the GLJrnHed / GLJrnDtl template.

SoftLedger Dimensions tag journal lines with organizational attributes (department, cost center, region). We map these to Epicor Analysis Codes or map them to User-Defined fields on GLJrnDtl depending on how the customer uses dimensional reporting in Epicor. The decision is made during scoping by reviewing the customer's existing SoftLedger dimension usage and Epicor reporting patterns. All tag assignments are preserved so analytical reporting continuity is maintained.

SoftLedger AR Invoices map to Epicor AR Invoice records with status preserved (Open, Closed). We extract the invoice header, line items, and tax information, then load via DMT. Customer lookup is resolved against the Customer mapping completed in the earlier phase. Open invoices are migrated with their payment status so the destination AR team picks up the outstanding balance; closed invoices are migrated as historical records without reopening the AR cycle.

SoftLedger AP Invoices map to Epicor AP Invoice or Bill records with status preserved. The vendor lookup is resolved against the Supplier mapping. Outstanding AP balances (unpaid bills) migrate with their open status so the accounts payable team manages payment in Epicor. SoftLedger's bill-to address and ship-to address are mapped to Epicor's separate address fields on the invoice.

SoftLedger Bank Transactions link to Journal Entries and carry a reconciliation status flag. We preserve the reconciliation flag on each item and set the Epicor bank transaction to Open so the finance team completes reconciliation in the destination. Unreconciled items are not marked as reconciled during migration, which prevents prematurely closing the bank reconciliation and hiding outstanding variances.

SoftLedger Custom Fields on Invoices, Customers, Bills, and warehouse items map to Epicor UD fields on the corresponding business objects. We discover all active custom fields during scoping, map their data types to Epicor UD field types (character, numeric, date, checkbox), and create the UD field definitions in Epicor before loading data. Any SoftLedger custom fields with no Epicor equivalent are flagged as requiring a new UD field or a data model redesign.

SoftLedger uses a specific Beginning Balance upload mechanism rather than standard journal entry posting for opening trial balances. We use Epicor DMT with the GLJrnDtl template to load account opening balances, structuring the payload to match the expected format for each entity's account range. Beginning balances are loaded before any historical transaction migration so the trial balance reflects the correct starting position.

SoftLedger stores custom report definitions as JSON configurations referencing account IDs. We extract each report definition, map the referenced SoftLedger account IDs to their Epicor GL Account equivalents, and deliver a written inventory of every report requiring rebuild in Epicor BAQ or SQL-based RDL. The rebuilt queries are created by the customer's Epicor admin or partner post-migration.