Migrate from Copper to Odoo CRM

Copper People records map directly to Odoo Contact records. We map name, email, phone, address, and related company to Odoo's name, email, phone, street/city/state/country, and partner_id fields respectively. Copper's People-to-Company linkage is preserved by resolving the Company slug to the Odoo Partner record created in the preceding step. We store the original Copper person_id as an external reference field x_copper_id on the Contact for audit and deduplication. Custom fields on the People object map to Odoo custom fields created in Studio or via Python before import.

Copper Company records map to Odoo Partner records with is_company = True. The company name becomes the Partner name, domain becomes the website field, and address fields map to the Partner's contact address fields. Partners are created before People so that the partner_id reference is resolved at Contact insert time. Multi-address Company records in Copper (if present) map to Odoo's child Contact records under the parent Partner.

Copper Opportunities map to Odoo crm.lead records with type = opportunity. Pipeline stage name maps to Odoo's stage_id within the crm.team pipeline; probability percentage maps to Odoo's probability field. Expected revenue, close date, and loss reason migrate as is. Copper's opportunity-to-person linkage becomes the Odoo lead's partner_id (Contact/Partner reference). We resolve the original Copper person_id to the Odoo Contact's x_copper_id field during the transform step.

Copper Lead records (separate from People) map to Odoo crm.lead with type = lead. Lead status from Copper maps to Odoo's stage_id within the applicable crm.team pipeline. We preserve lead score, source, and any lead-specific custom fields as Odoo custom fields on crm.lead. If a Copper Lead already has a qualified status that the customer considers converted, we migrate it directly as a crm.lead with type = opportunity to skip the manual lead qualification step in Odoo.

Copper Pipelines (available on Basic+ plans) map to Odoo crm.team records, each with its own stage pipeline. Stage names, order, and probability percentages migrate as Odoo crm.stage records within the team. Copper's multiple-pipeline setup (Basic allows one, Professional allows multiple) maps to one crm.team per Copper pipeline. We configure crm.team member assignments by matching Copper pipeline members to Odoo User records by email during the Owner reconciliation step.

Copper custom fields on People, Companies, Opportunities, Leads, and Tasks are enumerated via the Custom Field Definitions API and mapped to Odoo custom fields. We inspect Odoo's ir.model.fields to check for naming conflicts before creation, and we use Odoo Studio to create fields with correct types (char, text, selection, float, date, datetime, many2one, etc.) matching the Copper field type. Fields that reference related records in Copper (e.g., a custom field pointing to a Company) are resolved at migration time to their Odoo Partner IDs before the custom field value is written.

Copper Tasks map to Odoo project.task records if the customer includes the Odoo Project app in scope. If Project is not in scope, Tasks map to Odoo crm.lead internal notes or a custom project.task model on the CRM-only database. We preserve status (stage in Odoo), due date, assignee (user_id), and related record linkage (Copper's related_person and related_company map to Odoo's x_copper_person_id and x_copper_company_id custom fields for traceability). Task priority maps to Odoo's priority field using Copper's priority values.

Copper Projects (available on Basic+ plans) map to Odoo project.project records. Each Copper Project's associated Tasks are mapped to project.task records under the corresponding Odoo project. If Odoo Project app is not in the destination subscription, we map Projects to a custom project.project model and flag the dependency clearly during scoping so the customer can add the app or accept the Project-less CRM mapping. We preserve project stage, description, and member assignments.

Copper Activity records (email, call, meeting, note types) map to Odoo mail.message records attached to the parent crm.lead, Partner, or Contact record via Odoo's model and res_id fields. Call activities with disposition and duration map to custom fields on mail.message. Meeting activities with start/end times and location map to Odoo's calendar.event model linked to the parent record. Note activities map to Odoo's internal note (mail.message with subtype = comment and no envelope). We preserve the original Copper activity timestamp as message_date for timeline ordering.

Copper Tags (flat labels on People, Companies, and Opportunities) map to Odoo crm.tag records. Odoo CRM uses a single tag object (crm.tag) that applies across Leads, Opportunities, and Accounts. We create the Odoo tag records first, then write the tag many2many relationship to each migrated record using the x_copper_tag_ids field or the standard tag_ids on crm.lead. If a Copper tag is used for segmentation that the customer wants to preserve as a CRM filter, we flag it for Odoo view configuration during the rebuild phase.

Copper attachments store files in Google Drive, not in Copper's own storage. We extract the Google Drive file metadata (file name, mime type, Drive folder path, share URL) from Copper during discovery and re-create ir.attachment records in Odoo pointing to the file's new location. If the customer migrates Google Drive files to Odoo's filestore, we handle the file transfer and update the attachment record's store_fname. If files remain in Google Drive, we write the original Drive share URL as a char field on the Odoo attachment so the link is preserved without requiring file re-upload. We flag this dependency during scoping so the customer can decide on the file strategy before migration.

Copper Owners referenced on People, Companies, Opportunities, and Tasks are resolved by email match against Odoo res.users. We build the owner mapping table during discovery, matching each distinct Copper owner to an Odoo user by email. Owners without a matching Odoo user are placed in a reconciliation queue for the customer's admin to provision before record import resumes, because OwnerId references are required on most Odoo CRM records and unresolved references block insert.

Copper Lead records carry a lead_status property that does not have a native Odoo equivalent because Odoo models unqualified prospects as Leads (type = lead) flowing through crm.stage pipeline stages rather than a separate status property. We map the Copper lead_status values to Odoo crm.stage names within the lead pipeline and preserve the original Copper lead_status in a custom field x_copper_lead_status__c on the crm.lead for audit and reporting continuity.