Migrate from Centerpoint ERP to Dolibarr ERP

Centerpoint CRM Contacts map to Dolibarr Third party records (llx_societe) as the parent company/customer entity, with individual contacts migrated to llx_socpeople linked via fk_soc. We extract contact name, email, phone, address, and owner assignment from Centerpoint flat-file exports, normalize the country and state fields to Dolibarr's expected format, and preserve the original contact ID as a custom field for audit. Centerpoint contact types (customer, vendor, prospect) map to Dolibarr third-party types: CUSTOMER, SUPPLIER, and PROSPECT.

Centerpoint Leads are staged workflow records tracked separately from Contacts. We migrate them to Dolibarr Third parties with type PROSPECT. If the Lead contains individual contact data, it also gets a linked llx_socpeople record. We preserve the Lead status and workflow stage from Centerpoint in custom fields on the Dolibarr Third party so the customer's admin can re-route leads through a new Dolibarr workflow post-migration. The split between Lead-as-Thirdparty and Lead-as-Contact is configurable during scoping based on whether the customer wants a unified prospect pool or separate pipeline tracking.

Centerpoint Opportunities map to Dolibarr Commercial proposals (llx_propal) for active sales records. We transfer opportunity name, value, stage, probability, expected close date, and owner. Centerpoint's weighted and unweighted forecast values migrate as custom numeric fields since Dolibarr's native propal does not support dual forecast views. If the customer uses Dolibarr's Project module, opportunities with associated work orders or deliverable tracking can map to llx_projet with the opportunity value stored as a budget field.

Centerpoint Asset Management records (physical and digital assets with location and depreciation) map to Dolibarr Product records (llx_product) with the asset type classification. We preserve current value, depreciation method, location, and asset hierarchy as custom fields on the llx_product record. Dolibarr does not have a native depreciation engine for assets, so we flag this as a post-migration configuration item for the customer's admin to address via a community module or external depreciation tracking if required.

Centerpoint Work Orders (linked to assets, technician assignments, safety prerequisites, and status history) map to Dolibarr Project records with linked Task records for each work order line. The asset reference becomes a custom field on the Project. Technician assignments map to Dolibarr User references on Task. Safety prerequisites and status history migrate as task notes and custom status fields. We flag that Dolibarr's native project module does not have a separate work-order scheduling engine; the customer may need the Gantt module from Dolistore for visual scheduling.

Centerpoint HR Employee records map to Dolibarr User accounts. We extract first name, last name, email, department, role, and employment status from the flat-file export. Employee records contain sensitive PII that requires explicit customer authorization before migration. We extract via flat-file export only and do not handle payroll or benefits data as these are not standard Dolibarr HR module fields. Inactive employees from Centerpoint map to inactive Dolibarr users. We preserve the original employee ID as a custom field on the user record.

Centerpoint Purchasing records including line items and vendor associations map to Dolibarr Supplier Orders (llx_commande_fournisseur). We preserve vendor links via the vendor Third party (mapped from Centerpoint vendor records), line-item detail via llx_commandefournisseurdet, and PO status. Vendor names require value mapping if Centerpoint uses a vendor naming convention that differs from Dolibarr Third party names; we resolve this by matching on vendor email or creating a cross-reference table during the transform phase.

Centerpoint QHSE compliance records (safety incidents, audits, inspections) are industry-vertical configurations with schema that varies by customer. We review the customer's QHSE configuration during discovery and map available fields to Dolibarr Project records with custom fields, or to a community QHSE module from Dolistore if one matches the customer's regulatory framework. Where QHSE data cannot be mapped to a native Dolibarr object, we flag it for the customer's admin to review and manually transfer to the appropriate module post-migration.

Centerpoint Logistics module records (shipments, routes, carrier data) map to Dolibarr Shipment records (llx_expedition). We map shipment status, carrier, origin and destination addresses, and route information. Carrier names may require normalization if Centerpoint uses a carrier naming convention that differs from Dolibarr's standard carrier list. We flag this as a value-mapping step during the transform phase and present options: standardize to Dolibarr's carrier list or create custom carrier records.

Centerpoint CRM owners assigned to Contacts, Leads, and Opportunities map to Dolibarr User records. We resolve owners by email match during extraction. Any Centerpoint owner without a matching email in Dolibarr goes to a reconciliation queue for the customer's admin to provision the user account before record import resumes. Owner assignment migrates as a foreign key reference on the target object.

Centerpoint product catalog (if accessible via export) maps to Dolibarr Product records. We transfer product name, SKU, description, unit of measure, and pricing. Dolibarr's multi-price feature (different prices per customer type or tier) can accommodate Centerpoint's pricing tiers if the flat-file export includes tier-level pricing data. We flag any products with BOM (bill of materials) structures for manual review since Dolibarr's BOM module is a separate activation.

If Centerpoint CRM exports include quotes or proposals attached to Opportunities, these map to Dolibarr Commercial proposals (llx_propal) linked to the mapped Third party and Project. Quote line items map to llx_propaldet. We preserve quote date, expiration, status, and any attached PDF or document references. Dolibarr's native PDF generation template may differ from Centerpoint's; we flag template comparison as a post-migration admin task.