Migrate from Sharpspring to Odoo CRM

SharpSpring Contacts map to res.partner records with partner_type='contact'. The email field maps directly; phone, mobile, and title fields translate to Odoo's phone, mobile, and title fields. SharpSpring contacts without an associated company create res.partner records with company_id=false. We preserve the SharpSpring contact's original create_date as partner__create_date__migration__ on a custom datetime field.

SharpSpring Companies map to res.partner records with partner_type='company'. Company name maps to the 'name' field; domain/website maps to website; industry, employee count, and annual revenue map to industry_id, employee_count, and revenue fields respectively. Odoo automatically generates child contact partners for employees when the company partner is created.

SharpSpring N:N contact-to-company associations require pre-processing. We designate one primary company per contact (most-recently-modified by default, configurable) as the company_id lookup. Secondary company associations are preserved as partner category tags or as a custom 'additional_companies' text field listing related company names and SharpSpring IDs.

SharpSpring Deals map to crm.lead records with type='opportunity'. Deal name becomes crm.lead name; amount maps to expected_revenue; expected_close_date maps to date_deadline. The SharpSpring deal owner resolves against Odoo users by email match; unmatched owners are assigned to a migration fallback user flagged in the audit log.

Each SharpSpring pipeline becomes a named crm.team in Odoo, with its own set of crm.stage records. Stage names map value-by-value; stage probability and forecast category are re-applied from Odoo's stage configuration. We deliver a stage-mapping CSV before the migration runs so your Odoo admin can pre-create the stage records with correct probability and kanban color values.

SharpSpring lifecycle_stage (Subscriber, Lead, MQL, SQL, Customer, Evangelist) has no native Odoo equivalent — Odoo uses the lead/opportunity type split. We create a custom selection field 'x_sharpspring_lifecycle_stage' on crm.lead and migrate the final lifecycle value. Original stage-change timestamps migrate as custom datetime fields for reporting continuity.

SharpSpring's numerical lead score migrates to 'x_sharpspring_lead_score' (integer field) on crm.lead. Note that Odoo's native predictive lead scoring operates on historical conversion data and will recalculate scores post-migration — the SharpSpring score is preserved as a reference field for comparison during the reconciliation period.

SharpSpring VisitorID and associated behavioral data (tracked pages, anonymous visitor records) migrate as custom fields on crm.lead: x_sharpspring_visitor_id (char), x_sharpspring_tracked_pages (text), x_sharpspring_first_visit_date (datetime). Odoo's geo-IP detection runs on new inbound leads after go-live — historical visitor records cannot be retroactively matched to Odoo's tracking.

SharpSpring email open/click events and sent email records attach to the crm.lead as mail.message records with message_type='email'. Original timestamps and SharpSpring campaign names are preserved in the message body. Email templates do not migrate — we export the template list as a JSON file for manual rebuild in Odoo Email Marketing.

SharpSpring logged calls map to crm.phonecall records linked to the crm.lead. SharpSpring meetings (with start/end times and attendees) map to calendar.event records in Odoo. Original owner resolved by email match against Odoo users; duration fields normalized to Odoo's decimal-hour format.

SharpSpring social notes (internal comments on records) migrate as mail.message records with message_type='comment' on the corresponding crm.lead. Rich-text formatting is preserved as HTML; plain-text fallback is applied where rendering is unsupported. Author attribution resolves by email match to Odoo users.

SharpSpring form submission data (form name, field values, submission timestamp) migrates as part of the crm.lead record. The form name is stored as x_sharpspring_form_name; field values are preserved in a custom text field x_sharpspring_form_fields as a JSON string. Landing pages and form builder configurations do not migrate — these are rebuilt in Odoo Website or Odoo Marketing.

SharpSpring Campaigns (marketing campaign containers for emails and automation) have no direct Odoo CRM equivalent. Campaign names migrate as crm.tag records for association; campaign membership is preserved as x_sharpspring_campaign on crm.lead. The campaign's automation logic (workflows, sequences) is exported as a JSON blueprint and must be rebuilt in Odoo's Action Server or Odoo Marketing.

SharpSpring Enterprise custom objects map to Odoo custom models created via a custom module. Relationships between custom objects and standard objects (contacts, deals) require junction table creation. We deliver the Odoo model definition (Python + XML) as part of the migration package so your Odoo developer can review and install it before the full migration runs.

SharpSpring users (assigned as deal owners, workflow executors) resolve against Odoo res.users by email match. Unmatched users are flagged in the pre-migration audit with a fallback assignment to a designated Odoo admin user. Active/inactive status is preserved; inactive SharpSpring users are created as Odoo users with active=false.