Migrate from R4 ENTERPRISE to Epicor Prophet 21

R4 ENTERPRISE Customer records map to Epicor Customer with full contact details, credit limits, payment terms, and currency preferences preserved. Multi-currency assignments on the Customer record migrate as read-only currency codes in Epicor. Customer ID from R4 ENTERPRISE is preserved in a custom field r4_customer_id__c for cross-reference and reconciliation. Address book entries migrate to Epicor's Address table with the primary address flagged.

R4 ENTERPRISE Vendor master records including 1099 flags, W-9 status, and multi-currency settings map to Epicor Vendor. Tax ID fields (EIN/VAT) migrate to Epicor's VendorTaxRegion table. Vendor ID from R4 ENTERPRISE is preserved in r4_vendor_id__c for reconciliation. We flag any vendors marked inactive in R4 ENTERPRISE so they are created as inactive in Epicor to prevent duplicate vendor provisioning.

R4 ENTERPRISE Items map to Epicor Part records. Unit of measure conversions, stocking locations, and lot/serial controls transfer directly. Cost-layer histories require flattening: R4 ENTERPRISE stores layered costs as separate child table rows; Epicor uses Average, Standard, or FIFO costing per part. We compute a single effective cost from the most recent R4 cost layer and populate Epicor Part.UnitCost at migration. Lot numbers and expiration dates migrate to Epicor's PartLot table.

R4 ENTERPRISE Work Orders carry routings, labor standards, and material allocations that reference BOM revisions. These map to Epicor Job records. Any routing steps tied to superseded BOM versions are flagged and excluded during migration. Open work orders migrate with their current status (released, in process, complete); closed work orders export as historical job records unless the customer elects to include full job history, which requires Epicor JobPart records for each operation step.

R4 ENTERPRISE BOMs are versioned with each revision linked to a specific effective date and item revision. We extract the currently active BOM revision as of the migration date and map it to Epicor Job BOM. Superseded revisions are flagged in a reconciliation report for the customer's Epicor admin to review. If R4 ENTERPRISE uses phantom BOMs for subassemblies, these map to Epicor's Part.AllocatableFlag configuration.

R4 ENTERPRISE chart of accounts including account type, cost-center assignments, and intercompany flags maps directly to Epicor GL Account. Segment structures transfer if Epicor is configured with matching account segment definitions. We map the full account hierarchy and preserve cost-center assignments as Epicor dimension codes. Account ID from R4 ENTERPRISE is preserved in r4_account_id__c for audit trails.

Open AP vouchers from R4 ENTERPRISE migrate as Epicor AP Invoice records with vendor, invoice number, due date, and amount. R4 ENTERPRISE stores transaction currency and functional currency separately; at migration we preserve both amounts and the original exchange rate. Epicor re-prices or retains historical rates per the customer's election. Closed AP invoices are exported as reference history unless the destination requires full invoice detail, which increases migration scope significantly.

Open AR invoices migrate to Epicor AR Invoice with customer, invoice number, due date, and amount. We preserve open invoice aging buckets so Epicor's cash-flow reporting is accurate from day one. Multi-currency AR invoices carry both transaction and functional currency amounts with original exchange rates preserved for Epicor to revalue or hold.

R4 ENTERPRISE fixed asset records including acquisition cost, depreciation method, useful life, and location map to Epicor Asset. Accumulated depreciation balance transfers as of the migration cutover date. Asset ID from R4 ENTERPRISE is preserved in r4_asset_id__c. We map R4 depreciation methods to Epicor's depreciation method equivalents (straight-line, double-declining, units-of-production).

Open R4 ENTERPRISE Sales Orders migrate to Epicor Order with customer, line items, quantities, pricing, and promised dates. Any order lines referencing discontinued items or inactive price lists in the destination are flagged in a pre-migration exception report. Closed Sales Orders are not migrated unless the customer elects to include historical order reference data, which requires Epicor OrderHed and OrderDtl records.

Open R4 ENTERPRISE Purchase Orders migrate to Epicor PO Header and PO Release records with vendor, line items, quantities, and expected receipt dates. PO lines that reference item numbers not present in the Epicor Part table are flagged for the customer to resolve before import resumes. We preserve PO status (open, released, closed) and any internal notes or approvals stored on the R4 PO header.

R4 ENTERPRISE on-hand quantities extract per location and per lot/serial number. We populate Epicor PartBin records (quantity per warehouse and bin) and link lot numbers via PartLot. Bin location names transfer from R4 to Epicor's Warehse and Bin fields. Expired lots are flagged so Epicor does not create inventory records for discontinued SKUs that cannot receive new transactions.

R4 ENTERPRISE allows user-defined fields on several master records. We extract field names and values, then map them to Epicor UD columns (like UD01, UD02, or character/date/number fields configured on the target table). A customer-approved mapping table built during scoping documents each custom field name, source value format, and destination field type. Epicor requires custom fields to be pre-configured before migration; we coordinate schema deployment with the data load.

R4 ENTERPRISE user accounts include login name, role assignment, and menu preferences. We export user records and map roles to the nearest Epicor Security Group equivalents. Active users in R4 ENTERPRISE are provisioned as active Epicor users; inactive users are provisioned as inactive to preserve historical assignments without consuming a license. Employee records in R4 ENTERPRISE map to Epicor Employee records if the customer uses Epicor HR or time and attendance modules.