Migrate from Click to Odoo CRM

Dynamics CRM Contacts migrate to Odoo res.partner records with partner_type = contact. We use email address as the dedupe key and preserve full name, phone, mobile, address fields, and any Contact-specific custom fields. The original Dynamics Contact ID is stored as a legacy_id field for audit trail. Company linkage is resolved by matching the parentcustomerid field to the Account migration.

Dynamics CRM Accounts migrate to Odoo res.partner records with partner_type = company. We map accountname to name, website, industrycode, numberofemployees, and annualrevenue. Company identification number and custom fields migrate as Odoo custom fields or ir.config_parameter values. This is created before Contact import so that the commercial_partner_id lookup is satisfied at Contact insert time.

Dynamics CRM Leads migrate to Odoo crm.lead. The leadsubject, leadsourcecode, description, estimatedvalue, and pipeline stage fields map to crm.lead fields. We preserve the original leadscore from ClickDimensions custom fields as a custom crm.lead field. Lead status (open, qualified, disqualified) maps to Odoo lead stage values. The lead-to-opportunity split is configurable: leads can remain as Odoo leads pending qualification or be converted during migration based on customer preference.

Dynamics CRM Opportunities migrate to Odoo crm.lead records with type = opportunity. The estimatedvalue maps to Odoo expected_revenue, closeprobability maps to probability, and closedate maps to date_deadline. Opportunity fields that have no direct Odoo equivalent become custom fields on crm.lead. Product line items from Dynamics migrate as crm.lead.line records or a separate sale order depending on whether the Odoo Sale app is active.

ClickDimensions Email Sends migrate to Odoo mail.message records linked to the relevant res.partner. We map send date, campaign name, email subject, and send status (sent, bounced, failed) to mail.message fields and custom fields on the record. Individual open and click events are stored as Odoo mail.tracking.value records or custom activity log fields. Email content bodies migrate as mail.message body HTML.

ClickDimensions Event Registrations migrate to Odoo event.registration records. We map registration name, email, session choices, registration date, and registration status (registered, attended, cancelled) to the Odoo event.registration fields. The associated Dynamics Contact resolves to the Odoo res.partner via email match. If Odoo Event app is not active, registrations migrate as custom fields on res.partner or a dedicated crm.lead tag.

ClickDimensions Web Tracking Events for known contacts (email-identified) migrate to Odoo as custom fields on res.partner recording last website visit, page views count, and campaign attribution. Anonymous visitor events are optionally migrated as aggregate statistics on the relevant marketing campaign record. The mapping depends on whether Odoo Website or Marketing app is active at the destination.

ClickDimensions Survey Responses migrate to Odoo survey.user_input records if the Odoo Survey app is active, with survey questions mapped to Odoo survey.question answers. Responses linked to known contacts attach to the corresponding res.partner. If Odoo Survey is not active, response data migrates as custom fields or a notes section on the res.partner record.

ClickDimensions custom field values migrate to Odoo custom fields created via Studio or model inheritance. We map the custom field name and data type to the closest Odoo field type (char, integer, float, date, boolean, selection). The Free Forever plan's 60-use write limit is checked during scoping; if the customer is on Free plan, we flag any overflow and advise on upgrade or manual population for excess records.

Dynamics CRM activities (tasks, phone calls, appointments, letters) migrate to Odoo mail.activity records linked to the relevant res.partner or crm.lead. Phone call duration and disposition map to custom activity fields; appointment start and end times map to Odoo activity date and duration. Activity status (open, completed, cancelled) maps to Odoo activity state.

Dynamics CRM Notes migrate to Odoo mail.message records with message_type = comment (internal note). The notebody text maps to the message body. Notes attached to specific records link via Odoo's res_id and res_model referencing the correct crm.lead or res.partner. File attachments on notes migrate as ir.attachment records linked to the same res_id and res_model.

Dynamics CRM Users referenced as record owners map to Odoo res.users by email address match. We extract distinct owner values from all migrating records during discovery and match against the destination Odoo instance's user list. Any owner without a matching Odoo user goes to a reconciliation queue for the customer's admin to provision before record import begins.