Migrate from Sharp CRM to Odoo CRM

Sharp CRM Company records map directly to Odoo res.partner with is_company=True. We import Companies first so that subsequent Contact imports can resolve the parent company lookup. Company name, domain, address fields, phone, website, and any industry classification map to the corresponding res.partner fields. The company domain is used as a dedupe key during import.

Sharp CRM Contact records map to Odoo res.partner with is_company=False and parent_id pointing to the resolved Company record. Name, email, phone, job title, and address fields migrate directly. If Sharp CRM stores contact records with no linked company, we import them as standalone Contacts and flag for manual company assignment if needed post-migration.

Sharp CRM Deal records map to Odoo crm.lead with type='opportunity'. The deal name becomes crm.lead name, deal value maps to Odoo's expected_revenue field (or planned_revenue depending on Odoo version), and close date maps to date_deadline. We resolve the contact_id and partner_id lookups using the contact-company mapping from earlier phases.

Sharp CRM pipeline stages are per-account configuration with no standard export schema. During scoping we ask the customer to provide their current stage names and order, then build an explicit stage-mapping table to Odoo's crm.stage values. Stage probability percentages migrate from Sharp CRM to Odoo's probability field on each opportunity record.

Sharp CRM Tasks map to Odoo project.task records created under the CRM project's task types. Task title, due date, assignee (resolved via user email mapping), and status migrate directly. Any Sharp CRM Tasks linked to a specific Contact or Deal resolve the project.task parent_id and crm_lead_id references at migration time.

Sharp CRM call Activities map to Odoo crm.phonecall if the CRM module is installed with the phonecall feature enabled. Call duration, disposition, and timestamp preserve. If crm.phonecall is not available in the target Odoo version, calls migrate as crm.lead activity log entries. The contact_id lookup resolves to the migrated res.partner record.

Sharp CRM email Activities migrate to Odoo mail.message records attached to the crm.lead via the mail.thread model. Email body and subject preserve as plain text; attachments migrate as ir.attachment records linked to the message. Email timestamps are preserved in message date for timeline ordering.

Sharp CRM Notes attached to Contacts or Companies migrate to Odoo note.note records. Note body migrates as the note content, and the related res.partner is set via res_id/res_model linking. If the migrated account uses Odoo's Chatter model on crm.lead instead, notes attach as internal message notes on the opportunity.

Sharp CRM custom fields are common given its industry-agnostic positioning (healthcare, real estate, financial services). We enumerate all custom fields during scoping, classify each by data type (text, number, date, picklist, checkbox), and map them individually to Odoo custom fields created via Settings > Technical > Custom Fields or via XML data migration. Any Sharp CRM custom field without a clear Odoo equivalent is flagged for the customer to resolve before import.

Sharp CRM tags on Contacts and Deals migrate to Odoo crm.tag records. Tags are stored as a many2many relation on crm.lead via crm.tag.rel. We export Sharp CRM tag names as crm.tag records, then create the many2many link rows during the opportunity import phase. If the target Odoo instance uses a different tagging model, we align with the customer's configuration during scoping.

Sharp CRM owners referenced on Contacts, Companies, and Deals map to Odoo res.users records by email address match. Any Sharp CRM owner without a matching Odoo User goes to a reconciliation queue for the customer's admin to provision before record import resumes. Active and inactive status preserves. Seat counts are re-evaluated post-migration against Odoo's per-user licensing.

File attachments associated with Sharp CRM Contacts or Deals export to a file store with the original filename preserved. During Odoo import, attachments link to the target record via res_model and res_id using the migrated record's external ID. Attachments exceeding Odoo's file size limits are flagged and handled per the customer's preference (link to cloud storage or exclude).