Migrate from InStream to Odoo CRM

InStream Contacts map to Odoo CRM crm.lead for unqualified prospects and res.partner for known companies and individuals. We evaluate each Contact's company association and activity history during migration: Contacts with an associated Company record that have not entered a pipeline stage become Odoo crm.lead records; Contacts associated with active Deals or that represent known company representatives become res.partner records. The original InStream contact ID is preserved in a custom field x_instream_id on both the lead and partner for audit trail. Email, phone, social profile URLs, notes, and all standard InStream contact fields map to typed Odoo fields.

InStream Company records map directly to Odoo res.partner with partner_type set to 'company'. The InStream company name becomes res.partner.name, website maps to website, and any phone or address fields map to Odoo's address fields. The company record is created before any related Contact import so that the partner_id lookup is satisfied at insert time. InStream's free-text company industry and employee count fields map to custom fields x_instream_industry and x_instream_employee_count on res.partner.

InStream Deals map to Odoo crm.lead with type='opportunity'. The deal value maps to expected_revenue on the Odoo opportunity. The InStream contact association becomes crm.lead.partner_id (a res.partner lookup). We resolve the partner_id reference during migration by matching the InStream contact email to the migrated res.partner record. Any InStream Deal without a linked Contact is flagged for manual review before import.

InStream pipeline stages are free-text and not normalized across accounts. We capture the stage name-to-order mapping during discovery and create corresponding crm.stage records in Odoo CRM with the same display name, sequence order, and probability percentage. Probability is derived from the InStream stage's historical close rate if data is available, or assigned by the customer during scoping. Each stage is created in Odoo before Deals are imported so that stage_id references are satisfied at insert time.

InStream Lists are Contact groupings for segmentation. We migrate each List as an Odoo CRM Tag (ir.model.data / crm.tag). List membership maps to crm.lead.tag_ids and res.partner.category_id so that the original segmentation is preserved in the destination. Customers on InStream's paid tiers who use multiple Lists per Contact will see all original List memberships reflected as separate tag entries in Odoo. We extract the full List membership matrix during discovery to ensure no membership is silently dropped.

InStream email history attached to Contacts migrates to Odoo's mail.message records on the crm.lead or res.partner chatter thread. Email body content, sender, recipient, and timestamp migrate to mail.message fields body, email_from, email_to, and date. We resolve the parent record (crm.lead or res.partner) by matching the InStream contact email to the migrated record's email field before inserting messages.

InStream call engagements map to Odoo mail.message records with subtype set to 'crm.mt_lead_create' or a custom call subtype, with the call duration and disposition stored in custom fields on the message. Activity timestamp maps to mail.message.date to preserve the original call ordering in the record's chatter.

InStream meeting records (with title, start time, end time, location, and attendees) map to Odoo calendar.event. We resolve the attendee list by matching attendee email addresses against the migrated crm.lead and res.partner records to create calendar.attendee records linked to the event. Meeting body or notes migrate as a mail.message on the related crm.lead or res.partner.

InStream notes attached to Contacts and Companies migrate as Odoo mail.message records with message_type='comment' on the related crm.lead or res.partner. The note body migrates as plain text in mail.message.body. Notes without a parent record are attached to the related Company partner record.

InStream tags on Contact records migrate to Odoo crm.tag entries on crm.lead and res.partner. We extract the full tag vocabulary during discovery, deduplicate any synonyms (a tag called 'Enterprise' and another called 'enterprise' are treated as the same tag in Odoo), and create the tag records before the Contact-to-lead migration phase.

InStream custom fields have no publicly documented schema via API. We extract available field definitions from the InStream UI export during discovery, cross-reference them against Odoo's field types (char, text, integer, float, date, datetime, selection, many2one, many2many), and create equivalent custom fields on the crm.lead model via Odoo Studio before migration begins. Any fields that cannot be typed from the UI export are flagged in the discovery report for manual definition by the customer's admin.

InStream Owner references on Contact, Company, and Deal records map to Odoo res.users by email match. We extract every distinct Owner email during discovery and match against the destination Odoo instance's user table. Owners without a matching Odoo User go to a reconciliation queue for the customer's admin to provision before record import resumes. User provisioning is outside migration scope.