Migrate from Sierra Interactive to Odoo CRM

Sierra Interactive leads map directly to Odoo crm.lead records. The crm.lead model serves double duty as both Lead and Opportunity depending on its stage value in Odoo's kanban pipeline — early stages are Leads, later stages are Opportunities. We preserve the Sierra Interactive lead ID as Source_System_ID__c for traceability.

Sierra Interactive companies map to Odoo res.partner records with the is_company flag set to True. In Odoo, a company partner exists separately from its contact persons; we create the company partner first, then link individual contacts via the parent_id field. The Sierra Interactive domain field maps to res.partner.website.

Individual contacts in Sierra Interactive migrate as res.partner records with is_company = False and a parent_id linking to the company res.partner. Phone, mobile, email, street, city, state, and zip fields map directly. Owner resolution happens by email match against Odoo res.users; contacts without a matched owner receive a fallback assignment.

Sierra Interactive deals migrate as crm.lead records in the Opportunity stage of your Odoo pipeline. The deal amount maps to planned_revenue, close date maps to date_deadline, and the deal stage maps to the corresponding Odoo crm.stage id. One deal per crm.lead record; multi-property deals create one lead per property.

Sierra Interactive Action Plans (automated email, text, ringless voicemail, and task sequences) have no direct Odoo CRM equivalent. Odoo handles follow-up activities via the planned-activities feature or Ir.actions.server records, but these must be configured from scratch. We export the full Action Plan definition — step order, delay, channel, and message template — as a structured JSON document your Odoo admin can use as a rebuild reference.

Sierra Interactive notes on leads and deals migrate as crm.lead.description plain-text notes. If your Odoo instance has the discuss module enabled, notes can also land as mail.message records with note subtype for threaded chatter on the record. Original note timestamps and author information are preserved in custom datetime fields.

Sierra Interactive saved searches store the search criteria a lead used on the agent's website. Odoo CRM has no native saved-search object. We create a Saved_Search_JSON__c Char field on crm.lead and store the serialized search criteria as a JSON string. Your team decides whether to surface this in the Odoo form view via Odoo Studio.

Saved listings in Sierra Interactive attach a property URL and metadata to a lead record. Odoo has no native property object for real estate. We map saved properties to Saved_Property_JSON__c (Long Text / Char) storing an array of property URLs and basic listing data from Sierra Interactive. Odoo Studio creates and labels this field before migration runs.

Sierra Interactive lead_source fields map to Odoo CRM's crm.lead source_id, which references utm.source records for campaign attribution. If a source value does not yet exist in Odoo, the migration process creates a matching utm.source record automatically. This preserves original lead attribution for ongoing campaign analysis and reporting inside Odoo.

Sierra Interactive tags migrate to Odoo crm.lead tag_ids (many2many to crm.tag). Tags that do not exist in Odoo are created automatically during migration. Tags on deals and contacts map to the corresponding crm.lead and res.partner records respectively. Any missing tags are created as new crm.tag entries during the import, maintaining your existing taxonomy.

Sierra Interactive webhook subscriptions (Add WebHook Subscription API endpoint) do not transfer to Odoo. Odoo handles inbound webhooks via incoming email servers, API endpoints on crm.lead, or Ir.config_parameter values. We document your active webhook endpoints so your Odoo developer can rebuild them as Odoo automation rules or API receivers.