Migrate from Close to Odoo CRM

Close Leads map directly to Odoo CRM crm.lead records. Standard fields — name, email, phone, company name, status, owner — migrate 1:1. Close lead status labels (e.g. Potential, Contacted) map to Odoo stage names that we configure to match the source labels. The Odoo lead ID is generated at insert and is used as a parent reference for activity logs. Note that Odoo has no separate Contact object until a Lead is converted; contacts remain as partner_id fields on the Lead until the convert action is taken.

Close Contacts attached to a Company map to Odoo CRM Contacts (res.partner records with customer_rank set). Because Odoo does not maintain separate Contact and Lead records simultaneously, we stage Contacts as Lead records with a flag (e.g., is_contact__c) and convert them at migration time or post-migration using Odoo's lead-convert action, which creates the linked Contact and Opportunity. This approach preserves the relationship between Contact and Company that Close maintains explicitly.

Close Opportunities map to Odoo CRM Opportunities (crm.lead records with type='opportunity'). The Close opportunity value, expected close date, stage, and probability migrate to Odoo expected_revenue, date_deadline, stage_id, and probability fields. Each Close Pipeline becomes an Odoo CRM Pipeline (crm.team), and pipeline stages map to Odoo stage records with probability weights preserved from the source.

Close Pipelines map to Odoo CRM Teams. We create the Odoo team record first, then map each pipeline stage as an Odoo stage within that team's pipeline. Stage names and display order are preserved. Close pipeline custom columns carrying Opportunity-level data migrate as Opportunity custom fields in Odoo.

Close pipeline stages map to Odoo CRM stage records. Each stage carries a name, sequence order, and probability percentage. We create these in Odoo during schema setup using the Odoo RPC API, setting the probability to match the Close stage probability value. Stage loss and won flags map from Close pipeline stage behaviour.

Close activity records (calls, emails, SMS, tasks) migrate as Odoo mail.message and mail.tracking.value records attached to the corresponding Odoo crm.lead. Odoo stores these as Log a Note or Log an Activity on the lead. We map the Close activity type to Odoo's mail.message subtype (comment, email, call, sms) and set create_date to the original Close timestamp to preserve timeline ordering. This requires JSON export from Close because CSV exports silently omit activity data.

Close Custom Fields on Lead, Contact, and Opportunity map to Odoo custom fields created via Odoo Studio or the res.config.settings API. We read the Close field definition (type, choices, required flag) via the Close API and create matching Odoo fields of equivalent type before importing any records. Picklist choices become selection fields or many2one relations depending on cardinality. Required flags are set on the Odoo field definition.

Close Custom Activities require a three-phase migration: first we create the Odoo mail.message subtype that represents the custom activity type, then we create any type-scoped custom fields in Odoo, then we import activity instances linked to the subtype. The parent type must exist before any custom field scoped to it, and both must exist before activity records can be inserted. We sequence this as a dependency chain during the schema phase.

Close Custom Objects migrate to Odoo custom models created via the Odoo ORM. We pre-create the custom model with the matching API name (e.g., x_close_custom_object), add all custom fields with their types, create any many2one lookup relationships to standard Odoo models (crm.lead, res.partner), and then import the data. Custom object records are migrated last in the import sequence because they often reference Leads, Contacts, and Opportunities.

Attachments on Close Leads and Contacts are downloaded via the Close API as binary files and uploaded to Odoo as ir.attachment records linked to the corresponding crm.lead or res.partner record. The original filename, MIME type, and file content are preserved. Any attachment metadata (description, tags) migrates as attachment description fields.

Close call recordings are retrieved as audio files via the Close API and uploaded to Odoo as ir.attachment records attached to the matching call log (mail.message) on the crm.lead. The audio file format (typically MP3 or WAV) is preserved. Retention metadata from Close migrates to the attachment description.

Close Smart Views are named saved searches scoped to the Leads tab. We export the filter configuration (field conditions, operators, values) from the Close API and deliver it as a written inventory of saved search definitions for the customer's Odoo admin to recreate as Odoo Filters. Smart Views cannot be exported and re-imported into Odoo; manual recreation in the Odoo UI is required. The Contacts-tab-only limitation in Close means we validate all Smart Views via API before planning the export.

Close Users map to Odoo res.users records. We resolve by email match. Any Close User without a matching Odoo User goes to a reconciliation queue for the customer's Odoo admin to provision before record import proceeds. Permissions, role-based access control, and team membership do not migrate; Odoo admin configures these post-migration in Settings > Users.