Migrate from Xentral ERP to Odoo ERP

Xentral stores customer and vendor records as a unified Address object. We split these into Odoo Partner records using the address_type field: type=customer creates a Partner with is_customer=True and customer_rank set by frequency; type=vendor creates a Partner with is_vendor=True. The original Xentral address_id is preserved in a custom reference field xentral_address_id__c on Partner for audit. Tax ID fields (VAT and country-specific tax numbers) migrate to Odoo's vat field and a custom tax_reference__c field.

Xentral Articles map to Odoo Product Template records, with variant support enabled if the Xentral article has size, color, or other attribute variations. The article number becomes the product's default_code (SKU); article_name maps to name. Multilingual labels stored in Xentral custom fields migrate to Odoo's product.template.inherit record with language-specific translations. Pricing tiers from Xentral map to Odoo Pricelist rules applied to the product template.

Xentral Sales Orders map to Odoo Sale Order records. The original Xentral order number is preserved in the name field and the xentral_order_id__c reference field. Line items map to sale.order.line with product_id resolved to the Odoo Product record created during the Article migration. Order status from Xentral (pending, confirmed, shipped, invoiced) maps to Odoo's sale_order_state with a custom field xentral_status__c for the original status audit trail.

Xentral Purchase Orders map to Odoo Purchase Order records. The po_number from Xentral is preserved in the name field. Vendor assignment resolves via the Partner mapping (is_vendor=True). Expected delivery dates and received quantities migrate to Odoo's date_planned and move_ids (stock moves). PO status mapping mirrors the Sales Order pattern with xentral_status__c preserved for audit.

Xentral outgoing invoices map to Odoo Account Move records with move_type=out_invoice. The original Xentral invoice number is preserved in the ref field and a custom xentral_invoice_id__c field. Multi-currency amounts migrate with the exchange rate stored in a custom field; Odoo's currency_id is set accordingly. Tax lines are mapped to Odoo's account_tax records using the tax code lookup built during discovery.

Xentral incoming invoices map to Odoo Account Move records with move_type=in_invoice. Vendor resolution uses the Partner mapping (is_vendor=True). The invoice date, due date, and amount are preserved. Multi-currency incoming invoices require the same exchange rate mapping as outgoing invoices. If the customer uses Odoo Accounting, reconciliation with the corresponding Purchase Order is preserved through the purchase_order_id link on the account.move.line records.

Xentral warehouse assignments per Article map to Odoo's Stock Location model. Each Xentral warehouse becomes an Odoo Stock Location with location_type=internal. Stock levels are migrated as Stock Quant records linked to the Product and Location. Batch and serial numbers from Xentral migrate to Odoo's lot_id and serial_number fields on stock.move.line records. A stock.freeze period is coordinated with the customer before the snapshot to ensure accurate quantities at cutover.

Xentral Project records with their custom fields migrate to Odoo Project. The original project_id is preserved in a custom xentral_project_id__c field. Task dependencies and time entries are flagged as requiring Odoo Timesheet App configuration post-migration since these require the Odoo Timesheet module to be activated. Project-linked custom fields from Xentral migrate to Odoo custom fields on the project.project model.

Xentral account codes and names map to Odoo account.account records. Tax code configurations, cost centre assignments, and SEPA bank account details are flagged as requiring manual reconfiguration in Odoo Accounting because accounting schema requirements are country-specific and depend on the customer's fiscal position settings. We deliver a written mapping of every Xentral account code to its Odoo account.account counterpart during the approach phase.

Xentral custom field definitions for Articles, Addresses, and Projects are exported as property values and mapped to Odoo custom fields (ir.model.fields with is_custom=True) on the equivalent Odoo model before data import begins. Any custom fields detected on Orders, Invoices, or Warehouse records in Xentral are flagged as workarounds (since Xentral does not natively support them on these objects) and added to a manual remediation list for post-migration review.

File attachments linked to orders, articles, addresses, and invoices are downloaded from Xentral via the API, stored with their original filename and MIME type, and uploaded to Odoo as ir.attachment records linked to the corresponding res_model and res_id. Document associations (delivery notes, credit memos) are linked to their parent Sale Order or Account Move via the attachment's res_model field.

Xentral Flows workflows stored in the Xentral Connect middleware are not accessible via the Xentral REST API and cannot be exported programmatically. During discovery, we review Xentral Connect execution logs to identify active workflows and document each one: trigger, conditions, actions, and target records. We deliver this as a written workflow inventory document with recommended Odoo Studio equivalents (automated actions, server actions) or Python-based Odoo addon logic. The customer must re-implement workflows post-migration either manually or with an Odoo partner.