Migrate from reybex to Odoo ERP

reybex Customer records (name, address, contact fields) map 1:1 to Odoo res.partner with address type differentiation (invoice address vs delivery address via partner_address fields). Country-specific address structures are preserved through street, street2, city, state_id, zip, and country_id fields. VAT number from reybex maps to res.partner.vat for EU tax validation.

reybex Articles (SKUs with variant matrices for attributes like size and color) must be split into Odoo's two-object product model. The article header becomes product.template; each variant combination becomes a separate product.product record linked via product.template.attribute_line_ids. Multi-language article names and descriptions from reybex map to product.template.name and description fields with the relevant language context. Variant-specific pricing, barcodes, and stock quantities attach to product.product records.

reybex Sales Order headers map to sale.order with partner_id resolved from the Customer mapping, currency_id set from the order's currency, and order state translated from reybex status. Line items map to sale.order.line with product_id resolved to the product.product variant, price_unit and discount preserved, and taxes mapped from reybex tax codes to Odoo account.tax records. Order references, delivery addresses, and incoterms transfer as order-level fields.

reybex Purchase Orders map to purchase.order with partner_id resolved from the reybex vendor (stored as a Customer with vendor type in reybex). Lines map to purchase.order.line with product_id and price_unit from reybex. PO approval workflows do not migrate; the Odoo purchase configuration defaults to draft state on creation and the customer's admin sets up approval rules post-migration. Vendor-specific payment terms from reybex map to account.payment.term.

reybex real-time stock quantities per warehouse location map to Odoo stock.quant records tied to stock.location records. We create location records matching reybex warehouse names, then create quant records with product_id, location_id, quantity, and lot_id (for lot/batch-tracked stock). Bin-level or serialized stock requires custom field mapping; we detect serialized articles during schema discovery and create stock.production.lot records before quant import. Stock moves and the reybex reorder-point configuration are not migrated; Odoo's Odoo stock module provides its own reorder point configuration post-migration.

reybex invoices carry GoBD-compliant metadata (TSE signatures, document numbers, tax code assignments) that must be explicitly mapped to Odoo account.move fields. We map reybex invoice date to account.move.invoice_date, invoice number to name/ref, and tax codes to account.tax records with the correct tax_group_id. The reybex TSE signature and document number are stored in custom fields on account.move (tse_signature__c, gobd_document_number__c) to preserve audit trail integrity. Multi-currency invoices require currency_id mapping from reybex currency codes to Odoo res.currency. Cancelled or voided invoices in reybex map to Odoo state= cancel with the original move preserved for audit.

reybex POS cash register transactions and bank statement lines map to Odoo account.bank.statement (for statement lines) and account.move.line (for journal entries). TSE-signed receipts carry legal weight; we preserve TSE data in a custom field on account.move.line. The reybex cash register (TSE-integrated GoBD cash register) output is exported as a structured reference document; Odoo POS module provides its own cash control configuration for post-migration setup.

reybex Project records with tasks, time entries, and budgets map to Odoo project.project and project.task. Task dependencies and milestone hierarchies from reybex are flattened during export and reconstructed as project.task dependencies in Odoo. Budget figures map to the Odoo project financial fields or to a project budgetary line object if the customer licenses the Odoo Project Enterprise features. Milestone date tracking from reybex becomes task deadline fields in Odoo.

reybex BOMs (bills of materials) and production routings map to Odoo mrp.bom and mrp.routing objects. Finished-goods outputs map to mrp.production records with product_id, product_qty, and bom_id resolved. Material consumption lines map to mrp.bom.line records with the component product and quantity. Machine capacity planning data from reybex does not transfer natively; Odoo's work center and cycle-time configuration on mrp.routing provides the equivalent planning model but must be rebuilt by the customer's manufacturing team. Production order status (draft, confirmed, in progress, done) translates to Odoo state and state字段.

reybex CRM activities (calls, emails, meetings, notes) tied to Customer records map to Odoo mail.message records (for the timeline) and mail.activity records (for task-like follow-ups). Activity types map from reybex category to Odoo activity_type_id; timestamps preserve via date field. Custom activity fields detected during schema discovery are mapped to mail.message custom field columns. Activities without a matching Odoo partner (Customer) are linked to a general company partner record during import.

Custom fields defined on reybex Articles and Customers are detected during the pre-migration schema discovery visit (required because reybex does not publish API documentation). We generate a mapping matrix of every custom field definition including its data type, and pre-create matching fields on the corresponding Odoo model before data import begins. Field types are translated: reybex text fields become char or text, numeric fields become float or integer, date fields become date, and multi-select fields become char with delimiter or selection fields in Odoo.