Migrate your Streak data

Boxes are Streak's primary CRM record, wrapping an email thread with custom fields, stage, owner, and tasks. We extract all Box properties, stage history, and associated contacts. Custom fields are preserved as direct property mappings. Archived boxes require explicit reactivation scoping before export.

Pipelines define the workflow stages a Box moves through. We extract pipeline configuration including stage names, stage order, and stage-specific fields. Pipeline assignments (which pipeline a Box belongs to) are mapped to the destination CRM's equivalent pipeline or deal stage structure.

Stages are ordered steps within a Pipeline. We preserve stage names, ordering, and any stage-level metadata. Where the destination CRM uses fewer or differently named stages, we map them by position and prompt the customer to confirm stage grouping logic.

Streak Contacts are pulled from Gmail and stored alongside Boxes. We extract contact name, email address, company affiliation, and any custom contact properties. Gmail contact associations are preserved as email references in the exported record.

Tasks are Box-level action items with assignees and due dates. Streak tasks are flat — no subtasks or dependencies — and lack date-based ordering. We map them to the destination's task or activity objects, normalizing date formats and mapping assignee email addresses to destination user records.

Snippets are templated email text blocks with merge variables. We export snippet content and variable syntax. Variable naming conventions differ between Streak and destination CRMs, so we map merge field tokens to the destination's expected format during import.

Mail merge campaigns store recipient lists, email templates, send history, and open/reply tracking data. We export campaign metadata and send logs. Open tracking metrics are Streak-specific and map to the destination's activity tracking model.

Tags are flat label applied to Boxes for filtering. We preserve all tag names and associations. Tags with no Boxes attached are included as empty label lists for reconstruction in the destination.

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 before export and map each property to the destination's custom field structure, prompting for type confirmation where no direct match exists.

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 prompt customers to confirm access before initiating attachment export.

User records include email, name, role, and permissions level. Shared pipeline access depends on the Pro tier or above. We map users to destination CRM users by email and flag any archived users that need reactivation before their Box assignments can be transferred.

Enterprise tier includes custom roles and data validation rules. We extract role definitions and permission scopes and map them to the destination's role and access control model, flagging Enterprise-only constructs that have no direct equivalent.