Migrate from Unit4 ERP to Epicor Prophet 21

Unit4 Customer records with billing address, delivery address, payment terms, tax registration, and credit limits map directly to Epicor Customer. We use Unit4's CUSREF or customer code as the Epicor CustID dedupe key and resolve any split billing or multiple ship-to configurations against Epicor's ShipTo records. Customer-specific pricing matrices migrate to Epicor PriceLbr records if present.

Unit4 Supplier master data including bank details, W-9/W-8 BEN status, and multi-address support transfers to Epicor Vendor. We map Unit4's tax registration and payment terms to Epicor VendorPP records, preserving remittance addresses and bank account details for ACH or wire payment configuration in Epicor.

Unit4's multidimensional account structure uses cost centres and departments as natural posting axes alongside account codes. Epicor uses a flatter chart-of-accounts hierarchy where cost elements are modelled separately (as job cost codes, labour codes, and overhead allocation codes). We flatten Unit4's natural-account-plus-dimension combination into Epicor account segments, discussing whether to preserve the full account string or collapse into a simplified COA. This requires alignment on whether the customer wants cost-centre reporting in Epicor Projects/Jobs or as a separate reporting dimension.

Unit4's cost centres and departments (which carry posting rules, budget controls, and HCM assignments) require transformation for Epicor. We discuss three options: mapping cost centres to Epicor Job Cost Codes (JobPart.CostCode) for manufacturing cost tracking, mapping to Department codes in Epicor Project/Billing for services cost tracking, or storing them as a reporting dimension in Epicor's FRx reporting layer. The choice depends on whether the customer's post-migration primary use case is manufacturing or project services.

Unit4 Items with GL mapping, cost price, sales price, stock control flags, and complex pricing matrices map to Epicor Part (for manufactured or stocked items) and Product (for non-stocked items). We resolve Unit4's stock-control flags against Epicor's Part Type (Stock, Make-to-Order, Phantom, Service) and preserve pricing tiers in Epicor PriceLbr. Unit4's BOM structures migrate to Epicor's Bill of Materials (EBOM or MBOM) if the customer is transitioning to manufacturing on Epicor.

General Ledger accounts with account type, posting controls, and currency settings migrate directly from Unit4 to Epicor's GL Account master. Account codes and descriptions transfer as-is; posting controls (debit/credit rules, intercompany flags) are translated into Epicor's AcctType and JCDept fields. Currency settings map from Unit4's multi-currency configuration to Epicor's CurrencyMode.

Outstanding AP and AR documents (invoices, credit memos, payment applications) carry forward as open records in Epicor. We map document headers and line items with due dates, amounts, currency, and tax lines preserved. In Epicor, open AP lands in APInvoiceHed and APInvoiceDtl; open AR lands in InvoiceHed and InvoiceDtl. Document references and payment terms transfer to support continued payment matching and ageing reporting.

Posted journal entries with header, lines, and audit stamps transfer as locked records in Epicor. We preserve posting dates, source references, user stamps, and journal descriptions to maintain audit trails. Unit4's multi-dimensional postings (account plus cost-centre plus department) translate to Epicor's GLJrnDtl entries with the flattened account and the relevant cost-code or department reference resolved at migration time. A configured date-window (typically last two to three fiscal years) limits scope to avoid excessive migration load volumes.

Unit4 stores years of journal history across relational tables. Full historical extraction requires SQL access or GCON4 MFL export. We scope the date range with the customer, typically migrating two to three fiscal years for audit continuity and optionally archiving older periods as a structured data package outside Epicor. Each loaded journal batch is reconciled against Unit4's trial balance before the next phase begins.

Unit4 holds country-specific tax matrices with rates, jurisdictions, and posting rules across 30+ countries. We map these to Epicor TaxConnect or Epicor's internal TaxMaster records, preserving rate, tax type, and applicable transaction types. Jurisdiction combinations that do not map directly to Epicor's tax engine are flagged for manual review and configuration in the destination before the first live transaction.

Asset master records include depreciation schedules, cost-centre assignments, insurance values, and asset classification. Unit4 and Epicor may use different depreciation methods (straight-line, declining balance, units-of-production); we align on a per-asset-class conversion approach, setting the Epicor depreciation method and book-life to match the Unit4 original values, and store the original depreciation history in a custom field for audit purposes.

Bank account masters with currency, account type, bank code, and reconciliation settings migrate directly to Epicor's BankAcct table. Opening balances are mapped and reconciled in Epicor's cash-reconciliation module post-migration. Any intercompany bank accounts are flagged for manual setup in Epicor since intercompany configuration is destination-specific.

Unit4 HCM holds employment history, compensation, job titles, and department assignments. Epicor does not include a native HCM module; we migrate Employee records as Epicor Employee records (for manufacturing labour and time-tracking use cases) and note that full HCM, payroll, and talent management data requires a separate HR system migration or retention in Unit4 if the customer runs a split-stack. We flag any effective-dated employment changes that require sequencing against Epicor's labour reporting structure.

Unit4 Projects with WBS elements, cost objects, billing rates, and resource assignments require transformation for Epicor's job cost model. We map Unit4 project hierarchies to Epicor Jobs (for manufacturing and work-order cost tracking) or Epicor Projects (for project-services billing and resource planning). The customer's choice between Job-based and Project-based cost tracking is made during scoping. Unit4's project-to-GL mappings and billing rate tables transfer to Epicor's Job and Project billing configurations. Multi-customer project splitting migrates to Epicor's Multi-Company Project structure if applicable.

Unit4 Grant management with donor restrictions, fund balances, and statutory reporting for nonprofits and public-sector bodies maps partially to Epicor Projects with funding tracking. We map grant codes, funding allocations, and spend-vs-budget records to Epicor Project and ProjectPhase with a custom funding-tracking extension. Full fund-accounting compliance (restricted vs unrestricted fund classification, donor reporting by grant) requires post-migration configuration in Epicor or a fund-accounting add-on; we document the gap and deliver a written specification for the customer's admin to resolve.

Unit4 document attachments against transactions and master records are extracted via the document management API and re-associated in Epicor against the corresponding Customer, Vendor, Part, or Job record. File-size limits and format restrictions in Epicor's doc2 and Image thumbnail stores are discussed during scoping; extremely large files or non-standard formats may be stored in an external DMS with a link reference in Epicor.