Migrate from Centrium CRM to Odoo CRM

Centrium Contact records with no organization flag migrate directly to Odoo Contact. We map name fields (first_name, last_name), email address, phone number, address fields, and any custom fields stored on the contact record. Owner assignment maps to an Odoo User record resolved by email match. If the source contact has no email, we generate a placeholder and flag it for the customer's admin to complete post-migration.

Centrium Contact records marked with an organization flag are identified during preprocessing and split into two operations: first we create the Odoo Partner (res.partner) record with the company name, address, and organization-level custom fields; then we create the Odoo Contact record linked to that Partner with a child-contact relationship. The original Centrium contact email becomes the Partner's email if no other contact at that domain has been migrated yet. This split is the primary preprocessing step that can extend timelines for accounts with large organization lists.

Centrium Deals map to Odoo CRM Opportunities (crm.lead records with type = opportunity). The Centrium deal status (won/open/lost) maps to the nearest Odoo stage: won maps to Won, lost maps to Lost, and open maps to the first stage in the customer's Odoo pipeline. We preserve the deal name, amount, expected closing date, and associated contact/partner links. Note that Centrium's flat status does not carry intermediate stage history to Odoo; we flag this as a data completeness disclosure in the validation report.

Centrium uses a fixed three-status deal model. We configure an Odoo pipeline with at minimum a qualification stage, a proposal stage, and a negotiation stage, plus Won and Lost terminals. If the customer already has a multi-stage Odoo pipeline configured, we map the Centrium open status to the stage closest to mid-pipeline rather than the first stage. Stage probability percentages default to Odoo's standard values unless the customer provides historical win rates to calibrate.

Centrium Tasks map to Odoo Project Tasks. We transfer the task name, description, due date, assigned user (resolved by email match to Odoo User), and completion status. Open tasks migrate with their current state preserved. Closed tasks migrate with a Completed stage marker. Tasks linked to a specific Contact or Deal in Centrium carry the same Odoo record link in the destination.

Centrium Projects are lightweight containers for tasks and contacts. They map to Odoo Project records. We transfer the project name, associated tasks (via the task migration above), and the linked Contact/Partner records. Any project-level metadata beyond name and membership (such as project status or budget fields) requires Odoo Studio field creation before migration or is noted as a gap for manual post-migration entry.

Centrium Notes attached to contacts, deals, or projects migrate to Odoo internal notes on the equivalent record. We transfer the full note body and preserve the parent-object association (Contact, Partner, or Opportunity). Notes are not threaded in Centrium, and Odoo internal notes are flat, so no threading reconstruction is needed. Attachments within notes migrate as Odoo attachments linked to the same parent record.

Centrium custom fields store as property maps in the export. We extract the field definition and values per record during the extract phase. Before the import phase, we create the corresponding fields in Odoo using Odoo Studio (field name, type, and placement on the form view). Once the schema is deployed, we apply the values during the standard record import. Fields that have no Odoo equivalent (e.g., select options that exceed Odoo's picklist limits) are flagged for the customer's admin to resolve.

Centrium user records (name, email) map to Odoo User accounts resolved by email address. We extract every distinct user referenced on Contact, Deal, Task, and Project records. Users without a matching Odoo account are placed in a reconciliation queue for the customer's admin to provision before record import. Inactive source users migrate as inactive Odoo users so that historical assignment is preserved even if the user account is not reactivated.

Centrium stores file attachments against contacts, deals, and projects. Because Centrium exposes attachments through the UI but not through an API, we scope attachment retrieval during discovery. If the total attachment volume is accessible via the UI export, we include it in the migration. If the attachment volume exceeds the destination storage allocation, we flag this before cutover and recommend either purchasing Odoo storage or archiving attachments externally. Odoo Enterprise includes dedicated document management; Odoo Community relies on file system storage which may have hosting-provider limits.

Centrium's team-level permission model has no granular RBAC equivalent and does not map to Odoo's access rights and record rules. We set all migrated records to be owned by the importing admin account. The customer's Odoo admin rebuilds access groups and record rules post-migration using Odoo's native access control interface. This is documented as a manual post-migration step in the handoff report.

Centrium reports are pre-built summary views generated on-demand and are not stored as exportable data objects. We do not migrate historical report outputs. Reporting must be rebuilt in Odoo using its native reporting and dashboard tools (available from the Starter app). We deliver a written list of the Centrium report names and their approximate data sources so the customer's admin can reconstruct them in Odoo.