Migrate from Epicor Prophet 21 to Infor CloudSuite Corporate

P21 Customer records (ship-to addresses, contact details, credit limits, pricing tiers, buyer assignments) map to Infor CloudSuite Business Partner records with Customer role. The P21 customer number becomes the Infor PartyId, and the P21 ship-to structure maps to Infor address roles. We preserve pricing tier and credit limit as Infor Business Partner attributes. Territory assignments in P21 map to Infor's organizational hierarchy or a custom field.

P21 Vendor master records (address, payment terms, lead times, buyer assignment) map to Infor CloudSuite Business Partner records with Supplier role. The vendor-to-item linkage in P21 (preferred vendor per part) migrates as Infor Supplier Part Cross-Reference records. Payment terms from P21 (net-30, net-60, etc.) map to Infor Payment Terms codes by lookup table.

P21 Item master (part numbers, UoM, warehouse assignments, replenishment methods, lot/serial controls, cost layers) maps to Infor Item master. Complex item structures in P21 (kits, sales kits, job assemblies) require disaggregation: each kit component maps as a separate Infor item with a bill of materials or sales kit relationship. Lot/serial control flags and FIFO/lot-specific cost layer settings migrate to Infor's inventory and cost configuration. We flag any P21 items using non-standard UoM conversions for manual review before Infor load.

P21 stores sales orders across OrderHead (header) and OrderDtl (line) tables. Each OrderHead record splits into one Infor Sales Order header; each OrderDtl row becomes an Infor Sales Order line referencing the parent header. We preserve the order-to-customer link via PartyId resolution, the warehouse fulfillment assignment, pricing and discount details, and the original P21 order number as a cross-reference field. Open orders migrate in a first pass; historical closed orders migrate in a second pass to separate active from archive data.

P21 Purchase Orders split across POHeader and POLine tables. Each POHeader becomes an Infor PO header; each POLine becomes an Infor PO line with vendor pricing, lead times, and receipt schedule preserved. Partially received POs are flagged with receipt history so the Infor receiving team can reconcile open quantities. PO approvals and buyer assignments map to Infor workflow assignments or ION approval routing.

P21 Quotes use the same header/detail split as orders. QuoteHed becomes an Infor Quotation header; QuoteDtl becomes Quotation lines. We flag quotes with expired statuses (based on P21's QuoteHed.ExpirationDate) so the target system receives only valid quotes. Quote-to-customer linkage resolves via the same PartyId lookup used for sales orders. Quotes that converted to orders in P21 are linked to their corresponding Infor Sales Order by a cross-reference field.

P21 Warehouse master records (bin locations, picking priorities, cross-dock configurations, replenishment settings) map to Infor Warehouse and Location records. Multi-warehouse setups extract cleanly from P21 SQL and map to Infor's site structure. Bin location formats (zone-rack-shelf-bin) are preserved as Infor location codes, and cross-dock assignments map to Infor warehouse configuration. Each P21 warehouse's picking priority sequence migrates as an Infor location assignment rule.

P21 GL accounts export from the GLAccount table. Account segment structure varies by P21 company configuration, so we preserve the full account code string as an Infor GL Account code. The segment structure (company-department-account-subaccount) maps to Infor's account code hierarchy or dimension segments. We flag any accounts with non-standard segment lengths for the customer's Infor admin to validate against the destination chart template.

Open payables and receivables require careful sequencing: we extract invoice headers and line distributions from P21's APInvHed/ARInvoiceHed tables, map them to Infor AP/AR invoice records, and flag partially paid invoices with remaining balance and payment schedules. The vendor/customer PartyId must be resolved before invoice migration. We preserve original invoice numbers, invoice dates, due dates, and payment terms for reconciliation in Infor.

Lot and serial number tracking in P21 links to item and transaction history via LotSeqNum and related tables. We preserve the lot number, expiration date, and cost layer (FIFO or lot-specific) during migration. Full traceability chains are maintained as Infor inventory transactions linked to the migrated lot/serial records. The lot-to-supplier and lot-to-customer linkage from P21's LotCustLnk and LotNumVendor tables maps to Infor's lot attribute fields.

P21 user accounts and employee records include role-based permissions and territory assignments. We extract user records, role assignments, and territory coverage. Owner/User assignment links to orders and quotes require field-level mapping to Infor's user provisioning and organizational hierarchy. Territory coverage from P21 maps to Infor's organizational unit assignments. We do not migrate P21 user passwords; Infor admins provision new credentials post-migration.