Migrate from Solution ERP to Epicor Prophet 21

Account codes, names, and hierarchies transfer from Solution ERP to Epicor GL Account. We flag inactive accounts and map Gulf-specific VAT and excise tax codes to Epicor Tax Jurisdiction equivalents. Qatar's 5% VAT and any excise classifications require explicit mapping tables built during discovery because Epicor's standard tax engine covers country-level VAT but not Gulf-region excise codes without configuration.

Customer records including contact details, addresses, payment terms, and credit limits migrate as-is to Epicor Customer. Arabic company names are preserved in UTF-8 encoding. We confirm the destination Epicor company supports RTL field rendering if Arabic-language reporting is required. Customer payment terms map to Epicor Terms of Payment codes.

Vendor master records including tax registration numbers and bank details transfer to Epicor Supplier. We validate IBAN and bank account formats against the destination country's banking standards. Vendor payment terms map to Epicor Terms of Payment. Vendor records migrate before AP ledger entries to satisfy the foreign-key dependency in Epicor's purchase ledger.

Items with pricing, stock levels, and unit-of-measure hierarchies transfer to Epicor Part. Unit-of-measure naming conventions differ between Solution ERP and Epicor; we build a unit-of-measure conversion table during discovery. For construction-specific items, the Part's default cost and BOM (bill of materials) are preserved if they represent assemblies used in project costing.

Outstanding payables require careful date-range scoping with a migration-cutoff timestamp. We match open invoice numbers to prevent duplication and flag partial payments that span the cutoff date. Epicor AP Invoice records are created with the Supplier lookup resolved, and the outstanding balance is carried as a open item tied to the original invoice reference.

Outstanding receivables migrate as open Epicor AR Invoice records with Customer resolved by account number. We apply the same migration-cutoff timestamp used for AP. Any invoices with overpayments or credit memos are flagged for the customer's finance team to reconcile before finalising the AR migration.

Project records including budgets, milestones, and cost allocations transfer. Solution ERP's construction-specific phases and billing schedules map directly to Epicor Project Phases. Project cost centres are preserved as departments or as separate legal entities in Epicor depending on the destination's entity segmentation configuration. We flag any project with an open PO or Work Order for the customer's project manager to confirm before migration.

Solution ERP Work Orders map to Epicor Job (the parent production order) and Job Operations (the individual steps). If Solution ERP tracks labour hours and machine time per operation, these transfer to Epicor JobOper records with the appropriate work centre reference. We resolve the work centre from Solution ERP's cost centre codes during the transform phase.

POS transactions logged in Solution ERP often lack the cost-of-goods-sold split needed for accurate financial posting in Epicor. We identify POS-specific transaction types during discovery and split them into two records: an Epicor AR Invoice for the sales side and a GL Journal Entry with COGS debit and inventory credit lines applying the destination's COGS accounts. This reclassification step adds time but ensures Epicor's financial reporting accuracy.

Past journal entries transfer on request with full line-item detail. Volume-based chunking applies for large histories (typically in batches of 5,000 entries). We preserve original posting dates, fiscal periods, and audit references. Historical records are migrated last and quarantined separately from current-year data so that clean current records land first in Epicor's live fiscal year.

Attached files and document metadata (date, author, type) are extracted separately from binary content. We map document metadata to Epicor's native attachment model and link files to the corresponding Customer, Supplier, Part, or Project record. Binary file migration is scoped separately because Epicor stores attachments differently depending on whether the customer uses Epicor Data Logic or a connected DMS.

Bank account balances and cash account records migrate. We apply a migration-date cutoff balance adjustment to reconcile any transactions posted after the export snapshot. Epicor's bank reconciliation module is seeded with the opening balance from the last reconciled statement in Solution ERP.

Asset registers including acquisition dates, depreciation methods, and net book value transfer to Epicor Asset. We validate depreciation schedules against destination tax depreciation rules where applicable. Assets without a valid serial number or location code are flagged for the customer's fixed assets team to assign before the asset record is created in Epicor.

User accounts and role assignments migrate as role-name mappings because permission structures vary between ERP platforms. We flag admin-level accounts for explicit review and map Solution ERP role names to Epicor Business Logic access rights. Epicor requires at least one active admin user to be provisioned before the migration user writes records.