Migrate from Centerpoint ERP to Epicor Prophet 21

Centerpoint CRM Contacts map directly to Epicor Customer records. The Customer table in Epicor Kinetic serves as the master party record with ShipTo and BillTo address roles. We preserve the Contact name fields (FirstName, LastName, Company), email, phone, owner assignment, and any CRM stage properties as Epicor UD (user-defined) fields. Address data migrates to the CustomerAddress table with address type roles resolved during extraction.

Centerpoint CRM Leads map to Epicor Kinetic Prospect records. The staged workflow status from Centerpoint (Lead through Opportunity) migrates to the Prospect stage and is preserved as a custom UD field for audit. Lead source attribution and any scoring values stored in Centerpoint custom fields map to Epicor UD fields on Prospect.

Centerpoint Opportunities map to Epicor SalesOrder records in a pre-converted state or to Quote records depending on where the opportunity lifecycle sits in Centerpoint. Stage assignment maps to Epicor OrderHed.Status. We preserve deal value, close date, and weighted/unweighted forecast values as UD fields. Line items from Centerpoint Opportunity products map to OrderDtl with product code and quantity resolved against the Epicor Part table.

Centerpoint CRM supports both weighted and unweighted forecast views as distinct report outputs. Epicor Kinetic does not have native dual-forecast support. We present this as a scoping option: preserve both as separate UD numeric fields on the related SalesOrder (forecast_weighted__c, forecast_unweighted__c), or migrate only the unweighted value into the standard order amount field. The customer chooses during scoping.

Centerpoint Asset Management module records map to Epicor Kinetic Equivnent (equipment master) records. Asset hierarchy, current value, depreciation details, location, and asset class all map to corresponding Equivnent fields. Parent-child asset relationships in Centerpoint map to Equivnent parent link fields. Depreciation schedules are preserved as UD fields since Epicor's native depreciation runs in the finance module.

Centerpoint Work Orders map to Epicor Kinetic Job records, which is the core production order entity in Epicor's manufacturing module. We preserve the asset link (Centerpoint asset to Epicor Job.EquipID), technician assignments, safety prerequisites, status history, and job scheduling dates. Part numbers on Work Orders resolve against Epicor Part master during import. If Centerpoint Work Orders include actual labor and material transactions, those map to Epicor JobOper and JobMtl records.

Centerpoint HR Employee records map to Epicor Kinetic Employee. Employee records contain PII requiring explicit customer authorization before migration. We extract via flat-file export, sanitize any fields the customer designates for exclusion, and load into Epicor Employee with department, role, and manager hierarchy preserved. Employee-User linking in Epicor requires matching the employee record to a provisioned Epicor user account by email.

Centerpoint Purchasing Purchase Orders map to Epicor Kinetic POHeader with line items mapped to PODetail. Vendor name and number from Centerpoint resolve to Epicor Vendor references. Line item part numbers resolve against Epicor Part or a services description if non-inventory. Unit cost, quantity ordered, and UOM all migrate directly. Open versus closed PO status maps to Epicor POHeader.OpenStatus.

Centerpoint QHSE records (compliance records, safety incidents, audits, inspections) have no direct Epicor Kinetic equivalent because Epicor's QHSE schema is industry-vertical and configuration-specific. We review the customer's QHSE configuration during discovery, map records to Epicor's Quality Management (for audits and inspections) and Incident (for safety records) UD tables if available, and document the mapping in a written schema report for the customer's admin to finalize. Non-mapped QHSE record types are archived as a CSV with Epicor UD table structure delivered as a separate import package.

Centerpoint Logistics records (shipments, routes, carrier assignments) map to Epicor Kinetic Shipment records and Customer ShipTo address configurations. Carrier name normalization is required since Centerpoint and Epicor often use different carrier master naming conventions. Route assignments migrate as UD fields on Shipment if the destination Epicor installation does not have a native routing module enabled.

Centerpoint CRM owner assignments map to Epicor Kinetic User records. We resolve by email match against the destination Epicor User table. Any Centerpoint owner without a matching Epicor User goes to a reconciliation queue for the customer's admin to provision before record import resumes. Owner historical assignment is preserved as a UD field on each record.

Centerpoint ERP is operational-first and many customers run it alongside dedicated financial accounting software. We do not migrate financial transactions, journal entries, or general ledger balances as those are outside Centerpoint's core strength and are typically sourced from a separate accounting system already. We flag the customer accounting data gap during scoping and recommend their existing financial software as the source for Epicor's AP/AR/GL migration if needed.