Migrate from Streak to HubSpot

Streak people map to HubSpot contacts 1:1. All standard fields including name, email, phone, address, and job title transfer directly to the corresponding HubSpot contact properties. The Streak person's pipeline assignments — indicating which boxes they appear in across any pipeline — are reconstructed as HubSpot deal-contact associations by matching against the contact's email address. This ensures the contact's deal history is preserved in HubSpot's association graph.

Streak companies map to HubSpot companies 1:1. Domain-based linking in HubSpot auto-associates contacts to the matching company record after migration. If a Streak company has no domain, we use the stored company name as the HubSpot company name and flag for manual review.

Streak boxes map to HubSpot deals 1:1 using the box name as the deal name, the box's monetary value as the deal amount, the pipeline stage as the deal stage, and the box's create date as a preserved custom property. Closed-won and closed-lost boxes map to HubSpot deal stages using the mapped stage name.

Each Streak pipeline becomes a HubSpot deal pipeline. HubSpot allows multiple isolated pipelines — this directly parallels Streak's multi-pipeline model. We create a new HubSpot pipeline for each Streak pipeline and configure stage names and probabilities to match the source stage order.

Stage names map value-by-value from each Streak pipeline to the corresponding HubSpot deal pipeline stage. Probability percentages are applied per stage in HubSpot. If a Streak stage name does not match an existing HubSpot stage, we create a new stage in the target pipeline before inserting records.

Streak tasks map to HubSpot tasks with subject, due date, completion status, and owner preserved. Tasks attached to a specific Streak box are linked to the migrated HubSpot deal using the deal's internal ID stored on the task record. Unassigned tasks are flagged before migration.

Streak notes attached to a box become HubSpot engagement notes on the migrated deal timeline. If a note is attached to a person or company, it becomes a note on the corresponding HubSpot contact or company. Original timestamps and note authors are preserved as metadata.

Files attached to Streak boxes are downloaded and re-uploaded to HubSpot's file storage, linked to the migrated deal or contact. HubSpot's 60-day file-access window and storage limits are checked before migration. Inline images in notes are extracted and rehosted as HubSpot file attachments.

Streak mail-merge sequences and step configurations have no HubSpot equivalent that preserves the sequence structure. We export the sequence definition (step order, email template body, delay rules) as a CSV rebuild reference for your HubSpot admin to recreate in HubSpot Sequences or Workflows.

Streak's Pro+ automations trigger on stage changes, email opens, or date conditions inside boxes. These are not extractable as portable configuration. We document each automation's trigger and action as a rebuild specification for HubSpot Workflows, where your admin implements equivalent logic using HubSpot's workflow builder.

Streak box custom properties that have no direct HubSpot deal field (e.g., a text field for 'Referral Source' or a dropdown for 'Contract Type') are created as HubSpot deal custom properties. The property type is preserved — dropdown maps to HubSpot select, number maps to number, date maps to date. If the custom property references a HubSpot user, it maps to a HubSpot-user-picker property.

Streak person custom properties (beyond standard name/email/phone) migrate as HubSpot contact custom properties. Type-aware mapping applies: Streak checkbox → HubSpot single-checkbox, Streak dropdown → HubSpot select, Streak multi-user-picker → HubSpot contact-property with the user email as value. Property display order is preserved in the migration plan.

Streak boxes store the Gmail thread ID and display all email replies inline. This thread-level association has no direct HubSpot equivalent — HubSpot logs emails as individual engagement records on the contact timeline. We attach the Gmail thread export as a deal attachment and recommend enabling HubSpot's Gmail integration (Sales Hub) to re-link ongoing email tracking from migration date forward.

Streak box owner is a Gmail user email. We resolve this against HubSpot users by email match. Unmatched owners are flagged before migration — your HubSpot admin either invites the Gmail user to HubSpot first or assigns their records to a fallback owner. No deal lands without an owner assigned.

HubSpot's deal create date is set at migration time. We preserve the original Streak box create date as a custom datetime property (Original_Create_Date__c convention), and the stage-entered timestamp for each pipeline stage as a separate custom datetime. This enables reporting continuity from day one in HubSpot.