Migrate from Sage Business Cloud X3 to Epicor Prophet 21

X3 Business Partners (tiers BPXX) serve as both customers and suppliers in a single entity flagged by BP Type. We split them into Epicor Kinetic Customer records (for bill-to and ship-to) and Supplier records (for procurement). Address book entries, payment terms, currency, and credit limits migrate from the X3 BP table to Epicor's Customer and Supplier tables. Custom fields on BP (stored as extended columns in X3) map to Epicor Customer/ShipTo/Search single-tenant custom fields. The BP account code becomes the Customer Num or Supplier Num in Epicor with the original X3 reference preserved in the EDISC field for audit.

X3 Sales Orders (template ZSOH) map to Epicor Kinetic SalesOrder table with order header fields (order number, date, customer, terms, ship-to) and order lines (part number, quantity, price, tax, discount). The X3 order status lifecycle (Draft, Confirmed, Shipped, Invoiced, Closed) maps to Epicor's OrderRel and OrderDtl status fields. We preserve open order lines at migration cutover and carry forward any held or flagged lines as OrderRel records with their release status intact. Pricing and discount logic from X3 migrates as manual price breaks on the order line.

X3 Purchase Orders map to Epicor Kinetic POHeader and PODetail. X3 vendor, site, payment terms, and currency map to Epicor VendorNum, PrcConNum, Terms and CurrencyCode. PO line items map to PODetail with part number or miscellaneous charge, quantity ordered, unit cost, and tax. Approved and pending-approval status in X3 maps to Epicor's PO status field. We carry forward any blanket PO release history as separate PO release records in Epicor.

X3 hierarchical chart of accounts with segment codes and cost centers maps to Epicor Kinetic GLLedger and GLAccount. Each X3 company code with its currency settings becomes an Epicor Kinetic Ledger with the corresponding currency. Account segments (e.g., Department-Product-Region) map to the Epicor GLAccount segment fields or natural account with COA segments. We preserve the X3 account description, account type, and posting dimension tags. Historical balance records from X3 migrate as GLJrnLine entries for the relevant periods to seed Epicor's opening balances.

X3 AP and AR modules store open invoices, credit limits, payment terms, and aging data. We map open AP invoices (not yet paid) to Epicor Kinetic APInvoiceHed and APInvoiceDtl, with the vendor number, invoice number, date, due date, and amount. Open AR invoices migrate to ARInvoiceHed and ARInvoiceDtl with customer, invoice number, and amount. Aging data does not carry as a field in Epicor but is computed from the invoice date, due date, and payment terms. We flag records with holds or disputes in X3 for manual review before migration.

X3 Fixed Assets include acquisition cost, depreciation schedules, asset registers, and tax-book depreciation per legislation. We map each asset to Epicor Kinetic FaAsset with asset number, description, class, location, and acquisition details. Depreciation books (GAAP, tax, statutory) from X3 migrate to Epicor FaAssetReg records, each with its own depreciation method and convention. Current net book value and accumulated depreciation are seeded as opening balances in the relevant book. We map asset disposals, transfers, and revaluations from X3 as FaAsset transactions.

X3 Products with Bills of Materials, routings, lot/serial tracking, and expiry dates map to Epicor Kinetic Part records. Stock levels per site migrate to PartWhse records with quantity on hand, allocated, and available. Multi-location tracking in X3 becomes multiple PartWhse records across Epicor Sites. Lot and serial numbers from X3 migrate to PartLot records with expiry date preserved. BOM and routing headers from X3 map to Part and PartRev (BOM revision) and PartMtl (BOM line) and PartOpr (routing operation) in Epicor Kinetic. The BOM-routing linkage requires a separate reconciliation pass because X3 stores BOM and routing in separate linked tables.

X3 Production Orders with BOM links, routing operations, work centres, and consumption tracking map to Epicor Kinetic JobHead, JobMtl, and JobOper. We extract JobHead with job number, status, start and end dates, and the part number. JobMtl carries the component lines with part number, quantity per, scrap percent, and issue method. JobOper carries the routing operations with work centre, operation sequence, setup and run time, and labor and machine rates. We map the X3 work order status (Released, In Process, Complete, Closed) to Epicor JobHead.JobComplete. Active JobMtl and JobOper records migrate with the parent job header; completed historical jobs migrate as part transaction history only.

X3 supports parallel depreciation books per asset (GAAP book, tax book, local statutory). Each book carries its own depreciation method, convention, and schedule. We map each X3 depreciation book to a corresponding FaAssetReg record in Epicor Kinetic, preserving the book ID, depreciation method (straight-line, declining balance, units of production), useful life, and the accumulated depreciation balance per book. We seed the current period depreciation amounts as opening entries so Epicor's depreciation run produces the correct next-period accrual.

X3 Budgets tied to the GL spanning multiple periods and scenarios map to Epicor Kinetic GlBudget records with budget code, fiscal year, and period amounts per account or segment. Commitments representing purchase orders or contracts that have not yet posted migrate as Epicor Kinetic open PO records. We map budget version codes from X3 to Epicor GlBudget.BudgetCode and carry forward budget line descriptions for audit trail.

X3 user management with function-level permissions per site and company maps to Epicor Kinetic User and UserComp records. X3 named user IDs (not email-based in older deployments) map to Epicor Kinetic UserCode. Role and function permissions from X3's access control list map to Epicor Kinetic UserFile permissions by Company and Site. We flag any X3 user without a matching email for the customer to provision in Epicor's identity provider before user records import. Orphaned permissions are documented in the reconciliation report for manual remediation.

X3 custom fields stored as extended columns on business objects map to Epicor Kinetic user-defined (UD) fields. We detect all X3 custom fields during discovery, identify the parent table and column name, and create a corresponding Epicor UD field on the mapped object before data load begins. Data types are mapped: X3 text to Epicor Character, X3 numeric to Decimal or Integer, X3 date to Date, X3 logical to CheckBox. We preserve the field label and help text from X3 in the Epicor field description.

X3 multi-company architecture with separate legal entities and manual intercompany journal duplication requires reconstruction in Epicor Kinetic. We identify each X3 company code as a separate Epicor Kinetic Company record. Intercompany journal entries identified in X3 (by counterparty account segments) are reconstructed as Epicor Kinetic journal entries with proper debit-credit pairs across companies. The customer defines the intercompany elimination logic during scoping; we implement it as Epicor Kinetic Elimination rules and GLJrnEntry records for historical periods.

X3 tax codes and rates per legislation map to Epicor Kinetic TaxRegion and TaxCode records. Sales tax, VAT, and withholding tax configurations from X3 carry forward as TaxRegion entries linked to the relevant Company and ShipTo/CustCnt. We map the X3 tax calculation method (inclusive, exclusive, compound) to the Epicor tax group configuration. Epicor's tax connectivity to external services (Tax Connect, Vertex) is configured separately post-migration.