Migrate from Rootstock Cloud ERP to Epicor Prophet 21

Rootstock Items map to Epicor Part records with PartNum, Description, TypeCode (Stock, Non-Stock, Service), and costing method (Standard, Average, FIFO). Stocking UOM, primary warehouse, min/max replenishment, and lot/serial tracking flags transfer directly. The Part's ClassCode maps from Rootstock's Item Class, and any custom Item fields (rootstock_custom__c) are enumerated during schema review and mapped to Epicor UD fields or Part character fields as appropriate for the destination edition.

Rootstock Sales Orders map to Epicor SalesOrder with OrderNum, CustomerNum resolved from the Account-to-Customer split, ship-to address, terms, and line items tied to Part. OrderRel records are created for each ship date and quantity release. Fulfillment status from Rootstock is preserved as an OrderHed comment field and OrderDtl line text so partial shipment history is not lost. Open versus historical order flags determine OrderHeld status in Epicor.

Rootstock Purchase Orders map to Epicor POHeader with SupplierNum resolved from the Account-to-Supplier split, PO terms, and line items tied to Part. Receipt records from Rootstock are reconciled against Epicor PORel and POReceipt records post-migration; partial receipt flags and associated Notes transfer as POReceipt comments. Vendor performance ratings stored as custom fields on Rootstock Vendor Accounts migrate to SupplierPPD (Supplier Price Per Day) or UD fields in Epicor.

Rootstock Work Orders map to Epicor JobHead (header) and JobMtl (material lines). The Work Order's linked Sales Order reference becomes a LinkToContract field or JobAsmbl reference depending on Epicor configuration. Routing steps from Rootstock migrate as JobOper records with labor hours and work center assignments. Material allocations and scrap factors transfer to JobMtl and JobOper records respectively.

This is the most complex object mapping in this migration. Rootstock BOMs support multi-version structures with effective dates and alternate BOMs per Item. Epicor uses a single-revision ECO model with effective dates per revision. We collapse multi-version BOMs by selecting the current active revision based on effective dates, mapping alternate BOMs to a UD field on the primary ECO revision. Engineering Change Order (ECO) headers from Rootstock map to Epicor ECOGroup and ECN records, with the current approved revision designated as the active PartRevision in Epicor.

Rootstock's flat location list with optional parent-warehouse relationships maps to Epicor's two-level Warehse (warehouse) and Bin (bin location) structure. Complex Rootstock hierarchies (regions > plants > warehouses > bins) are flattened to Epicor Warehse (plant/site level) with Bin records for sub-location detail. Circular location assignments identified during pre-migration review are flagged for the customer's Epicor admin to resolve before migration begins. ABC analysis codes from Rootstock transfer as Warehse character fields or UD fields.

Rootstock on-hand quantity records map to Epicor PartWhse (per warehouse) and PartBin (per bin) quantity records. The migration resolves the Part reference first, then the Warehse reference, then the Bin reference. Lot and serial number assignments transfer as PartLot and SerialNo records linked to the PartWhse/PartBin quantity.

Rootstock Account records where IsCustomer__c is true map to Epicor Customer. We extract customer-specific fields including payment terms, credit limits, tax codes, ship-via preferences, and any custom fields. The Rootstock Account's shipping addresses map to Epicor ShipTo records linked to the Customer. The Account's primary Contact migrates as the Customer's primary ShipTo contact.

Rootstock Account records where IsVendor__c is true map to Epicor Supplier. Vendor-specific fields including W-9/1099 settings, EDI identifiers, payment terms, and any custom fields transfer. Multiple vendor sites from Rootstock map to Epicor SupplierPPI (Supplier Price Per Item) records per Part and supplier. The Account-to-Supplier split is computed during extraction using Rootstock's Vendor checkbox field.

Rootstock lot master records and serial number assignments map to Epicor PartLot (lot tracking) and SerialNo (serial number) records with their associated transaction history. Full traceability links to source documents (Purchase Receipts, Work Orders, Sales Order shipments) transfer as PartTran records. Lot expiration dates and manufacturing lot attributes map to PartLot character and date fields.

Rootstock GL accounts map to Epicor GLAccount with account segment definitions, account types, and natural account classifications. Multi-company and intercompany account settings from Rootstock transfer to Epicor's Company and Segment configuration. The account code structure (natural account + segments) is preserved as configured in Epicor's COA维护.

Rootstock Fixed Asset records (available on Advanced tier) map to Epicor Asset if the destination includes the Asset Management module. Depreciation schedules, accumulated depreciation balances, and asset classification codes transfer, but depreciation method mappings require field-level review against Epicor's Asset book configurations. Assets without a destination Asset Management license are flagged during scoping and excluded from the migration scope.