Migrate from MarketSharp to Odoo CRM

MarketSharp Lead records map directly to Odoo crm.lead. The crm.lead.type field is set to 'lead' for inbound MarketSharp leads. All standard lead properties (name, email, phone, source, status) migrate as crm.lead fields. MarketSharp lead score migrates as a custom integer field on crm.lead since Odoo has no native lead scoring — the custom field is created via Odoo Studio before the full migration run.

MarketSharp leads that have advanced to an active deal stage migrate to Odoo crm.lead with type='opportunity'. The MarketSharp pipeline stage name maps to an Odoo crm.stage record scoped to the relevant crm.team. If multiple MarketSharp pipelines exist, each requires its own Odoo crm.team + stage sequence so stage pick-lists remain scoped correctly.

MarketSharp Contact records map to Odoo res.partner with type='contact'. The contact's linked Company in MarketSharp becomes res.partner.parent_id pointing to the corresponding company partner. Email, phone, mobile, job title, and address fields migrate as direct field equivalents using Odoo's standard address formatting (street, city, state, zip, country).

MarketSharp Company records map to Odoo res.partner with type='company'. Company name becomes res.partner.name, website migrates as website field, industry maps to a custom selection field or the built-in industry_id if available, and employee count stored as a custom Integer field. MarketSharp company hierarchies (parent/child) map to res.partner.parent_id on the child record.

MarketSharp Appointments have no native Odoo equivalent — they migrate as calendar.event records requiring the Odoo Calendar module to be installed. The appointment start/end datetime maps to calendar.event.start and calendar.event.stop. The salesperson (assigned_to) resolves to calendar.event.user_id via email match against Odoo internal users. The linked MarketSharp Lead or Contact resolves to calendar.event.res_id with model='crm.lead' or model='res.partner'.

MarketSharp Job records are a domain-specific object without a direct Odoo CRM equivalent. If the Odoo project.management module is active, Jobs map to project.project with name, partner_id (linked customer), and stage. If project management is not in scope, the job's key fields (status, products, crew, address) migrate as custom Char/Selection fields on the related crm.lead record so the data is preserved and accessible to the sales team.

MarketSharp custom lead fields (set via Settings > Custom Lead Fields) translate to Odoo custom fields on crm.lead. Each custom field requires creation in Odoo Studio before migration — selection-type custom fields in MarketSharp become selection fields in Odoo with the same value options preserved via value_mapping. The migration plan surfaces every custom field and its Odoo target type so the Odoo admin can pre-create the schema.

MarketSharp custom contact fields follow the same pattern as custom lead fields — they map to Odoo custom fields on res.partner. Boolean, date, integer, and text custom fields in MarketSharp translate to their Odoo counterparts (boolean, date, integer, char/text). The mapping plan includes a type-check pass to flag any MarketSharp field types that lack a direct Odoo equivalent and require a custom char field with structured value storage.

MarketSharp stores a salesperson assignment on each lead and appointment. FlitStack AI resolves MarketSharp owner IDs to Odoo res.users records by email match — if no matching Odoo user exists, the record is flagged before migration and assigned to a fallback user so no record lands without an owner. The fallback owner is configurable per migration plan.

MarketSharp file attachments on leads, contacts, or jobs are downloaded from MarketSharp's storage and re-uploaded as Odoo ir.attachment records linked to the corresponding crm.lead or res.partner via res_model and res_id. File size limits are respected per Odoo's attachment configuration. Inline images in MarketSharp notes are extracted and stored as ir.attachment with a relation to the note or description field on the target record.

MarketSharp lead source values (Google Ads, referral, walk-in, etc.) map to Odoo utm.source records. If the MarketSharp source value does not match an existing Odoo utm.source, a new utm.source record is created during migration with the original MarketSharp source label preserved. The utm.source_id on crm.lead carries the attribution forward for reporting in Odoo.

MarketSharp lead status values (New, Contacted, Qualified, etc.) map to Odoo crm.stage records. Each stage gets its own crm.stage entry scoped to the relevant crm.team. Probability values attached to MarketSharp stages migrate as stage_default_probability on the Odoo crm.stage record. If MarketSharp stages use custom probabilities, these are applied per stage during migration so deal forecasting in Odoo reflects the historical close probability.