Migrate from crmConnect to Odoo CRM

crmConnect Contacts map directly to Odoo res.partner records with partner_type set to 'contact'. The crmConnect contact's email becomes the partner's email field (used as dedupe key), phone maps to phone, first name and last name concatenate from crmConnect's name field. We resolve crmConnect owner assignments to Odoo user records by email match; any unmatched owners go to a reconciliation queue for the customer's admin to provision before contact import begins.

crmConnect's one-pipeline-per-account model on Standard (or unlimited pipelines on Professional) requires Odoo configuration. For customers with a single crmConnect pipeline, we map it to Odoo's default crm.lead pipeline with stages renamed to match crmConnect stage names. For customers with multiple crmConnect pipelines, we configure multiple Odoo sales teams (crm.team) and assign pipeline visibility per team, or document the requirement for Odoo multi-database deployment if complete pipeline isolation is required. Probability percentages migrate from crmConnect to Odoo stage probability settings.

crmConnect Opportunities map to Odoo crm.lead records. The opportunity's name becomes the lead's name field, amount maps to planned_revenue, stage maps to stage_id (resolved against the pipeline stage configuration), and contact_id references the migrated res.partner. Expected_close_date migrates to date_deadline. Owner assignments resolve via email-to-user lookup against the Odoo user table.

crmConnect's Company records (if present as a separate object from Contacts) map to Odoo res.partner with partner_type = 'company'. Company name becomes the partner's name, website maps to website, and address fields map to street, city, state_id, country_id, and zip. We create the Company partner record before Contact records so that the child Contact records can reference parent_id on the Company partner.

crmConnect calendar events with sync to Google or Outlook migrate to Odoo calendar.event records. Event name, start datetime, end datetime, location, and attendee list migrate. Attendees resolve by email to migrated res.partner records. crmConnect's calendar-to-contact linkage migrates as calendar.attendee records pointing at the corresponding crm.lead or res.partner. Standard tier's single-calendar limit maps to one Odoo calendar; Professional's unlimited calendars map to multiple Odoo calendar.event records per user.

crmConnect email engagement records (send history, not the email content itself) migrate to Odoo mail.message records linked to the parent crm.lead or res.partner via model and res_id. The email subject becomes the message subject, body becomes the body, and date_sent maps to date. Note that crmConnect email templates do not migrate as templates; we document the template structure for manual Odoo email template recreation in mail.template.

crmConnect call engagements migrate to Odoo crm.phone.call records (available when Odoo CRM phone integration is enabled). Call duration, disposition, and timestamp migrate to the corresponding fields. The call links to the related crm.lead or res.partner by res_id. If crmConnect stores call recordings as URLs, these migrate to a custom Char field for manual link access in Odoo.

crmConnect meeting engagements with attendees and locations map to Odoo calendar.event records. Meeting title, description, start, end, and location migrate. Attendee email addresses resolve to migrated res.partner records via calendar.attendee. Meeting notes or agenda text migrate as the event description.

crmConnect notes migrate to Odoo note.record (if using Odoo Notes app) or as mail.message records with no email (internal note). The note body migrates as text, author resolves to the Odoo user matching the crmConnect owner email, and date imports as the note creation timestamp. Notes linked to specific Contacts or Opportunities resolve via res_id and model references.

crmConnect tasks migrate to Odoo project.task records. Task title, description, due date, status (open/closed), priority, and assignee resolve by email to the Odoo user table. Tasks linked to specific Contacts or Opportunities in crmConnect reference the migrated crm.lead or res.partner via project.task's relation fields. Recurring tasks document recurrence pattern for manual Odoo recurring task configuration.

crmConnect membership portal records and course enrollment records do not have a direct Odoo equivalent. We migrate membership status, enrollment dates, student name, and course name as custom fields on a dedicated Odoo custom object (created via Odoo Studio before migration). The membership portal structure and course hierarchy are documented as JSON for the customer's admin to reassemble in Odoo eLearning or custom modules post-migration.

crmConnect Professional e-commerce products (up to 6 on Professional tier) map to Odoo product.product records. Product name, price, SKU (if present), and description migrate. Product associations to Contacts (as order history) map to Odoo sale.order and sale.order.line records if the customer enables the Odoo Sales app. If Odoo Inventory app is enabled, product variants and stock locations configure during migration.

crmConnect Professional text-to-pay invoices migrate to Odoo account.move records (invoices) when the Odoo Accounting app is present. Invoice number, date, line items, amounts, and payment status migrate. Text-to-pay URL associations are documented as notes for Odoo payment provider reconfiguration (Odoo supports Stripe, PayPal, and SEPA direct debit as payment acquirers). Without Odoo Accounting, invoice data migrates as custom fields on a migrated Contact record for reference.

crmConnect contact tags and segment membership lists migrate to Odoo crm.tag records and crm.lead.tag.rel junction table entries. Tag names map directly. For segments that represent static contact lists, we create Odoo mailing.contact lists (if Odoo Mass Mailing is enabled) or document the list membership for manual Odoo list reconstruction.

crmConnect custom contact properties and custom opportunity properties do not have a documented schema endpoint, so we discover them during the export phase by reviewing the CSV column headers. Each discovered custom property is created as a custom field on res.partner (for contact properties) or crm.lead (for opportunity properties) via Odoo Studio before import. Field types are inferred from data values: numeric strings become Float or Integer fields, dates become Date fields, and text values become Char or Text fields.