Migrate your Epicor Prophet 21 data

Customer records in P21 include ship-to addresses, contact details, credit limits, and pricing tiers. Standard export via SQL views or REST API endpoints. We map each Customer record to the target system's counterpart, preserving any custom fields attached to the customer record.

Vendor master data includes address, payment terms, and buyer assignment. Exportable via SQL Server views or direct table query. We preserve the vendor-to-item linkage so replenishment relationships survive the migration.

Item master in P21 contains part numbers, UoM, warehouse assignments, replenishment methods, and lot/serial controls. Complex item structures (kits, sales kits, job assemblies) require field-level mapping to the destination item schema. We handle the UoM conversion and BOM flattening during migration.

Open and historical sales orders export via SQL queries against the OrderHead and OrderDtl tables. Line item pricing, discounts, and warehouse fulfillment data are included. We preserve order-to-customer linkage and open order status at cutover.

PO master and line data extract from the POHeader and POLine tables. Vendor pricing, lead times, and receipt schedules are included. We maintain the PO-to-vendor relationship and flag any partially received POs for manual reconciliation.

Quote headers and lines export from the QuoteHed and QuoteDtl tables. Expiration dates, pricing, and customer linkage are preserved. We flag quotes with expired statuses so the target system receives only active or recently expired records.

P21 GL accounts export from the GLAccount table. Account segment structure varies by company configuration, so we preserve the full account code string and map it to the destination's chart structure. Sub-account and cost center segments require explicit mapping.

Open payables and receivables require careful sequencing: we extract invoice headers and line distributions, then map them to the destination AP/AR modules. Partially paid invoices are flagged with remaining balance and payment schedules for reconciliation.

Warehouse master records include bin locations, picking priorities, and cross-dock configurations. Multi-warehouse setups extract cleanly via SQL. We map each warehouse and its bin structure to the destination, flagging any non-standard bin configurations.

Lot and serial number tracking links to item and transaction history in P21. We preserve the lot number, expiration date, and cost layer (FIFO/lot-specific) during migration. Full traceability chains require exporting LotCtrl and SNTran tables together.

User accounts and employee records have role-based permissions in P21. We extract user records, role assignments, and territory coverage. Owner/User assignment links to orders and quotes require field-level mapping in the destination system.

P21 supports user-defined fields (UDFs) added via the SDK or data directive framework. These are stored in extension tables or custom columns that vary by company. We do not migrate custom fields by default; we document their existence and advise the customer to re-create them post-migration or engage P21 consulting resources to map them.