Migrate from reybex to Microsoft Dynamics 365 Business Central

reybex Customers map to Dynamics 365 Customer records, which can serve as a Person or Company customer type. Address records (street, city, postal code, country) map to the Dynamics 365 Address table; German address formats (Straße, Hausnummer split) are preserved as separate address lines or parsed into structured fields during transform. reybex customer-specific pricing tiers map to Customer Price Groups in Dynamics 365. Tax identification numbers map to VAT Registration Number on the Customer card.

reybex Articles (SKUs with variant matrices for size, color, etc.) unpack into Dynamics 365 Item records. The parent Article becomes the Item; each variant (size-color combination) becomes a separate Item Variant attached to the parent. Multi-language article descriptions (German, English) map to Dynamics 365 Item Translation records. reybex's article-specific units of measure (Stück, kg, Liter) map to Dynamics 365 Unit of Measure groups. Article pricing from reybex price lists maps to Sales Prices on the Item or to Customer Price Groups for customer-specific pricing.

reybex Sales Orders map to Microsoft Dynamics 365 Sales Order. The order header (customer reference, order date, delivery date, shipping method) maps to corresponding Sales Order header fields. Line items resolve the Item number from the Article mapping and preserve quantity, unit price, discount percent, and line amount. reybex order status (opened, confirmed, partially shipped, completed, cancelled) maps to Dynamics 365 Status and Shipment Status fields. Open orders migrate first; archived or completed orders migrate based on the customer's data retention scope defined during scoping.

reybex Purchase Orders map to Dynamics 365 Purchase Order. The vendor reference maps to the Dynamics 365 Vendor account resolved from the vendor mapping. PO approval workflows from reybex (configured in the Run tier) do not transfer; we flag the workflow structure in the automation inventory document for the customer's admin to reconfigure in Dynamics 365 using Approval Workflows or Power Automate. Line items map by resolving the Item number from the Article mapping against the vendor's item cross-reference if configured.

reybex real-time stock quantities map to Dynamics 365 Item Ledger Entries for quantity tracking and Warehouse Entries for bin-level placement. Each reybex warehouse location maps to a Dynamics 365 Location code. Lot and batch tracking data from reybex maps to Dynamics 365 Item Tracking Codes and Item Tracking Lines if the customer uses serialized or lot-tracked inventory. We schedule inventory exports during low-activity windows and cross-reference open order quantities to produce a consistent cutover balance that excludes in-flight allocations.

reybex Invoices map to Microsoft Dynamics 365 Sales Invoice records with GoBD-compliant metadata explicitly preserved. TSE signatures, document numbers, and tax codes (German tax codes MwSt 19%, 7%, 0%, and intra-Community supply codes) map to the corresponding Dynamics 365 fields on the posted invoice. We flag any reybex invoice records missing TSE data for manual review before the cutover. Multi-currency invoices from EU cross-border trade map to Dynamics 365 Currency and exchange rate fields with the original currency amount preserved alongside the euro equivalent.

reybex bank statements and POS cash register transactions (TSE-signed receipts) map to Dynamics 365 Bank Account Ledger Entries or Cash Document records depending on the selected Finance module configuration. TSE-signed receipt metadata maps to external document number or a custom field capturing the TSE signature hash for audit trail continuity. German cash register (Kasse) configurations map to Dynamics 365 Cash Desk functionality in Business Central if the German localization is enabled.

reybex Project records map to Dynamics 365 Job (Business Central) or Project Operations entities. Task hierarchies and milestones from reybex flatten to Job Task Lines and Job Planning Lines in Business Central. Time entries map to Job Journal Lines for hours; expense items map to Job Journal Lines for item consumption. Budget amounts from reybex are stored as reference values in Job Budget fields for the customer's admin to verify post-migration. Project status (active, on-hold, completed) maps to the Job status field.

reybex BOMs (bills of materials) and production routings map to Dynamics 365 Production Bill of Materials and Production Routing. Finished goods outputs map to Production Order header and line items with the quantity and due date preserved. Material consumption lines map to Production Order Component Lines resolved against the Item mapping. Machine capacity planning data (work center calendars, setup and run times) maps to Dynamics 365 Capacity Ledger Entries if the customer uses capacity scheduling; this requires a partner-configured work center and machine center setup in the destination.

reybex CRM activities (calls, emails, meetings, tasks, notes) tied to customer records map to Dynamics 365 Activity records. reybex call dispositions and duration map to the Dynamics 365 Phone Call subject with custom fields for disposition and duration. reybex meeting entries with attendee lists map to Dynamics 365 Appointment records with the attendee list preserved in the Required Attendees and Optional Attendees fields. reybex task engagements map to Dynamics 365 Task records with Status, Priority, and ActivityDate preserved.

reybex custom fields on Articles, Customers, and Sales Orders require schema discovery per tenant before mapping. We detect all custom field definitions during the pre-migration audit visit using reybex's frontend endpoint introspection method. Each discovered custom field is assigned a Dynamics 365 field type (Text, Decimal, Integer, Boolean, Option) and mapped to the corresponding table extension in Business Central or Finance. Custom field data migrates as part of the parent object import phase.

reybex EDI transaction sets (ORDERS, INVOIC, DESADV) are platform-native message formats that do not transfer to Dynamics 365 as functional records. We export EDI partner mappings (partner ID, IDOC type, message format) as a structured reference document that the customer's implementation partner or EDI middleware provider (LANSA, Extrom, or SEEBURGER) uses to reconfigure EDI in Dynamics 365. Actual EDI transaction history remains in reybex for audit reference but is not imported into Dynamics 365.