Migrate from ClinchPad to Odoo CRM

ClinchPad Leads map directly to Odoo CRM Lead records. We extract first name, last name, email, phone, company name, and source from the ClinchPad Lead export. Any ClinchPad custom text fields become Odoo custom fields on the crm.lead model, with manual field type configuration required in Odoo Studio post-migration. The ClinchPad Lead ID is preserved in a custom reference field for cross-system audit.

ClinchPad merges Deal data directly into the Lead record — deal value, expected close date, and pipeline stage live on the Lead object. We split these into Odoo Lead (contact fields) and Odoo Opportunity (deal fields) during transformation. The deal value maps to Odoo expected_revenue, expected_close_date maps to date_deadline, and ClinchPad stage name maps to Odoo stage_id within the configured pipeline. Leads without a ClinchPad deal value are created as Odoo Leads only and flagged for manual Opportunity creation.

ClinchPad Kanban column names (e.g., New, Contacted, Proposal, Won, Lost) map to Odoo CRM stage records within the default pipeline. We preserve the exact stage sequence as defined in ClinchPad. Stage probability percentages are set on each Odoo stage (e.g., New at 10%, Proposal at 50%, Won at 100%). Lost stages map to Odoo's lost_reason field on the opportunity. Multi-pipeline ClinchPad setups require Odoo to create additional CRM Teams or pipeline configurations, which we document as setup tasks for the customer's admin.

ClinchPad notes attached to a Lead migrate to Odoo CRM Lead internal notes as plain text entries. We preserve note body, creation timestamp, and author name if exposed via export. Odoo stores notes on the chatter thread of the Lead or Opportunity record rather than as a separate Notes object. Note volume per record in ClinchPad is typically low given the platform's minimal feature surface.

ClinchPad lead tags map to Odoo CRM tags on the tag_ids many2many field of crm.lead. Tags migrate as label strings; Odoo handles tag creation during import if they do not already exist. If Odoo does not have the CRM app installed, tags may not be available — we confirm Odoo module installation during scoping.

ClinchPad contact fields (name, email, phone, company, address) are extracted from the Lead record during transformation. If Odoo has the Contacts app installed alongside CRM, we optionally create Odoo Contact records and link them to the migrated Opportunities. The customer chooses during scoping whether to create separate Contact records or keep contact data on the Lead record, which is the default Odoo CRM behavior.

ClinchPad stores file attachments as external references — Dropbox links, Wufoo form attachments, or direct upload filenames. The CSV export does not include file bodies. We extract attachment filenames and URLs from the export, request the customer provide source storage access during scoping, and re-attach files to the corresponding Odoo Lead or Opportunity record via Odoo's ir.attachment model. Filename deduplication applies when multiple records share the same attachment name.

ClinchPad user accounts map to Odoo User records by matching email address. ClinchPad has a flat permission model with no granular roles, so ClinchPad users who own Leads and Deals map to Odoo User records that the customer's admin assigns to the appropriate Odoo access groups post-migration. We flag any ClinchPad owner that has no matching Odoo User for admin provisioning before record import.

ClinchPad custom text fields on leads migrate to Odoo custom fields on the crm.lead model. We define the field name, field type (Char, Text, Selection, or Boolean depending on the ClinchPad field content), and place it on the Lead form view. Odoo Studio is required to configure custom fields after migration; we provide the field definition XML as part of the migration package.

ClinchPad integrations (Mailchimp, Google Calendar, Dropbox, Wufoo) store connection tokens and configuration but not customer data. We do not migrate integration state. Connections must be re-established manually in Odoo using Odoo's native email marketing, calendar, and document management apps, or via the Odoo Apps store if equivalent functionality exists. We document each active ClinchPad integration for the customer's admin to reconfigure.

ClinchPad does not expose a structured activity log or task object via export. We cannot migrate activity history beyond notes and file attachments. The customer's admin sets up Odoo CRM activity tracking (Next Action Date, Log an Activity) after migration for forward-looking activity management.

ClinchPad Lead source field (e.g., Website, Referral, Trade Show) maps to Odoo CRM medium_id or a custom source field on the Lead record. We preserve the original source label as a string during migration. If Odoo's marketing campaign tracking is active, we optionally link source to campaign_id for attribution analysis.