Migrate from reybex to Epicor Prophet 21

reybex Customer records map to Epicor Customer with address fields preserved in EU format (Street, HouseNumber, PostalCode, City, CountryCode). We map reybex country-specific address structures to Epicor Customer address fields and detect duplicate customers by email and TaxId during import. Customer payment terms, credit limits, and tax jurisdiction codes migrate to Epicor Customer CreditHold and TaxZone fields. Any EU VAT identification number stored in reybex custom fields maps to Epicor Tax Exempt number.

reybex Articles with variant matrices (size, color, material combinations) stored as structured rows must be unpacked into Epicor Part Master with PartRev (BOM) and PartBin or PartWhse location records. Multi-language article descriptions (German, English) map to Epicor's language-pack description fields if the destination is configured for multilingual; otherwise the primary language description is preserved. reybex ArticleType (product, service, assembly) maps to TypeCode (Stocked, Non-Stock, Service, Expense) on Epicor Part.

reybex Sales Order headers and line items map to Epicor SalesOrder and SalesOrderDetail. Order status, pricing, discounts, and fulfillment tracking preserve. reybex order numbers become Customer PO references in Epicor; Epicor generates its own order number sequence. We map reybex order channels (marketplace, B2B shop, POS) to Epicor OrderComment or a custom field for traceability. Cancelled or archived reybex orders migrate as closed orders with Status=Complete and OrderHeld=False.

reybex Purchase Orders map to Epicor POHeader and PODetail. Vendor relationships require reconciliation against the Epicor Supplier master (matched by supplier number or TaxId). reybex PO approval workflow states (draft, submitted, approved, closed) do not transfer; Epicor PO approval is a separate configuration step post-migration. Expected receipt dates and promised dates migrate to Epicor DueDate and PromiseDate fields.

reybex real-time stock quantities across warehouse locations and channels map to Epicor PartWhse (quantity per site-warehouse) and PartBin (quantity per bin location). Lot and batch tracking numbers from reybex migrate to PartLot records with LotTran history. Serialized stock requires Epicor PartPlant.SerialTracking setting enabled before import; we handle this during schema validation. Inventory export runs during a coordinated low-activity window to avoid discrepancies with in-flight orders.

reybex invoices carry GoBD-compliant metadata including TSE signatures (TSE_Signature), document numbers (FiscalDocumentNumber), and German tax code assignments (TaxCode_DE). We map these to Epicor ARInvoice with InvcHead TaxRegion, TaxConnectCalc flag, and custom fiscal reference fields. Multi-currency invoices from reybex require Epicor Currency and ExchangeRate records to be provisioned before import. Any missing TSE metadata is flagged for manual review before cutover to preserve audit-readiness.

reybex bank statement records and TSE-signed cash register (POS) transactions map to Epicor CashHead and CashDtl. TSE receipt signatures preserve in Epicor custom fields since Epicor does not have a native TSE concept. Bank account reconciliation data migrates to Epicor BankBcDetail for bank statement import functionality. reybex POS transactions migrate as Epicor CashDtl with TenderType and ShiftNum for shift-based cash management.

reybex Project records including tasks, time entries, and budgets map to Epicor Project and ProjectTask. reybex task dependencies and milestone hierarchies require flattening during export and reconstruction in Epicor's WBS-style task structure. Time entries migrate to LabErnDetail linked to ProjectPhase. Project status (active, on-hold, completed) maps to Epicor PhaseJob flag or a custom ProjectStatus field.

reybex BOMs (bills of materials) and production routings map to Epicor PartRev (BOM definition) and JobMtl/JobOper (job-based material and operation consumption). Finished-goods outputs map to Epicor Part. reybex material consumption lines become JobMtl with MtlSeq and RequiredQty. Machine capacity planning data (work center utilization percentages) does not transfer natively; we provide a capacity planning reference document for the customer to configure Epicor Work Centers post-migration.

reybex sales activities (calls, emails, notes) tied to Customer records map to Epicor Erp.SysActivity or CRM module equivalents if the destination Epicor license includes CRM. Activity types and timestamps migrate; custom activity fields require schema discovery during the pre-migration audit. If Epicor CRM is not licensed, activities migrate to Epicor ProjectNotes or remain in a reference export for manual re-entry.

reybex custom fields on Articles and Customers require schema discovery per tenant during the pre-migration audit visit. We detect all custom field definitions, map them to Epicor UD fields (PartLot_c, Customer_c, etc.) or standard fields, and generate a mapping matrix before the migration window opens. Custom fields on EDI documents cannot migrate.

reybex EDI transaction sets (ORDERS, INVOIC, DESADV) are platform-native message formats that cannot be meaningfully migrated to Epicor's EDI layer without re-establishing EDI partner mappings. We export EDI partner configuration metadata (partner ID, message type, transport) as a reference document and recommend the customer's IT team or an EDI specialist re-onboard partners to Epicor's EDI module post-migration. Historical EDI transaction records are not transferable.