Migrate from Contlo to Odoo CRM

Contlo Contacts map to Odoo res.partner (qualified customers and companies) and crm.lead (unqualified prospects). We apply a split rule based on Contlo lifecycle and engagement data: Contacts with high engagement scores and recent campaign interactions become Odoo crm.lead records; Contacts that are established buyers or have deal history become res.partner attached to a parent company record. The split rule is defined during scoping and applied as the first transformation step. All original Contlo contact properties migrate as custom fields on both objects for audit traceability.

Contlo Segments are behavioral groupings used to target automations. We preserve segment membership as Odoo res.partner tags (ir.model.data records linked via res.partner.category) on the Contact migration. Segment names and member counts are preserved as tag labels. Segment rule logic (AND/OR conditions, behavioral filters) is extracted as structured data in the written automation inventory for the customer to rebuild as Odoo server actions or CRM stage triggers.

Contlo Companies map to Odoo res.partner with company_type = company. The Contlo company domain becomes the Website field on res.partner and is used as the dedupe key during import. Parent-child company relationships in Contlo map to Odoo's parent_id reference on res.partner. Company is created before any Contact import so that the partner_id Lookups are satisfied at Contact insert time.

Contlo Email and SMS campaigns map to Odoo mass.mailing records. Campaign name, subject, sender identity, and body content migrate as mailing.mailing fields (subject, body_html, mailing_model_id). Campaign delivery statistics (sent, delivered, opened, clicked, bounced) migrate as mailing.trace records linked to the recipient partner or lead. SMS campaign content migrates separately with mailing.mailing.mailing_type = sms.

Contlo automations are event-triggered flows with conditional branching, time delays, and multi-step actions. Odoo CRM uses stage-based workflows and server actions. We extract the full automation graph as structured data including trigger type, conditions, action steps, and branch logic. This becomes the written automation inventory delivered to the customer for manual rebuild in Odoo Studio or via custom module development. We do not migrate automations as executable code because the event models differ structurally.

Contlo email engagement records (opens, clicks, replies) map to Odoo mail.message records linked to the recipient res.partner or crm.lead via the res_id and model fields. Email content bodies migrate as mail.message body HTML. The original engagement timestamp preserves activity ordering in the Odoo chatter timeline.

Contlo call engagement records map to Odoo crm.phone.call if the Odoo CRM installation includes the crm_phone module (available in Odoo Apps). Call duration, disposition, and recording URL migrate to the corresponding crm.phone.call fields. If crm.phone.call is not installed, calls migrate as note records attached to the Contact for timeline visibility.

Contlo meeting engagements map to Odoo calendar.event records. Start time, end time, location, and description migrate directly. Attendee relationships map to calendar.attendee records linked to the res.partner or crm.lead participants.

Contlo task engagements map to Odoo project.task records (if project management is in scope) or CRM tasks attached to crm.lead. Task status, priority, due date, and description migrate. Task assignment in Contlo maps to Odoo user_id on the task record via email-based owner resolution.

Contlo notes migrate to Odoo mail.message records with message_type = notification and subtype = note. Note content and timestamp preserve. Notes are linked to the parent res.partner or crm.lead via res_id and model for full chatter timeline visibility.

Contlo custom fields on Contacts and Segments migrate as Odoo custom fields created via Odoo Studio or XML before data migration begins. We map Contlo field types to Odoo field types: text properties become char or text, numeric properties become float or integer, date properties become date, and multi-select behaviors become many2many or selection fields. All custom fields are created with appropriate validation rules before any records are imported.

Contlo's brand-owned generative AI Model is trained on the customer's campaign content and behavioral data within Contlo's infrastructure. This model is a proprietary artifact that cannot be exported as a portable data object. We document the AI Model configuration in the migration handoff as an explicit action item for the customer to re-train or recreate in the destination system. This is not a data gap; it is a platform-specific capability that requires manual rebuild.

Contlo event-level analytics (opens, clicks, conversions, unsubscribes) migrate as Odoo mailing.trace records linked to the corresponding mailing.mailing and recipient res.partner or crm.lead. We preserve event timestamps for reporting continuity. Conversion event data (purchase events, form submissions) migrates as custom stat records attached to the Contact if Odoo's standard analytics do not cover the specific event type.