Migrate from Convertkit to Odoo CRM

ConvertKit Subscribers map directly to Odoo crm.lead records. Both represent a person record with name, email, and metadata. The migration creates one crm.lead per subscriber. ConvertKit does not distinguish between leads and opportunities — all subscribers enter Odoo as leads; your team converts them manually or via Odoo's Lead to Opportunity wizard.

ConvertKit custom fields (up to 140 per account) require Odoo custom fields on crm.lead, created before migration via Settings > Technical > Models. Text fields map to Char or Text in Odoo. Number fields map to Float or Integer. Date fields map to Date. Checkbox-style fields map to Boolean. Pick-list fields in ConvertKit map to Odoo Selection fields with value-by-value mapping. The ConvertKit field system_name (e.g., ck_field_1_last_name) must be translated to Odoo's alphanumeric field name convention.

ConvertKit tags apply N:M to subscribers — one subscriber can have N tags. Odoo has no native N:M tagging model for CRM leads. We store tags as a custom field on crm.lead (Tags__c as Char or Text, storing comma-separated values). For large tag sets (>50 distinct tags), we recommend collapsing into a Category pick-list on the Odoo side during schema setup — your admin defines the category taxonomy before migration so tags route into controlled values rather than free-text.

ConvertKit form submissions create or update a subscriber with a form_id reference and opt-in state. We preserve form name and form_id as custom Char fields on the resulting crm.lead. The opt-in consent flag migrates as a Boolean custom field (Opted_In__c). Odoo's Website module can recreate form integrations — the form IDs serve as reference data for rebuilding Odoo Website forms post-migration.

ConvertKit sequences are multi-step email drip programs with delays, conditions, and content. Odoo CRM has no visual automation builder with the same semantics. We export sequence definitions (step order, delay, trigger conditions, email subject, and body) as a structured JSON reference document. Your Odoo admin uses this to rebuild the logic in Odoo's Automated Actions and Server Actions. The email content itself (subject, HTML body) is exportable separately for manual reformatting as Odoo email templates.

ConvertKit broadcasts are one-time email sends to a tag segment. Odoo Email Marketing (part of Odoo's marketing suite) handles campaign emails but is not part of the base CRM module. Broadcasts do not migrate — the email content can be exported as HTML, but the broadcast metadata (send date, recipient count, open/click stats) does not have a natural landing in Odoo crm.lead. We export a broadcast summary as a CSV reference file for post-migration reporting reconciliation.

ConvertKit stores per-subscriber engagement: emails_sent, emails_open_count, emails_click_count, and last_email_open_date. These values migrate as custom Number and Date fields on crm.lead (Emails_Sent__c, Email_Open_Count__c, Email_Click_Count__c, Last_Email_Open_Date__c). Odoo's native mail.tracking is event-based; historical ConvertKit open/click counts from before the migration are imported as bulk historical data rather than real-time events.

If ConvertKit stores products (digital goods, paid newsletters, courses), those migrate to Odoo product.product records. ConvertKit product names and prices map to product.product Name and list_price. The mapping handles the product-purchase association as a custom Many2many field on crm.lead or as a separate sale.order.line record depending on your post-migration sales process.

ConvertKit provides created_at and updated_at timestamps on every subscriber. Odoo's crm.lead.create_date is set at import time. We preserve the original created_at as Original_Create_Date__c (DateTime custom field) and updated_at as Original_Modify_Date__c for reporting continuity. This lets your team sort and filter leads by original acquisition date rather than migration-import date.

Each ConvertKit subscriber has a numeric id (e.g., 12840391). We store this as Source_System_ID__c on the crm.lead record. This serves two purposes: it prevents duplicate imports on delta runs (FlitStack checks Source_System_ID__c before inserting), and it enables cross-referencing Odoo leads back to their ConvertKit source records for audit purposes.

ConvertKit account-level settings (account name, timezone, default from-name) do not have an Odoo equivalent at the CRM level — they are account configuration rather than record data. We document them in the migration summary so your admin can set Odoo's company name, email alias, and timezone in Settings > General Settings after the migration completes.