Migrate from Streak to Zoho CRM

Streak Boxes map to Zoho CRM Deals as the primary record. The Box subject (typically the email thread subject) becomes the Deal name. Box stage history maps to Deal stage transitions with timestamps preserved. We preserve the Gmail thread reference as a structured custom field gmail_thread_ref__c rather than recreating the email inside Zoho. Custom Box properties (per-pipeline text fields, dropdowns, checkboxes, dates, numbers) map to Zoho custom fields scoped to the corresponding Deal layout. If the Box has an associated Pipeline assignment, we map it to the nearest Zoho Custom Pipeline using stage-order matching.

Streak Pipelines define the workflow stages a Box moves through. We map each Streak Pipeline to a Zoho Custom Pipeline with matching stage names and ordering. Stage-specific fields from Streak (fields visible only at certain stages) become Zoho custom fields on the Deal with conditional visibility rules applied via Zoho Blueprint or layout rules. Pipeline ownership and shared/private access flags map to Zoho Deal ownership and sharing rules.

Streak Stages are ordered steps within a Pipeline. We preserve stage names, ordering, and any stage-level metadata (such as stage-specific field visibility) as Zoho Stage values within the corresponding Custom Pipeline. Where Zoho uses fewer stage slots than the source Streak Pipeline, we map by position and flag any orphaned stage names for the customer's admin to resolve.

Streak Contacts (pulled from Gmail and stored alongside Boxes) map directly to Zoho CRM Contacts. We extract contact name, email address, company affiliation, phone, and any custom contact properties. Gmail contact associations are preserved as structured metadata. Email addresses serve as the deduplication key during import. Contacts are imported before Deals so that the Deal-Contact lookup relationship is satisfied at import time.

Streak stores company affiliation on Contacts and Boxes as a free-text or contact-linked field. We map it to Zoho CRM Account. If the company is stored as a free-text field on the Box (not linked to a Streak Contact), we create a corresponding Account record and link it to the Deal during migration. Account domain and website data maps to the Account's Website field when available.

Streak Tasks are Box-level action items with assignees and due dates. They are flat — no subtasks or dependencies — and map directly to Zoho CRM Tasks. We preserve assignee (mapped by email to Zoho User), due date, task subject, and completion status. Streak task notes migrate as Task comments or description text. Completed vs open status maps to Zoho Task Status values.

Streak Tags are flat labels applied to Boxes for filtering. We preserve all tag names and their Box associations as Zoho Tags linked to the corresponding Deal records. Tags with no Boxes attached are included as empty tag lists for reconstruction in Zoho. Tags are stored as a multi-select picklist on the Deal in Zoho to maintain the flat-label behavior from Streak.

Streak Mail Merge campaigns store recipient lists, email templates, send history, and open/reply tracking. We export campaign metadata and send logs as structured records linked to the source Contacts. The actual email template content and merge field syntax migrate as a Zoho Email Template. Automated follow-up sequences require rebuilding in Zoho Blueprint or Workflow rules; we document the original cadence (days between sends, conditions, skip rules) as a written handoff so the customer's admin can reconstruct it. Open tracking metrics are Streak-specific and cannot be represented in Zoho's standard analytics.

Streak Snippets are templated email text blocks with merge variables. We export snippet content and variable syntax as Zoho Email Templates. Variable naming conventions differ between Streak and Zoho (Streak uses {{contact.name}} while Zoho uses $Contact.Name$), so we map merge field names during the transform phase and flag any unresolvable variables for the customer's admin to correct in the Zoho template editor.

Streak User records (email, name, role, permission level) map to Zoho CRM Users. We resolve by email match. Archived Streak users require reactivation before export — we detect them during the schema audit and prompt the customer to confirm reactivation before including their Box records in the export. Enterprise-tier custom roles and permission scopes from Streak are extracted and mapped to Zoho Roles and Profiles, with any unresolvable permission rules flagged for manual remapping.

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, pre-create the corresponding Zoho custom fields (with correct field types and picklist values), and map each property during the Box export. Properties that exist on some Boxes but not others in the same Pipeline are created as optional fields in Zoho to avoid null-value import failures.

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; we flag this dependency upfront. In Zoho, attachments are stored as file fields on the Deal or Contact record. We do not migrate the attachment content if the source Gmail account is scheduled for deactivation before migration completes.