Migrate from Streak to Freshsales

Streak Boxes are the primary CRM record and map to Freshsales Deals. We extract Box name, stage, owner, created date, last modified date, custom properties, associated contacts, and any Box-level notes. Box stage maps to Freshsales Deal stage. We create the parent Contact and Account in Freshsales before Deal import so that the AccountId and ContactId lookups are satisfied at insert time. Archived Boxes require reactivation in Streak before export; we flag any Box owned by an archived user during schema discovery.

Each Streak Pipeline defines the workflow stages a Box moves through. We map each Pipeline to a Freshsales Deal Stage set, creating Freshsales stages with names and probabilities that match the source pipeline stage configuration. If a Streak customer has multiple pipelines, we map each to a separate stage group or use Freshsales Deal custom fields to preserve multi-pipeline context within a single Deal object.

Streak Contacts (pulled from Gmail and stored alongside Boxes) map to Freshsales Contacts. We extract contact name, email address, phone, company affiliation, and any custom contact properties. Email address is the dedupe key during import. Streak contact-box associations migrate as Freshsales Deal-to-Contact relationships.

Streak stores company affiliation alongside Contacts, not as a separate object. We extract company data from the contact's Gmail affiliation and create Freshsales Account records. Account name becomes the Freshsales Account name, and the contact's email domain is used as a secondary dedupe signal. If no company affiliation exists in Streak, we create an Account named after the contact's domain or flag for customer decision.

Box-level tasks with assignees and due dates map to Freshsales Tasks. Streak tasks are flat — no subtasks or dependencies — which maps cleanly to Freshsales Task records. Task owner maps by email resolution to Freshsales User. Due dates and completion status transfer directly. Streak tasks with no due date become Open tasks in Freshsales.

Streak Custom Box Properties (dropdowns, text fields, dates, numbers, checkboxes) vary per pipeline. We discover the full property schema per pipeline during scoping, then pre-create matching Freshsales custom fields on the Deal object before migration. Field types are mapped: Streak text to Freshsales text, Streak date to Freshsales date, Streak number to Freshsales number, Streak checkbox to Freshsales checkbox. Custom fields without a matching Freshsales type are flagged for customer decision.

Streak Tags are flat labels applied to Boxes for filtering. We preserve all tag names and their Box associations as Freshsales Labels on the Deal. Tags with no attached Boxes are included as empty label lists for reconstruction in Freshsales. If the customer uses tags for multi-pipeline categorization, we map them to a Freshsales custom multi-select field.

Streak user records include email, name, and role (Pro tier or above for shared pipeline access). We map users by email to Freshsales User accounts. Archived users in Streak must be reactivated before their Box records are accessible for export; we detect archived users during schema audit and prompt the customer to confirm reactivation before export begins. Pro-tier users map to Freshsales users with the equivalent role permission set.

Streak mail merge campaigns store recipient lists, email templates, send history, and open/reply tracking. Freshsales has Sales Sequences (cadence tools) but they are structurally different from Streak's mail merge model. We export campaign metadata and send history as a structured CSV report delivered alongside the migration. We do not rebuild mail merge campaigns as Freshsales Sequences because the trigger conditions, follow-up rules, and template logic differ. The customer receives the send history as a reference document for manual sequence setup.