Migrate from PrismERP to Epicor Prophet 21

PrismERP Customer Master records (personal details, company data, contacts, addresses, banking information) map to Epicor Customer records with associated Ship To addresses. The customer's primary contact becomes the Epicor primary Ship To contact record. We preserve all address variants (billing, shipping, plant) as separate Epicor Ship To records under the same Customer. Payment terms and credit limits migrate as Epicor Customer credit hold and terms fields.

PrismERP Vendor Master records mirror the Customer Master structure with vendor details and banking information. They map 1:1 to Epicor Supplier records. Payment terms, bank details, and W-9 information migrate as Supplier fields. If the vendor is also a customer, we flag this as a dual-role record for the customer's admin to configure in Epicor's supplier-customer linkage.

PrismERP's Chart of Accounts uses hierarchical codes that may encode multiple segment dimensions (company, region, department, product line) in a single account string. Epicor uses flat account codes with separate Cost Center, Division, and Department fields. We generate a segment mapping worksheet during the discovery phase, have the customer define how each PrismERP segment maps to Epicor's account segment fields, and apply that mapping as a transform step. The mapping is validated against PrismERP's trial balance to ensure account totals balance after segment extraction.

Open Accounts Receivable vouchers represent live outstanding balances, not just historical records. We migrate open AR invoices with their current status, outstanding amounts, due dates, and customer linkage. Epicor creates corresponding AR Invoice records and applies them to the correct Customer and Invoice Date. Partial payments are preserved as separate payment records linked to the original invoice. This is a high-integrity set—we validate the sum of migrated open AR against PrismERP's AR aging report before committing.

Open Accounts Payable vouchers migrate to Epicor AP Invoice records with vendor linkage, current outstanding amounts, due dates, and payment terms. Epicor's AP module handles invoice matching, approval workflows, and payment runs. We validate the sum of migrated open AP against PrismERP's AP aging report before committing to ensure no balance discontinuity.

PrismERP Item Master records (product definitions, pricing tiers, stock levels, warehouse assignments, BOM associations) map to Epicor Part records. Current stock quantities per warehouse become Epicor Part Plant records (one per warehouse location). PrismERP's BOM associations migrate to Epicor's Bill of Materials structure linked to the parent Part. We handle unit-of-measure conversions where PrismERP and Epicor use different stocking or selling UOMs.

PrismERP Purchase Orders (headers, line items, quantities, agreed prices, vendor assignments, approval status) from the SDM module migrate to Epicor PO Header and PO Release records. Open POs carry their current status and outstanding quantities; closed POs are migrated as read-only history. We preserve the vendor linkage through the Supplier mapping and set PO dates, terms, and buyer assignment from PrismERP fields.

PrismERP Sales Orders and related delivery/invoice documents migrate to Epicor OrderHed (header) and OrderDtl (line) records with full line-item detail, pricing, customer linkage, and lifecycle status. Open orders carry their fulfillment status; historical orders are migrated as read-only. We resolve the customer and ship-to references through the Customer mapping and preserve any order-level discounts or charges as Epicor OrderMsc records.

PrismERP Production Planning & Control orders reference BOMs and routing steps but the structure varies by manufacturing configuration. We map the production order as a Job Head record in Epicor, with materials sourced from the migrated BOM (JobMtl) and operations from the routing (JobOper). Work center assignments map to Epicor Resource Groups. Make-to-order production orders preserve their linked Sales Order reference. We flag any PrismERP production orders that cannot be fully reconstructed from migrated BOMs for customer review before loading.

PrismERP BOM definitions (component items, quantities per assembly, operations) migrate to Epicor Engineered BOMs linked to the parent Part. Phantom BOMs and multi-level BOM structures are reconstructed by traversing the PrismERP BOM hierarchy. We validate component quantities and operation step counts against PrismERP production order requirements to ensure the BOM is sufficient for migrated jobs.

The PrismERP HCM module is the highest-rated module in user reviews, making employee records the highest-confidence source dataset. Employee records (personal data, employment details, department assignments, compensation history) map to Epicor Employee records. We preserve department assignments through the Department/Cost Center mapping and set employee status, hire date, and work group from PrismERP fields. HR-specific fields that have no Epicor equivalent are documented for the customer's HR admin to configure post-migration.

PrismERP organizational hierarchy (stored independently and linked to employees, accounts, and projects) maps to Epicor Department and Work Group records. Cost center assignments on PrismERP accounts map to Epicor Cost Center fields on the account structure. We preserve the full organizational tree including any multi-company setup in PrismERP and map it to Epicor's company and site structure.

PrismERP Project System module records (project definitions, WBS elements, time entries, budget assignments) migrate to Epicor Project records. Project structures vary by industry configuration, so we scope the WBS migration with the customer during discovery and migrate only the requested depth. Billable projects map to Epicor's project billing structure. Non-billable projects migrate as reference records. Time entries become Epicor Labor records linked to the project and production order.

PrismERP's Document Management System stores files linked to transactions, master records, and projects. File attachments migrate as Epicor attachments (Document Management records or blob storage links) with their associated entity reference. We preserve the original file name, MIME type, and content hash for integrity verification. The customer defines the target storage configuration in Epicor during discovery.

PrismERP allows custom fields within modules. We discover custom field definitions during the discovery phase and include them as additional columns in the migration mapping. Custom fields migrate to Epicor UD (user-defined) fields on the equivalent Epicor table, with field types matched (string to string, number to decimal, date to date). Some PrismERP custom field types may not map directly to Epicor UD field types; these are documented for the customer's admin to configure as custom UD fields post-migration.