Migrate from reybex to Infor CloudSuite Corporate

reybex Customer records map to Infor CloudSuite Business Partner (BP) with BP Type = Customer. Address structures include country-specific formatting that we map to CloudSuite BP Address records. Contact persons, phone numbers, and email addresses transfer to BP Contact roles. Tax jurisdiction assignments from reybex map to CloudSuite tax codes that must be configured in the destination tax engine before Customer import.

reybex Articles with variant matrices (size, color, material rows) must be unpacked into CloudSuite Product and Item variants. We generate one CloudSuite Product2 record per reybex Article, then create Item variants for each distinct attribute combination found in the Article matrix. ProductCode maps from reybex's internal article number. Multi-language Article descriptions map to CloudSuite localized text fields. BOM and routing assignments for manufactured Articles transfer separately as Manufacturing objects.

reybex Sales Order headers and line items map to Infor CloudSuite Sales Order. Order status, pricing, discounts, and fulfillment tracking transfer directly. reybex order numbers become CloudSuite external order references. We preserve the sales channel origin (ecommerce, marketplace, EDI) as a custom field since CloudSuite multi-channel order intake may require configuration per channel. Cancelled or archived orders require separate scoping to confirm whether they should import as historical or closed records.

reybex Purchase Orders map to Infor CloudSuite Purchase Orders with vendor assignment, expected receipt dates, and line items. Vendor relationships require reconciliation against the reybex vendor master, which may overlap with the reybex Customer master for companies that are both supplier and customer. PO approval workflows (common in reybex Run tier) do not transfer and must be reconfigured in CloudSuite procurement workflow rules.

Current stock positions by warehouse location and lot/batch transfer to CloudSuite Inventory Management. Bin-level or serialized stock requires custom field mapping that we define during schema discovery. We schedule inventory exports during low-activity windows and cross-reference against open order quantities to produce a consistent cutover balance. In-transit and allocated stock are flagged for manual post-cutover reconciliation. reybex multi-channel stock flags map to CloudSuite warehouse and inventory ownership structures.

reybex sales invoices map to Infor CloudSuite AR Invoice. Every GoBD compliance attribute — TSE signature, document number, tax code, fiscal posting date — maps to a corresponding CloudSuite financial metadata field. Multi-currency invoices require currency code and exchange rate mapping to CloudSuite's multi-currency configuration. Invoice PDFs and attachments migrate as ContentDocument records linked to the Invoice. We flag any reybex invoice with a missing or invalid TSE signature for customer finance team review before the cutover date.

reybex purchase invoices map to Infor CloudSuite AP Invoice. Vendor references resolve via the reybex vendor master to CloudSuite Business Partner (Vendor) records. Tax code assignments transfer to CloudSuite AP tax handling. Payment terms and due dates map to CloudSuite payment term codes. 3-way match status from reybex does not transfer; it must be reconfigured in CloudSuite AP workflow.

reybex bank statement records and TSE-signed cash register (POS) receipts map to CloudSuite Cash Management bank statement records and treasury entries. TSE signatures on receipts must map to CloudSuite audit trail metadata. We extract transaction dates, amounts, bank references, and reconciliation status from reybex and load them into CloudSuite bank statement import format. Open item matching status does not transfer; CloudSuite performs its own matching post-import.

reybex Project records with tasks, time entries, and budgets map to Infor CloudSuite Project if the customer licenses the Project module. Task dependencies and milestone hierarchies from reybex require flattening during export (since reybex and CloudSuite use different WBS structures) and reconstruction in CloudSuite WBS or project task grid. Budget lines map to CloudSuite project cost budgets by cost type. Projects without the CloudSuite Project module licensed are exported as reference data for manual entry.

reybex BOMs (bills of materials) and production routings map to Infor CloudSuite Manufacturing BOM and Routing structures. Finished-goods outputs and material consumption lines transfer to CloudSuite Production Order. Machine capacity planning data, shift calendars, and work center calendars do not transfer natively; we export them as reference spreadsheets for the customer's CloudSuite manufacturing consultant to reconfigure. Operation sequencing from reybex routings maps to CloudSuite work center operations.

reybex CRM activities tied to Customer records — calls, emails, meetings, tasks, notes — map to CloudSuite Activity records linked to the corresponding Business Partner. Activity types and timestamps transfer directly. Custom activity fields discovered during the schema audit phase map to CloudSuite custom Activity fields. reybex does not store activities in a separate CRM object but rather as event types attached to Customer records; we separate these into typed CloudSuite Task and Event records during transformation.

reybex custom fields on Articles and Customers are supported but require per-tenant schema discovery. We detect all custom field definitions during the pre-migration audit visit using the frontend endpoint introspection method, then generate the mapping matrix before any data extraction. CloudSuite custom fields are created in the destination tenant before migration. Field data types are mapped: reybex text to CloudSuite string, reybex number to CloudSuite decimal or integer, reybex date to CloudSuite date, and reybex multi-select to CloudSuite multi-select picklist.