Migrate from Streak to Odoo CRM

Streak's Box is the primary CRM record, bundling the email thread, contact associations, stage history, and custom fields into one object. We split each Box into an Odoo crm.lead record. If the Box represents an unqualified prospect (early pipeline stage), it remains as an Odoo Lead. If the Box represents a qualified opportunity (later stage, associated with a known deal value), we convert it to an Opportunity in Odoo's CRM pipeline. We preserve the original Box ID as an external identifier (x_streak_box_id) on the Odoo crm.lead for traceability and re-import verification. The Box's stage history maps to Odoo's lead history tracking (mail.message records on the crm.lead) rather than a separate stage history table.

Streak Pipelines define the workflow stages a Box moves through. Each Odoo CRM pipeline is represented by a stage sequence on cdoo.crm.lead model. We create Odoo CRM stages that match Streak's pipeline stage names and ordering. If the source account has multiple Streak pipelines (one per product line or sales process), we replicate them as separate Odoo stage sequences within a single crm.lead pipeline or as separate CRM teams in Odoo. Stage probabilities from Streak (if configured) map to Odoo's probability field on crm.lead, and closed-won / closed-lost states map to the corresponding Odoo stage state.

Streak Contacts (pulled from Gmail and stored alongside Boxes) map to Odoo res.partner records. We extract contact name, email address, phone, company affiliation, and any custom contact properties. Gmail contact associations are preserved as a note on the res.partner record referencing the source Gmail contact ID. Companies associated with Streak Contacts map to separate res.partner records of type 'company' with individual contacts linked via the child_ids relationship. The primary contact on a Box becomes the res.partner record; additional shared contacts on the Box are created as separate res.partner records and linked to the Box's crm.lead via a many2many relation.

Streak Box-level tasks map to Odoo crm.lead tasks (crm.activity or ir.model.data tasks). Streak tasks are flat — no subtasks or dependencies — and lack date-based ordering. We map assignee, due date, task title, and completion status to Odoo's mail.activity model. If Odoo CRM is configured with the Tasks app enabled, Box tasks migrate to the Tasks module linked to the crm.lead record. We flag any Box tasks that reference a Gmail attachment (file stored in Gmail) for manual relinking post-migration because Gmail file IDs are not accessible outside the source Gmail account.

Streak Snippets are templated email text blocks with merge variables (e.g., {{contact.first_name}}). We export snippet content and merge variable syntax. Odoo uses Jinja-style template variables ({{object.partner_id.name}}) inside mail.template records. We map Streak snippet content to Odoo email templates, transforming merge field syntax from Streak's format to Odoo's format. Variable naming conventions differ between platforms, so we document the mapping table in the handoff deliverable. Note that Snippets are content templates only; they do not include scheduling or sequence logic, which resides in Streak's Mail Merge Campaign feature.

Streak Mail Merge campaigns store recipient lists, email templates, send history, and open/reply tracking data. We export campaign metadata (name, send date, send volume) and send logs as a CSV attachment to an Odoo note on the corresponding crm.lead records. Open tracking metrics and reply rates are Streak-specific; we import these as custom fields on crm.lead (x_streak_open_rate, x_streak_reply_rate) as reference data. Odoo does not have a native sales engagement cadence feature equivalent to Streak Mail Merge; the customer rebuilds outreach sequences in a dedicated sales engagement tool (such as Mailchimp, Lemlist, or Lavender) or through Odoo's email marketing module. We do not migrate Mail Merge sequences as code.

Streak Tags are flat labels applied to Boxes for filtering. We preserve all tag names and associations as Odoo crm.tag records linked to crm.lead via a many2many field. Tags with no associated Boxes are included as empty tag records for reconstruction in the destination. Odoo CRM's tag model is a simple shared tag pool across all leads, not per-pipeline like Streak, so we consolidate tags across pipelines during mapping.

Streak custom properties (dropdowns, text fields, dates, numbers, checkboxes) vary per pipeline and per Box. We discover the full property schema per pipeline during the discovery audit, then create equivalent custom fields in Odoo using Odoo Studio (or via XML data if a custom module is deployed). Odoo field types are mapped: Streak text -> char or text, Streak number -> float or integer, Streak date -> date, Streak checkbox -> boolean, Streak dropdown -> selection or many2one. Per-pipeline custom properties require per-pipeline Odoo field creation; if two pipelines share a custom property with the same name but different value sets (e.g., a dropdown with different options per pipeline), we map them to a single Odoo field with the superset of options and flag the discrepancy in the handoff document.

File attachments stored inside Box threads are referenced by Gmail file ID. We export the file URL, filename, size, and attachment date. File content download requires the source Gmail account to remain active and accessible. Attachments that originated from within the Gmail thread migrate as Odoo ir.attachment records linked to the corresponding crm.lead. We flag any Box attachments that were Gmail-native files (Google Drive links, Google Docs) as external URLs in a note field rather than downloadable files, since Google Drive file access requires OAuth tokens outside FlitStack AI scope.

Streak User records (email, name, role, permissions level) map to Odoo res.users. We resolve owners by email match. Shared pipeline access (Pro tier or above) maps to Odoo's internal user access controls — Odoo does not have a shared/private pipeline distinction at the same level as Streak; pipeline visibility is controlled at the record level via Odoo's access rights model. Any archived Streak users are created in Odoo as inactive users so their Box ownership records can be mapped without data loss.

Streak preserves the chronological stage changes a Box has moved through, including the date and owner at each stage. We extract this history as a set of mail.message records attached to the migrated crm.lead, with each message recording the old stage, new stage, date, and responsible user. This preserves the pipeline audit trail inside Odoo's native activity and message thread, allowing the customer's sales team to view the full stage history without leaving the crm.lead record.

Streak Enterprise tier includes custom roles and data validation rules. Odoo models access control through res.groups (security groups) assigned to modules. We extract Streak role definitions and permission scopes and map them to Odoo's nearest equivalent security groups (CRM / Sales / Administrator). Enterprise-specific data validation rules in Streak have no direct Odoo equivalent; we flag these as manual policy decisions for the customer's admin to implement in Odoo using domain filters on the crm.lead model or server actions.