Migrate from CentraHub CRM to Odoo CRM

CentraHub Leads map directly to Odoo crm.lead records with type=lead. Lead source, status, owner assignment, and any lead-score custom fields migrate as fields on crm.lead. The Odoo lead create date is set to the original CentraHub creation timestamp. We resolve the owner by email lookup against Odoo res.users and flag any owner without a matching user in the reconciliation queue.

CentraHub Accounts map to Odoo res.partner records with is_company=True. The Account ID from CentraHub is preserved in a custom field centrahub_id__c on the Odoo partner record for audit traceability. Account is created before any Contact import so that the parent_partner_id lookup is satisfied at Contact insert time.

CentraHub Contacts map to Odoo res.partner records with is_company=False, linked to their parent Account via parent_id pointing to the Odoo res.partner created from the CentraHub Account. Contact name, email, phone, job title, and address fields map directly. We resolve the parent Account reference by matching the CentraHub account_id against the centrahub_id__c custom field we set on import.

CentraHub Deals map to Odoo crm.lead records with type=opportunity. The deal amount becomes crm.lead.planned_revenue, the close date becomes date_deadline, and the deal name becomes the Odoo lead name. We link each opportunity to its primary contact (res.partner) via partner_id and to its owning team via team_id resolved from the CentraHub pipeline assignment.

Each CentraHub deal pipeline maps to a separate Odoo crm.team (sales team), and the CentraHub stage names map to Odoo crm.stage records scoped to that team via team_id. Probability percentages from CentraHub stage settings migrate to stage sequence order and probability. If CentraHub has a single pipeline, we create one crm.team and map all stages within it.

CentraHub standalone Tasks map to Odoo project.task records created in a dedicated migration project (not attached to a sales opportunity). Task title, due date (date_deadline), priority, and status map directly. Custom task types and priority values are mapped via a value translation table built during scoping. Tasks linked to specific Accounts or Contacts in CentraHub carry the Odoo partner_id reference resolved via centrahub_id__c lookup.

CentraHub Appointments map to Odoo calendar.event records. Start datetime, end datetime, location, and description migrate directly. We normalize all timestamps to UTC before insert and flag any appointment with a start time more than 24 hours in the past that would fall outside Odoo's default calendar window. Attendee resolution links calendar.attendee records to Odoo res.partner records via email match.

CentraHub Activity records (calls, emails, notes) map to Odoo mail.message records with message_type set to email, phonecall, or comment respectively. The message body and timestamp migrate directly. We resolve the message's res_id and model using the CentraHub record type and ID: contacts and accounts resolve to res.partner, leads and deals resolve to crm.lead. Activity history is reconstructed by inserting mail.message in chronological order and verifying the chatter thread count matches the source record count.

CentraHub per-module custom fields (text, number, picklist, date, phone, email, website) map to Odoo custom fields created via Settings > Technical > Database Structure > Fields before migration begins. We extract the full CentraHub custom field schema per module during discovery, map each to an Odoo field type (char, float, selection, date, char, char, char respectively), and create the fields in Odoo before any data import. CentraHub's loose type enforcement means we validate all custom field values against the declared type and flag any record with a mismatched value before writing to Odoo.

CentraHub tags applied across objects migrate to Odoo crm.tag records (for lead/opportunity tags) or a custom tag field on res.partner for contact-level tags. We extract the full tag taxonomy from CentraHub, create matching tags in Odoo, and map tag applications via tag_ids on crm.lead or a custom partner_tags field on res.partner. Tags with no exact Odoo equivalent are held for the customer to resolve during acceptance testing.

CentraHub attachments are accessed via the CentraHub-Dropbox and CentraHub-Box pre-built connectors, which store files externally rather than inside the CentraHub database. We download attachment files to temporary storage, map each to its parent Odoo record (res.partner or crm.lead) via the Odoo ir.attachment API, and re-attach them post-import. Any attachment with no accessible URL (connector not active, file deleted from cloud storage) is logged with the CentraHub record reference for manual retrieval.

CentraHub email campaign records with historical send, open, and click data are exported as a structured JSON read-only inventory. Active campaign state (scheduled sends, active sequences, cadence rules) cannot migrate because Odoo Email Marketing requires reconfiguration of templates, audiences, and send schedules. We deliver a written campaign inventory listing every CentraHub campaign, its target audience segment, and its send history for the customer's admin to rebuild in Odoo Email Marketing or a dedicated platform.

CentraHub Workflows are stored as structured JSON with field-ID references (not field names), which break silently if any mapped field is renamed during migration. We export all workflow definitions as structured JSON during discovery and deliver them as a written inventory: trigger type, condition fields, condition operators, and actions. The customer's admin rebuilds these in Odoo Automated Actions (server actions triggered by on_create, on_write, or on_cron) or Odoo Studio workflows post-migration. This is outside standard migration scope.