Migrate from Onsite CRM to Odoo CRM

Onsite CRM Contact records map to Odoo res.partner with is_company=False. The email field maps to email, phone maps to phone, and the contact name maps to name. We use email as the deduplication key during import. If Onsite CRM stores a contact's associated Company as a lookup field, we resolve that reference after the Company phase completes and backfill partner_id on each Contact record.

Onsite CRM Company records map to Odoo res.partner with is_company=True and commercial_partner_id pointing to itself. Company name maps to name, domain maps to website, and address fields map to street, city, state, zip, country using Odoo's partner address fields. Company records import first because Contact records reference them via partner_id or commercial_partner_id.

Onsite CRM Deal records map to Odoo crm.lead. The deal name maps to name, deal value maps to planned_revenue, close date maps to date_deadline, and stage maps to stage_id via a stage lookup resolved against Odoo's crm.stage table. We preserve the original Onsite CRM deal ID in a custom field x_onsite_deal_id__c on the Odoo lead for audit and cross-reference.

Onsite CRM pipeline stages are extracted during scoping by requesting screenshots of the pipeline configuration from the customer. Each stage name maps to a crm.stage record within the appropriate crm.team. Probability percentages from Onsite CRM map to Odoo stage probability values. We create the stage records in Odoo before Deal import begins.

Onsite CRM call logs migrate to Odoo's crm.phone.call model if the Odoo CRM instance has the phone module active. The call direction (inbound/outbound) maps to direction, duration maps to duration, and the call notes map to description. If crm.phone.call is not available in the customer's Odoo edition, call logs migrate as mail.message records on the related crm.lead.

Onsite CRM email records migrate as mail.message entries attached to the relevant res.partner or crm.lead via model and res_id. The email subject becomes message_subject, body becomes body_html, and the email date becomes date. We reconstruct the email thread by matching message_id headers if available, otherwise import as standalone entries.

Onsite CRM SMS records migrate as mail.message with a note subtype and a custom x_onsite_sms__c flag to distinguish them from internal notes. SMS content and timestamp map to body and date respectively. We attach each message to the related partner or lead record using the same model-res_id pattern as email.

Onsite CRM meeting records and general notes map to mail.message entries with a note subtype and meeting subtype respectively. Meeting location and scheduled time migrate as body content if available. If the customer uses Odoo Project to track follow-up tasks derived from meetings, we create project.task records linked to the crm.lead with the meeting context preserved in the task description.

Onsite CRM task records map to Odoo project.task. Task name maps to name, due date maps to date_deadline, assignee maps to user_id via email resolution against res.users, and status maps to stage_id within the Odoo project. We import tasks into a dedicated CRM project or the default Odoo Tasks project depending on the customer's configuration.

Onsite CRM user records map to Odoo res.users via email match. The customer's Odoo admin provisions the destination users before migration begins. We reconcile Onsite CRM owner references against the provisioned user list and flag any owner without a matching Odoo user for admin provisioning. Active/inactive status maps from Onsite CRM to the Odoo active flag.

Onsite CRM tags applied to Contacts or Deals migrate as crm.tag records. Each tag name maps to a tag in Odoo's crm.tag table, and the tag-lead relationship migrates via crm.lead.tag_ids. If the customer's Onsite CRM uses a tagging taxonomy with hierarchical categories, we normalize it to flat tags in Odoo and document the taxonomy mapping for the admin.

Onsite CRM custom fields on Contact require manual scoping during discovery. We request screenshots of the Contact record layout to identify all visible custom fields. Each custom field is mapped to a corresponding custom field in Odoo created via Odoo Studio or ir.model.fields before Contact import. Field types (text, number, date, picklist) map to equivalent Odoo field types with appropriate column_index adjustments.

Custom fields on Onsite CRM Deals migrate to custom fields on crm.lead in Odoo. The same scoping process applies: we request screenshots of the Deal record layout, create the corresponding custom fields in Odoo before migration, and map values during the Deal import phase. Any custom field that has no Odoo equivalent is flagged for manual review and documented in the migration inventory.