Migrate from BusinessCloud to Epicor Prophet 21

BusinessCloud Customer records map to Epicor Customer. BusinessCloud's regional fields (MENA address formats, tax registration numbers for VAT/GST in GCC countries) migrate to Epicor Customer standard address fields plus UD fields we create during schema provisioning. Arabic-language customer names migrate to Epicor's Name field with a secondary Latin-name UD field for English-language reporting. The customer account code from BusinessCloud becomes Epicor's Customer ID; we validate for uniqueness before import.

BusinessCloud Vendor records map to Epicor Supplier. GCC tax registration (VAT/TRN), payment terms specific to MENA markets, and multi-bank account details for international payments migrate to Epicor Supplier standard fields and UD fields. Supplier classifications (manufacturer, distributor, trader) from BusinessCloud map to Epicor Supplier Type if present, or to a custom Supplier Class UD field we create during provisioning.

BusinessCloud Product records map to Epicor Part. BusinessCloud fields including SKU, description, unit of measure, and cost price map directly to Epicor Part.PartNum, Part.Description, Part.IUM, and Part.StandardCost. Part Type (make, buy, or service) requires a mapping decision based on BusinessCloud's product classification. If BusinessCloud tracks lot numbers or serial numbers, these migrate to Epicor's PartLot and PartBin structures. We create UD fields for any BusinessCloud product attributes that have no Epicor standard equivalent.

BusinessCloud inventory quantities and warehouse assignments map to Epicor PartPlant (per-site quantity and ordering data) and WarehseBin (per-location quantities). The warehouse code mapping requires a reconciliation step because BusinessCloud warehouse naming conventions may differ from the Epicor site-warehouse structure. On-hand values migrate to Epicor's PartQtyOnHand table with a post-migration inventory valuation check against BusinessCloud's financial inventory value.

BusinessCloud GL Account structure migrates to Epicor's COA (Chart of Accounts). We preserve the BusinessCloud account code as the Epicor Account field and the account description as the Epicor Description field. If BusinessCloud uses a segment-structured account code (common in MENA financial reporting), we map each segment to an Epicor financial dimension segment. GCC companies with VAT/GST reporting requirements ensure the COA includes VAT input and output accounts matching Epicor's tax category configuration.

BusinessCloud Purchase Orders migrate to Epicor POHeader and PODetail records. We migrate open POs and recently closed POs (within the retention window defined during scoping). PO line items map to PODetail with supplier part number cross-referenced via Epicor's PartXRef table. Tax amounts from BusinessCloud's VAT/GST calculations migrate to Epicor POHeader.TaxAmt as UD fields or into Epicor's tax integration if the customer activates Avalara or Vertex.

BusinessCloud Sales Orders migrate to Epicor OrderHed and OrderDtl. Open orders, back orders, and recent completed orders (within the retention window) migrate. Line item pricing, discounts, and tax amounts carry forward as Epicor OrderDtl.DocUnitPrice, OrderDtl.DiscountPercent, and OrderDtl.TaxAmt. We resolve the Epicor Customer and ShipTo records by BusinessCloud customer code match before importing orders so that the foreign key constraint is satisfied.

If BusinessCloud includes a production module, Work Orders migrate to Epicor JobHead and JobMtl. The Job structure (production sequences, material requirements, labor estimates) maps to Epicor's JobMtl (materials) and JobOper (operations) tables. We flag JobHead.Status as JobEngineered or JobReleased based on BusinessCloud's work order status mapping defined during scoping. If BusinessCloud tracks job cards or labor tickets, these migrate to Epicor LaborDtl records linked to the corresponding JobNum.

BusinessCloud BOM records migrate to Epicor's engineering change order structure (ECOMtl for bill of materials lines). If BusinessCloud tracks multiple BOM revisions or version-controlled bills, each version migrates as a separate Epicor ECO revision. The top-level part number in BusinessCloud's BOM becomes the Epicor Part.PartNum; child components map to ECOMtl.MtlPartNum with quantity per assembly preserved.

BusinessCloud custom tables have no documented naming conventions or field schemas. We reverse-engineer the schema from the exported database dump during the discovery phase, map each BusinessCloud custom table to an Epicor User-Defined table (UD100, UD101, UD102, etc.) matching the row data type, and create the corresponding Epicor UD field definitions with appropriate data types (character, number, date, checkbox). Lookup relationships between BusinessCloud custom tables and standard objects are resolved through foreign key columns in the export before Epicor UD table import.

BusinessCloud file attachments linked to Customers, Vendors, Products, or Orders migrate to Epicor's attachment structure (ERP standard or DocStar EDM if the customer licenses it). We extract file blobs from the database dump, restore the file name and MIME type, and link each attachment to the corresponding Epicor record by BusinessCloud's entity-reference ID. We flag attachments that cannot be re-linked because the parent record was not migrated.

BusinessCloud GL journal entries migrate to Epicor GLJrnGrp (journal batch) and GLJrnDtl (journal line) records. We migrate the current fiscal year and the preceding fiscal year of transactional history based on the customer's reporting retention requirements. Epicor fiscal year setup must be completed before GL migration. Each BusinessCloud journal line debits and credits map to Epicor GLJrnDtl.DebitAmt and CreditAmt. Account segment mappings (from the COA migration) resolve the BusinessCloud account code to the Epicor COACode segment values.

BusinessCloud Accounts Payable and Accounts Receivable transactions migrate to Epicor APTran and ARTran records. Open invoices, credit memos, and payments migrate with vendor/customer references preserved. ARTran.LinkOrderNum and APTran.LinkOrderNum tie the transaction to the migrated Sales Order or Purchase Order where applicable. Tax amounts from BusinessCloud's VAT calculations migrate to Epicor's tax integration tables or UD fields based on whether the customer activates Epicor's native tax module.

BusinessCloud Users and Owner records migrate to Epicor User records. We match BusinessCloud user email addresses to Epicor Kinetic User.Email and provision the Epicor User account with the corresponding security group. BusinessCloud role or permission assignments map to Epicor Kinetic Security Role definitions. If a BusinessCloud user has no corresponding Epicor User, the record goes to a reconciliation queue for the customer's admin to provision.