Migrate from Streak to Twenty CRM

Streak Boxes map to Twenty Opportunities. The Box name becomes Opportunity name, stage history (pipeline name and stage name at time of record creation) is preserved in custom fields, and owner assignment maps via email match to a Twenty User. Box ID is stored in a custom field streak_box_id__c for audit and cross-reference. Custom Box properties discovered per pipeline during schema audit are created as Twenty custom fields on Opportunity before import.

Streak Pipelines define the workflow a Box moves through. In Twenty, we create a custom picklist field (e.g., pipeline_name) on Opportunity to preserve the pipeline label, and use Twenty's workspace-level stage configuration to recreate stage names in the same order. For migrations with multiple pipelines, each pipeline becomes a distinct status group or a separate Opportunity filter view.

Streak Stage names and order are extracted per Pipeline. We configure Twenty's opportunity stage field with stage names matching Streak's sequence. If Twenty has fewer default stages than Streak, we add custom stage values via the API and map the remaining Streak stages to a closest-match custom field.

Streak Contacts (pulled from Gmail, stored alongside Boxes) map to Twenty Person records. Email address is the dedupe key. Name, company affiliation, and custom contact properties migrate. Gmail contact associations (which Gmail contacts are linked to a Box) are stored as a custom field on the Person record rather than as a live link since Gmail contacts do not exist in Twenty.

Box-level company associations in Streak map to Twenty Company records. We extract company name from the Box's company field and create or match a Twenty Company. The Person record is then linked to the Company via the standard relationship.

Streak Tasks are Box-level action items with assignees and due dates. They map directly to Twenty Tasks linked to the corresponding Opportunity. Streak tasks are flat with no subtasks or dependencies, which matches Twenty's task model. Due date, assignee (via email-to-User match), and task body migrate.

Streak Tags are flat labels applied to Boxes. We export all tag names and associations. Tags with no associated Boxes are included as a label list for reference. In Twenty, we create a custom text or multi-select field on Opportunity to hold tag values, or document them as a filter-view definition for the customer's admin to implement.

Mail merge campaigns store recipient lists, templates, send history, and open/reply tracking. We extract campaign metadata (name, send date, recipient count, open rate, reply rate) and export the template content and recipient list. Open tracking metrics are Streak-specific and have no direct Twenty equivalent. We deliver a written campaign inventory with template body and recipient list for manual or scripted reconstruction using a third-party email tool integrated via Twenty's API.

Snippets are templated text blocks with merge variables used inside Gmail. We export snippet content and variable syntax as a written inventory. Merge variable naming conventions differ between Streak and any third-party replacement tool, so we document the original variable names alongside a recommended replacement syntax. Snippets do not function inside Twenty without a third-party email integration.

Custom properties added to Boxes (dropdowns, text, dates, numbers, checkboxes) vary per pipeline. We discover the full property schema per pipeline during the schema audit phase, create matching custom fields in Twenty (with correct type mapping), then import property values as part of the Box-to-Opportunity migration. Properties that reference other Boxes are mapped to the corresponding Opportunity records.

File attachments inside Streak Box threads are stored by Gmail file ID. We export the file URL, filename, size, and attachment date as a written inventory. File content retrieval requires the source Gmail account to remain active and accessible; we document the file reference list and recommend the customer's admin validate and re-upload files to Twenty or a connected storage system post-migration.

Streak Users with email, name, role, and permissions level are mapped to Twenty Users by email. Shared pipeline access depends on Streak Pro tier or above; we verify each owner's plan tier during scoping. Any archived Streak users (Pro+ feature) are flagged in a separate reconciliation queue and must be reactivated before their Box records are accessible for export.