Migrate from Circle Commerce to Epicor Prophet 21

CircleHub Customer records map to Epicor Customer with the CircleHub customer name as Customer.CustID (or Name, depending on Epicor deduplication config). We preserve CircleHub customer-specific custom fields as Epicor UD fields on Customer (e.g., Customer.UDFieldA_c). Addresses migrate as ShipTo records with the CircleHub shipping address linked via ShipToNum. Account managers and sales reps from CircleHub become CustomerSalesTerritory assignments in Epicor.

CircleHub Products map to Epicor Part records. The CircleHub SKU becomes Part.Number, description maps to Part.Description, and unit of measure maps to Part.IUM. Pricing from CircleHub becomes PartPlant unit cost and the default price list entry. Bundle and kit relationships from CircleHub map to Epicor SalesKits if the destination is configured for kit processing. Custom product attributes become Epicor UD fields on Part.

If CircleHub products use multiple units of measure (each, case, pallet), we create Epicor PartUOM records linking each UOM to the base Part with conversion factors preserved. This is critical for accurate order entry and inventory reporting in Epicor.

CircleHub Orders map to Epicor SalesOrder. The CircleHub order number becomes OrderHed.Reference fields; customer linkage uses the Customer.CustID resolved during the Customer migration phase. Order status (open, shipped, cancelled) maps to Epicor OrderRel.AvailableDate and OrderHed.OpenOrder logic. Custom order fields from CircleHub become OrderHed UD fields configured before migration.

CircleHub line items map to Epicor OrderDtl. We resolve the PartNum reference from the Product migration, map quantity to OrderDtl.OrderQty, and unit price to UnitPrice. Discounts from CircleHub line items map to OrderDtl.DiscountPercent or OrderDtl.DiscountAmount depending on the source format. Line-level custom fields become OrderDtl UD fields.

CircleHub inventory quantities per channel (online, BOPIS, warehouse) export as separate records and map to Epicor PartWhse (part-warehouse quantity). Where CircleHub tracks channel-specific allocation, we preserve the channel designation in a PartWhse UD field and flag the allocation logic for the customer's Epicor admin to implement via BPM or allocation code configuration. Multi-warehouse setups require PartWhse records per site.

CircleHub shipment records map to Epicor ShipHead (header) and ShipDtl (line detail). Carrier, tracking number, and shipment status migrate from CircleHub. If CircleHub tracks partial shipments as separate records, we consolidate into a single ShipHead with multiple ShipDtl lines per OrderDtl. Shipment timestamps preserve the original CircleHub shipment date for audit.

CircleHub Purchase Orders map to Epicor POHeader and PODetail. We resolve the vendor reference: if CircleHub stores vendor as a free-text field rather than a linked vendor record, we flag the vendor for manual review and create the corresponding Epicor Vendor record before PO import resumes. PO line items map to PODetail with PartNum, quantity, unit cost, and expected date preserved.

Every CircleHub custom field on any object becomes an Epicor UD field on the corresponding base table. During scoping we introspect the customer's CircleHub schema to capture all custom field definitions (name, data type, validation rules). We pre-create UD fields in Epicor before any data import begins. For UD fields that should auto-populate from related records (e.g., OrderHed.MyZip_c from ShipTo.Zip), we document the required BPM or data directive as part of the migration handoff.

CircleHub custom picklist or dropdown fields with a defined value set map to Epicor UD Codes (UD01 through UD08) and associated UD01A-UD08A tables. This preserves the enumerated value constraints rather than allowing free-text migration into open text fields.

CircleHub vendors referenced on Purchase Orders map to Epicor Vendor records. We extract all distinct vendor names from CircleHub PO records, check for existing Vendor.CustID matches, and create any missing Vendor records before PO import. Vendor addresses and payment terms from CircleHub transfer to VendorAddr and VendorPRet records.

CircleHub custom reports and KPIs built on customer-defined fields do not have a direct export path and cannot be migrated as report definitions. We capture report metadata during discovery (report name, objects referenced, field names, filter logic) and deliver a written inventory of every report requiring rebuild. The customer's Epicor admin or a reporting partner rebuilds reports in Epicor Report Builder or SSRS against the migrated data model.

Closed CircleHub orders migrate as Epicor SalesOrder records with OpenOrder = false. We migrate historical orders primarily for audit and customer lookup purposes; the customer defines the lookback window (typically 12-36 months of closed orders depending on reporting needs). Epicor's database performance considerations mean we may recommend archiving orders older than the defined window to a separate searchable archive rather than loading all historical data into the live ERP database.

CircleHub users referenced as order owners, customer account managers, or shipment handlers map to Epicor User records by email match. We extract all distinct owner emails, match against the destination Epicor User list, and place unmatched users in a reconciliation queue for the customer's admin to provision before record import resumes.