Migrate from Streak to Pipedrive

Streak Boxes map directly to Pipedrive Deals. The Box name becomes Deal title, Box owner maps to Deal owner by email match, Box stage maps to a Pipedrive Stage within a configured Pipeline, and Box creation and modification timestamps migrate as Deal open_date and update_time. Box-thread associations (the Gmail thread ID Streak uses to link a Box to an email conversation) are preserved as a custom text field thread_id__c on the Deal for re-association in Pipedrive's Gmail add-in if desired.

Streak Pipelines map to Pipedrive Pipelines. We extract pipeline name, stage order, and stage-specific fields during schema discovery. Pipedrive pipelines support multiple parallel pipelines per account, which mirrors Streak's multi-pipeline model. Stage names map by position; if Streak uses stages named 'Demo Done' and Pipedrive uses 'Proposal Sent', we map by order rather than by name and flag the customer to confirm stage name alignment before import.

Streak Stages within a Pipeline map to Pipedrive Stages within the corresponding Pipeline. Stage order and probability percentages (if set in Streak) migrate to Pipedrive Stage probability. Pipedrive Stage order is configurable post-migration in the Pipeline settings, so we set the initial order from Streak and document any customer-requested reordering as a post-migration configuration step.

Streak Contacts map to Pipedrive People. We extract name, email address, phone, company affiliation, and any custom contact properties. Streak stores Gmail contact associations; we preserve the email address as the dedupe key and link the Person to an Organization (Company) if the Streak Contact has a company field. People without an Organization map as standalone Persons in Pipedrive.

Streak Contacts with a company affiliation require a two-step import: Organizations first, then People with OrganizationId resolved. We extract unique company names from Streak Contacts during the pre-migration audit, create Organizations in Pipedrive, then import People with the OrganizationId lookup satisfied from the Organization creation pass. Circular dependencies (Contact with company, Company with a Contact as the primary) are resolved by creating the Organization with a placeholder primary and updating after People load.

Streak Box Tasks map to Pipedrive Activities (type Task). Task subject, assignee (owner), due date, and completion status migrate. Streak tasks are flat with no subtasks or dependencies; Pipedrive activities follow the same flat model, so no transformation is needed. Activity assignment maps by owner email match to Pipedrive User.

Streak Tags applied to Boxes migrate to Pipedrive Labels on Deals. Tags are a flat label system in Streak; Labels are a flat label system in Pipedrive, so the mapping is direct. We export all tag names and the Box IDs each tag is attached to, then map those associations to Deal labels during Deal import. Tags with no attached Boxes are included as an empty label list for reconstruction if needed.

Streak custom properties added to Boxes (dropdowns, text fields, dates, numbers, checkboxes) vary per Pipeline and per Box. We discover the full property schema per Pipeline during the schema audit, then map each property to a Pipedrive custom Deal field of the matching type. Pipedrive Growth and above support custom field types including text, number, date, dropdown (single select), and multi-select. We create the destination fields via Pipedrive API before migration and flag any Streak property types (such as currency with symbol) that require type normalization during import.

Streak mail merge campaigns store recipient lists, email templates, send history, and open/reply tracking. We export campaign metadata (name, send date, recipient count, open rate, reply rate) and template content with merge variable syntax. Pipedrive has no direct mail merge campaign object; templates with merge variables are available via Email Templates, and outreach sequences are available via the Sales Automation Power Dialer add-on. We deliver a written rebuild guide mapping each Streak campaign to a Pipedrive Email Template plus a Sequence rebuild plan, which the customer admin implements post-migration.

Streak Snippets (templated email text blocks with merge variables) map to Pipedrive Email Templates. We export snippet content and merge variable syntax. Streak uses {{contact.firstName}} and similar variable syntax; Pipedrive uses {{ person.first_name }} format. We transform variable naming conventions during export so templates are immediately usable in Pipedrive without manual variable re-tagging.

Streak Team Members map to Pipedrive Users. We resolve by email match. Any Streak user without a matching Pipedrive User is held in a reconciliation queue for the customer admin to provision. Archived Streak users (read-only access on Pro+) require explicit reactivation before their Boxes are accessible for export; we detect archived users during the schema audit and prompt the customer to confirm reactivation before including those Box records.

Streak Enterprise custom roles and data validation rules are extracted during schema audit. Pipedrive's role model uses Admin, Member, and Limited access levels from Essential onward, with visibility controls on pipelines and activities. We map the nearest Pipedrive role for each Streak Enterprise role definition and flag any permission constructs (field-level write restrictions, data validation rules) that cannot be represented in Pipedrive's standard role model as a post-migration configuration note.