Migrate from Xentral ERP to Dolibarr ERP

Xentral's unified Address object (used for both customers and vendors) maps directly to Dolibarr ThirdParty records. We preserve the address type distinction using Dolibarr's third-party type field (Customer, Supplier, or Both). Tax IDs from Xentral map to Dolibarr's VAT/Siret fields. Custom Address fields configured in Xentral migrate as Dolibarr ExtraFields on ThirdParty if the destination is self-hosted or DoliCloud Premium; if Basic tier, we store them as delimited text in a custom note field and document them for manual post-migration field creation.

Xentral Articles map to Dolibarr Product records. We preserve the article type (product, service, assembly), unit of measure, multilingual labels, and item-specific pricing rules. Xentral's custom Article fields migrate as Dolibarr ExtraFields on Product. Batch and serial number configurations map to Dolibarr's lot/serial tracking module if the destination instance has the necessary module enabled.

Xentral Sales Orders map to Dolibarr Order documents. We preserve the original order number, creation date, status, assigned warehouse, shipping information, and all line items referencing the mapped Product records. The document hierarchy (order linked to invoice and delivery note) is preserved through Dolibarr's document linking. Xentral order number becomes Dolibarr's ref_customer field for customer reference continuity.

Xentral Purchase Orders map to Dolibarr SupplierOrder documents. Vendor assignment resolves to the mapped ThirdParty (type Supplier), expected delivery dates migrate as note fields, and received quantities are mapped to Dolibarr's reception tracking. Closed and open PO status maps directly to Dolibarr's status values.

Xentral outgoing invoices (AR) map to Dolibarr Facture documents with type = Customer. Document number and date preserve. Multi-currency amounts require exchange rate mapping at migration time; we use the historical rate from the invoice date or a configurable fallback rate. PDF invoice attachments migrate as Dolibarr linked files.

Xentral incoming invoices (AP) map to Dolibarr Facture documents with type = Supplier. We preserve vendor reference, date, amount, and currency. Multi-currency AP invoices require the same exchange rate resolution as AR invoices.

Xentral warehouse records and stock levels map to Dolibarr Entrepot and Stock objects. Real-time stock snapshots during migration require a freeze period (typically 24-48 hours coordinated with the customer) to prevent in-flight transactions from distorting the snapshot. Batch tracking fields vary by warehouse configuration; we flag any non-standard batch or serial setups during discovery and handle them as configuration-specific mapping tasks.

Xentral Projects map to Dolibarr Project records. Project-linked orders, invoices, and custom fields migrate with their associations preserved. Task dependencies and time entries (if tracked in Xentral) require separate mapping because Dolibarr's project task model differs structurally from Xentral's task hierarchy. We flag any complex project structures for manual post-migration review.

Xentral Delivery Notes map to Dolibarr Expedition documents. The parent order reference preserves, and line items map to the linked Product records. Delivery tracking information from Xentral migrates as expedition notes.

Xentral Credit Memos map to Dolibarr FactureAvoir documents. We preserve the reference to the original invoice for proper reversal linkage.

File attachments linked to orders, articles, and addresses are downloaded from Xentral and uploaded to Dolibarr with the original filename and association preserved. Dolibarr's file storage location and attachment module must be enabled in the destination instance.

Xentral custom field definitions on Articles, Addresses, and Projects are exported as field names and values. Values migrate as Dolibarr ExtraFields on the corresponding object. The destination Dolibarr instance must have the ExtraFields module enabled (self-hosted or DoliCloud Premium). We document the full custom field schema during discovery so that field definitions are created before data import begins.