Migrate from Centerpoint ERP to Odoo ERP

Centerpoint CRM Contacts map to Odoo res.partner records filtered to customer=True. The contact's name, email, phone, address, and owner assignment migrate as typed fields. We deduplicate by email match against existing Odoo partners. Any HubSpot or external ID stored in Centerpoint is preserved in a custom char field for audit traceability. The CRM module owner assignment resolves to an Odoo res.users record by email lookup; unresolvable owners are flagged for admin provisioning before the Contact phase runs.

Centerpoint Leads map to Odoo crm.lead records with type='lead'. The staged workflow from Centerpoint (initial lead through opportunity realization) maps to Odoo CRM stage IDs via a named-stage lookup table built during scoping. Lead priority and assigned owner migrate directly. We treat Centerpoint Leads and Contacts as distinct migrations since the crm.lead model separates prospects (type='lead') from opportunities (type='opportunity') within one object.

Centerpoint Opportunities map to Odoo crm.lead records with type='opportunity', linked to the partner_id resolved from the associated Contact or Company. The Centerpoint deal value and probability migrate to Odoo's expected_revenue and probability fields. Both weighted and unweighted forecast values from Centerpoint are preserved as custom float fields since Odoo's standard expected_revenue model defaults to one view; the customer chooses which becomes the standard field during scoping. Stage mapping uses the same named-stage table as Leads, applied per pipeline.

Centerpoint Asset Management module records map to Odoo's account.asset model. Physical asset name, location, current value, and depreciation schedule transfer directly. Asset hierarchy from Centerpoint (parent-child relationships) maps to Odoo's parent_id on account.asset where the destination has the Enterprise asset_management module enabled; Community edition requires custom fields or a third-party module for hierarchy. Asset category assignments map to Odoo asset category records created during schema setup.

Centerpoint Maintenance Work Orders map to Odoo's maintenance module (maintenance.request). Technician assignments, safety prerequisites, asset link (via equipment_id), and full status history migrate. The Centerpoint work-order number becomes the Odoo request's name for traceability. Odoo's maintenance module supports scheduled and corrective maintenance; if Centerpoint work orders include preventive scheduling data, we map them to maintenance.calendar with recurring rules as custom fields rather than native calendar recurrence.

Centerpoint HR Employee records map to Odoo hr.employee. Department and role assignments migrate to Odoo's department_id and job_id. Employee records contain PII (national ID, compensation details, personal contact info) that requires explicit customer authorization before extraction and ingestion. We extract via flat-file export from Centerpoint, validate field completeness, and map to Odoo's typed hr.employee fields. The migration user is granted HR-specific field access during ingestion to comply with data-handling authorization.

Centerpoint Purchasing Purchase Orders map to Odoo purchase.order with vendor name resolved to res.partner (vendor=True). Line items, quantities, and unit costs transfer to purchase.order.line with Odoo product_uom resolution. Vendor names from Centerpoint may require value mapping if the source uses abbreviated or inconsistent vendor naming conventions; we build a vendor normalization table during data audit. PO status (draft, sent, received, cancelled) maps to Odoo's state field using a status lookup table.

Centerpoint QHSE compliance records (safety incidents, audits, inspections, regulatory reports) have no direct Odoo equivalent in the standard Community edition. We map these to Odoo's quality module if the Enterprise quality app is licensed, or to custom fields on a dedicated project.task or stock.productionlot record type during migration. The schema varies by industry vertical and Centerpoint configuration, so we review the customer's QHSE configuration during discovery, define a custom Odoo model, and migrate records with field-by-field mapping to the closest typed destination. Odoo Enterprise Quality app customers get safety checks, quality alerts, and control points mapped from the source QHSE record types.

Centerpoint Logistics module shipment records, routes, and carrier assignments map to Odoo stock.picking operations. Carrier names may require normalization if Odoo uses a different carrier vocabulary; we build a carrier mapping table during data audit. Route assignments from Centerpoint map to Odoo stock.location routing rules. Delivery status and timestamps migrate as typed fields on stock.picking. If the customer uses Odoo's delivery module with carrier integration, carrier names normalize to the integration's expected carrier codes.

Centerpoint QHSE module stores configuration records (inspection templates, compliance checklists, regulatory categories) that vary by industry vertical. We treat these as configuration records rather than transaction data, migrating them to Odoo's quality module as quality.point and quality.alert records if the Enterprise quality app is installed, or as notes and custom fields on a dedicated Odoo model if Community edition is deployed. The customer confirms which QHSE record types are active during scoping, as Odoo's Community edition does not ship a native QHSE or EHS module.