Migrate from Proteus ERP to Epicor Prophet 21

Proteus Customer records (contact data, buying habits, referral source) map directly to Epicor Kinetic Customer. The Customer's unique identifier from Proteus becomes the Epicor CustNum, and we preserve the referral source as a custom field on the Epicor Customer record. Email, phone, and address fields map to the standard Epicor contact and address tables. We extract all customer fields via Proteus CSV export and map them to the Epicor Customer and CustBillTo tables during DMT import.

Proteus Vendor master records map to Epicor Kinetic Supplier. Vendor codes from Proteus can collide with existing Epicor supplier numbers, so we build a vendor code mapping table during scoping and prefix or remap Proteus vendor codes to avoid collisions. PO references and payment terms transfer to Epicor Supplier records with purchasing defaults.

The Proteus accounting module uses a structured COA with GST-compliant coding. Account codes from Proteus may use different segment lengths or naming conventions than Epicor's GlAccount structure. We build an account code mapping table during discovery, align segment lengths to Epicor's COA structure, and verify that balance types (Asset, Liability, Equity, Revenue, Expense) map correctly. Historical trial balance data from Proteus transfers as opening balances in Epicor GL.

Proteus Item records (SKU, description, stock levels, pricing tiers, revenue center assignments) map to Epicor Kinetic Part. Multi-revenue-center flagging from Proteus becomes Part Plant records in Epicor, with stock levels loaded per plant. Pricing tiers map to Epicor Price Lists. The Proteus item code becomes Epicor Part Number, and we validate that no duplicate part numbers exist in the destination.

Open and historical sales orders from Proteus carry header-level and line-level data. Line item mapping requires aligning Proteus item codes with Epicor Part Numbers at migration time. We scope open orders for priority migration and load historical orders by date range to manage file size. Order totals, taxes, and shipping charges transfer to Epicor SalesOrderHed and SalesOrderDtl records.

Proteus Purchase Orders are tracked with vendor associations and line items. We preserve the PO-to-receive linkage where Epicor supports it, loading POHeader records first and then PODetail records with resolved Supplier and Part references. Open POs are prioritized; closed historical POs are loaded by date range.

Proteus Invoice records include GST/HST data and payment status. Historical invoices may require date-range scoping given export file sizes. We load invoices as AR Invoices in Epicor, preserving invoice numbers, dates, amounts, and tax codes. Payment status maps to Epicor's invoice payment terms and open/closed flags.

Proteus Employee records from the employee management module map to Epicor Kinetic Employee. We extract employee data via CSV export and map it to Epicor's Employee table, preserving employee IDs, names, departments, and employment status. Active employees are imported first; inactive or historical records are loaded separately for audit trail completeness.

Proteus e-commerce orders are integrated into the back-end with inventory sync. We pull order data and line items via CSV export, then map to Epicor Sales Order records. The challenge is aligning Proteus's e-commerce item codes with Epicor Part Numbers; we resolve this at import time using the item mapping table built during discovery.

Proteus POS transactions are captured within the same inventory and accounting system. We extract transaction-level data and map to Epicor order or receipt records depending on whether the destination Epicor instance has POS module enabled. Transaction dates and totals transfer with inventory impact recorded against the correct Part and Plant.

Proteus custom fields added within the CRM or accounting modules may not appear in the default export view. We identify custom field columns during the scoping call and request a full field export that includes them, then map each to the corresponding Epicor User Defined field (UD field) or ZDataTable framework. Epicor UD fields require either manual entry or BPM logic for auto-population after import, which we document in the handoff report.

Multi-year inventory transaction histories in Proteus can generate export files that exceed spreadsheet row limits. We handle this by chunking exports into date-range batches (quarterly or annual) and validating each chunk independently. PartTran records in Epicor capture every inventory movement (receipts, issues, adjustments, transfers), and we map Proteus transaction types to Epicor transaction codes during the transform phase.