Migrate from Perfecto ERP to Epicor Prophet 21

Perfecto ERP's multi-level hierarchical Chart of Accounts maps directly to Epicor ERP's Chart of Accounts structure. We preserve parent-child relationships during migration using Epicor's account segment hierarchy. For multi-entity customers, each Perfecto entity's COA maps to a separate Epicor Company within the same tenant, or to separate Cost Centers within a single Epicor company, depending on the customer's consolidation requirements. Account codes longer than Epicor's defined length are truncated with a prefix-suffix mapping documented for the customer's finance team.

General Ledger transactions from Perfecto ERP migrate as Epicor GL Journal Entries with journal number, entry date, account reference, debit/credit amounts, and description preserved. Journal entry numbering sequences are carried forward where Epicor's number sequence configuration allows; otherwise we assign a migrated-entry prefix to distinguish historical entries from new ones. Closed periods in Epicor must be unlocked or extended by the customer's Epicor admin before GL migration if historical entries fall within locked fiscal periods.

Perfecto ERP customer records map 1:1 to Epicor ERP customer records with name, contact information, billing and shipping addresses, payment terms, and tax registration preserved. The End-User Customization Studio may have added non-standard fields to customer records; we audit these during discovery, map them to Epicor UD03 customer extension records, and flag any that require custom development in Epicor. Customer credit limits and payment terms migrate to the Epicor Customer Credit and Customer Tax records.

Perfecto ERP vendor records follow the same structure as customer records and map 1:1 to Epicor ERP vendor records. Vendor-specific fields including tax registration, W-9/W-8 information, and payment terms migrate to the corresponding Epicor Vendor table fields. We extract vendor address hierarchies and map them to Epicor's ship-to and pay-to address structures.

Perfecto ERP Items (finished goods, raw materials, and services) map to Epicor ERP Part records. Standard fields including part number, description, unit of measure, cost, and pricing migrate directly. Stocking types (stocked, make-to-order, discontinued) map to Epicor Part Type. The part number from Perfecto ERP becomes the Epicor Part Number; we validate for character compatibility and rename where Epicor's naming rules reject source characters.

BOM structures in Perfecto ERP require multi-pass migration sequencing because component Items must exist before parent Items can reference them. We extract the BOM hierarchy, sort by level depth, migrate all leaf-level components first, then migrate parent assemblies with their Job and Material Queue records. We validate referential integrity after each pass and flag any orphaned component references. Epicor's BOM revision tracking requires a revision code for each BOM version; we map Perfecto's BOM revision or effective date to Epicor revision fields.

Employee records from Perfecto ERP map to Epicor ERP Employee profiles with personal information, employment status, department, and job title preserved. Employee IDs from Perfecto ERP are mapped to Epicor's EmpID field, and we validate for uniqueness. Terminated employees migrate as inactive records to preserve HR history and enable historical reporting.

Perfecto ERP role-permission matrices are extracted as configuration documentation rather than migrated as code. We map each Perfecto role to its closest Epicor equivalent (Full User, Shop User, Web User, etc.) and document the permission mapping so the customer's Epicor administrator can configure security groups accordingly. Role-based field-level permissions that have no Epicor equivalent are flagged for manual review.

Perfecto ERP file attachments are stored as file references linked to records. We export all linked files to a neutral file store (network share or cloud storage) with a flat naming convention that encodes the source record type and ID, then re-link them in Epicor using Epicor's Document Management attachments by associating the file reference to the corresponding Epicor record. Epicor attachment storage paths are not portable between tenants, so the neutral file store serves as the permanent archive.

Open and historical purchase orders from Perfecto ERP migrate to Epicor ERP Purchase Order records. PO header fields (vendor, date, terms, FOB) and line items (part number, quantity, unit cost, due date) migrate directly. Closed POs migrate with their receipt history as read-only records if Epicor's fiscal period and PO status configuration permits; otherwise they migrate as historical records without further transaction processing capability.

Sales orders from Perfecto ERP migrate to Epicor ERP Sales Order records with header information (customer, order date, ship date, terms) and line items (part number, quantity, unit price, discount) preserved. Open orders migrate with their full detail so that Epicor's ATP (Available to Promise) and CTT (Capable to Promise) engines can process them post-migration. Historical orders migrate as closed or completed records depending on fulfillment status at migration time.

Perfecto ERP inventory transactions (receipts, issues, transfers, adjustments) migrate to Epicor ERP PartTran records, which form the audit trail for all inventory movement. Transaction dates, quantities, from/to warehouse and bin locations, and unit costs migrate directly. We validate that the warehouse and location codes referenced in transactions exist in Epicor before import and flag any that require warehouse setup before the transaction import phase.

Perfecto ERP approval workflows define custom approval chains tied to specific transaction types. These are configuration artifacts that have no direct Epicor equivalent in the same form. We extract the workflow definitions (approval stages, approver assignments, conditions, and thresholds) as a written configuration document and deliver it to the customer's Epicor administrator to implement using Epicor's built-in approval workflow tools post-migration.