Migrate from reybex to Dolibarr ERP

reybex Customer records map to Dolibarr ThirdParty (societe). reybex stores name, address, contact fields, and country-specific address structures that map to Dolibarr's address, country, and state fields. reybex's customer-specific custom fields (discovered during the pre-migration audit) map to Dolibarr Extra Fields on ThirdParty. reybex Customer categories map to Dolibarr categories via the Categorie API.

reybex Articles (SKUs with variant matrices) map to Dolibarr Product. reybex stores variants as structured rows (size, color, material) that we unpack into Dolibarr product variants using Dolibarr's multi-price and variant attribute system. Multi-language article descriptions map to Dolibarr's translated description fields. reybex hs_sku maps to Dolibarr's ref field. Stock quantities per warehouse map to Dolibarr's warehouse-linked stock entries.

reybex Sales Orders map to Dolibarr Customer Order (CommandeClient). Order headers (order number, date, status, customer reference) map directly. Line items map to order lines with product reference, quantity, unit price, VAT rate, and discount preserved. reybex order status values map to Dolibarr ORDER_STATUS values (Draft, Validated, Shipped, Closed). reybex fulfillment tracking references migrate as notes on the order.

reybex Purchase Orders map to Dolibarr Supplier Order (CommandeFournisseur). reybex vendor relationships require mapping to Dolibarr ThirdParty records with the Supplier flag set. PO line items (product, quantity, expected delivery date, cost price) map to Dolibarr order lines. PO approval workflows do not transfer and must be reconfigured in Dolibarr under Home > Setup > Workflows.

reybex real-time stock quantities per warehouse map to Dolibarr warehouse-linked stock entries. reybex's warehouse locations map to Dolibarr Entrepot records. Lot and batch tracking in reybex maps to Dolibarr's lot/serial number tracking on Product if enabled. We export stock as a snapshot taken during a low-activity window and cross-reference against open order quantities to produce a consistent cutover balance.

reybex invoices carry GoBD-compliant metadata (TSE signatures, document numbers, tax codes, VAT rate assignments) that must map explicitly to Dolibarr invoice fields. reybex's invoice headers and line items map to Dolibarr Facture and FactureLigne. reybex's tax code assignments map to Dolibarr VAT rate configuration (regles_tva table). Any invoice with missing TSE metadata is flagged for manual review before the cutover. Multi-currency invoices require mapping reybex currency codes to Dolibarr multicurrency settings.

reybex's GoBD-compliant bank statement and POS transaction records require mapping to Dolibarr's bank reconciliation module (ComptaBank). TSE-signed receipts map to Dolibarr's document attachment model. Cash register transactions map to Dolibarr's cash management entries. reybex's account assignment structure (Geldkonto) maps to Dolibarr's bank account and analytical account dimensions.

reybex Project records including tasks, time entries, and budgets map to Dolibarr Projet and tasks (Task). reybex task dependencies and milestone hierarchies require flattening during export and reconstruction in Dolibarr's task management interface. Dolibarr's project billing features (linking invoices to projects) provide a partial replacement for reybex's project cost tracking. We flag any project-level financial reporting gaps during the migration audit.

reybex BOMs (bills of materials) and production routings map to Dolibarr Product with Nomenclature (BOM) module enabled. reybex's finished-goods outputs and material consumption lines map to Dolibarr BOM components. Machine capacity planning data and production scheduling parameters do not transfer natively because Dolibarr's production module lacks capacity planning. We perform a gap assessment during scoping to determine whether Dolibarr's production module meets the customer's needs or whether a third-party production add-on is required.

reybex Sales Activities (calls, emails, meetings, tasks) tied to Customer records map to Dolibarr Agenda (Action) records. reybex activity types and timestamps preserve; custom activity fields require schema discovery before mapping. reybex email body content maps to Dolibarr Action with full notes preserved. Meeting location and attendee information maps to Dolibarr Action's location and contact linkage.

reybex custom fields on Articles and Customers require schema discovery per tenant during the pre-migration audit visit. We detect all custom field definitions, data types, and picklist values, then create equivalent Dolibarr Extra Fields on the corresponding objects under Setup > Dictionaries > Extra Fields before the data migration phase begins. reybex multi-select custom fields map to Dolibarr's checkbox group or multiple-select Extra Field types.

reybex EDI transaction sets (ORDERS, INVOIC, DESADV) are platform-native message formats that cannot be meaningfully imported into Dolibarr. We export EDI partner mappings, partnership configurations, and transaction set metadata as a reference document (CSV and PDF) for the customer's admin to re-establish EDI in Dolibarr via a third-party EDI marketplace module or external EDI gateway. The EDI partner re-onboarding workflow is documented separately as a manual workstream.

reybex Users map to Dolibarr User records. We resolve by email match. Any reybex user without a matching Dolibarr User is held in a reconciliation queue for the customer's admin to provision before record import resumes. User permissions (sales, purchasing, admin) map to Dolibarr's permission groups under Home > Setup > Users & Groups.