Skip to content
Get a quote

Streak to HubSpot migration

Moving from Streak to HubSpot means translating a Gmail-centric box-and-pipeline model into HubSpot's unified contact-and-deal database. FlitStack AI maps every Streak box, stage, person, and custom property to HubSpot contacts, deals, and custom properties — preserving original create timestamps, owner assignments, and Streak-specific thread associations so your new HubSpot portal carries the full sales context from day one.

Short answer

FlitStack AI migrates contacts, companies, deals, deal pipelines and deal stages from Streak to HubSpot, with their history and the associations between records. Every field is mapped and validated, a sample run is checked with you before the full migration, and the whole move can be rolled back in one click. Typical timeline: 24–48 hours for under 25,000 Streak boxes and contacts.

By

Source Streak
DestinationHubSpot
ContactCompanyDealDeal PipelineDeal Stage
Mapped field by field · sample run · one-click rollback

What moves from Streak to HubSpot?

Streak organizes sales work around Gmail threads — each box wraps a deal or process around an email conversation, with stages defined per pipeline and people tracked as simple contact records.

Read the full summary

HubSpot uses a unified contact model where lifecycle stage tracks the buyer journey, deals belong to pipelines with configurable stages, and companies link to contacts in a graph rather than flat lists. The migration maps Streak's Pipeline objects to HubSpot deal pipelines, Streak boxes to HubSpot deals, Streak people to HubSpot contacts, and Streak companies to HubSpot companies — collapsing the thread-centric box model into HubSpot's object-relationship structure. Email threads associated with boxes do not migrate as native timeline entries; they require either HubSpot's Gmail integration or a custom attachment of thread exports. We handle the data extraction via Streak's REST API, map every standard and custom property, and deliver a sample migration with field-level diff before committing the full run. Workflows, mail-merge sequences, and Gmail-side automations built inside Streak do not transfer — those must be rebuilt as HubSpot workflows and sequences. All object relationships (person-to-box, company-to-person) are resolved by email match against HubSpot users and contact records before insert.

direct

Person (Contact) → Contact

Streak people map to HubSpot contacts 1:1.

How it maps

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.

direct

Company → Company

Streak companies map to HubSpot companies 1:1.

How it maps

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.

direct

Box (Deal) → Deal

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.

How it maps

Closed-won and closed-lost boxes map to HubSpot deal stages using the mapped stage name.

direct

Pipeline → Deal Pipeline

Each Streak pipeline becomes a HubSpot deal pipeline.

How it maps

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.

value_mapping

Stage (within Pipeline) → Deal Stage (within Pipeline)

Stage names map value-by-value from each Streak pipeline to the corresponding HubSpot deal pipeline stage.

How it maps

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.

direct

Task → Task

Streak tasks map to HubSpot tasks with subject, due date, completion status, and owner preserved.

How it maps

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.

What moves15 objects
StreakHubSpot
  • PersonContact1:1
  • CompanyCompany1:1
  • BoxDeal1:1
  • PipelineDeal Pipeline1:1
  • StageDeal Stagetransformed
  • TaskTask1:1

+ 9 more in the mapping below

How Streak and HubSpot differ

The differences that decide how each record is mapped. These are what a CSV export and a native importer don't resolve for you.

DimensionStreakHubSpot
Record modelStreak boxes wrap every record around a Gmail thread — contacts and companies are secondary to the email-centric box viewHubSpot uses a unified contact model with lifecycle_stage as the primary buyer-journey property; deals and tickets are separate objects linked by associations
Pipeline modelStreak pipelines define a stage list scoped to one pipeline per team; box stage values are free-text or pick-list within each pipelineHubSpot deal pipelines have named stages with probability percentages, automation triggers, and optional weighted scoring; multiple pipelines are fully isolated
Custom fieldsStreak custom properties exist per-object (box, person, company) as key-value pairs; types include text, number, date, dropdown, checkbox, and user-pickerHubSpot custom properties support text, number, date, select, multi-select, checkbox, and HubSpot-user-picker types; custom objects (Enterprise) extend the schema beyond contacts and deals
Email threadingStreak stores emails as the primary record context — every box is anchored to one Gmail thread with all replies visible inlineHubSpot tracks email as activities logged against contact and company timelines; the Gmail sidebar integration provides a similar in-context view but the historical thread must be re-associated
Automation / sequencesStreak sequences (Pro+ plan) send timed email steps from Gmail with open/click tracking; automations trigger on stage changes within a boxHubSpot sequences (Sales Hub Professional/Enterprise) operate from the Sequences tool and enroll contacts via manual add or workflow; HubSpot workflows handle multi-step automation across objects
Reporting depthStreak offers basic pipeline stats, email open rates, and reply rates per box; reporting is scoped to individual pipeline viewsHubSpot provides revenue forecasting, deal velocity reports, team-level dashboards, and custom report builder across all objects — available at all Sales Hub tiers
Collaboration modelStreak boxes are owned by one Gmail user; sharing is via Streak team permissions on the box levelHubSpot uses owner assignment on records with team-based sharing rules, record-level access control, and object-level sharing settings

Streak to HubSpot field mapping

The 30 most-used fields of 42 mapped for this pair. Custom fields are added from your own schema during scoping. Download the full mapping (CSV) ↓ or open it in the field mapping template.

Field mapping5 shown
StreakHubSpot
  1. namePerson firstnameContact
  2. emailPerson emailContact
  3. phonePerson phoneContact
  4. job_titlePerson jobtitleContact
  5. addressPerson addressContact
Streak fieldHubSpot fieldMappingNote
Person.nameContact.firstnamedirect
Person.emailContact.emaildirect
Person.phoneContact.phonedirect
Person.job_titleContact.jobtitledirect
Person.addressContact.addressdirect
Person.cityContact.citydirect
Person.stateContact.statedirect
Person.zipContact.zipdirect
Person.countryContact.countrydirect
Person.linkedin_urlContact.linkedinbjdirect
Person.notesContact.notes_last_contacteddirect
Person.last_contactedContact.notes_last_updateddirect
Person.owner_emailContact.hubspot_owner_idtransformedStreak owner email resolves to HubSpot user by email match; unmatched owners flagged for fallback assignment before migration.
Person.createdateContact.original_create_datecustom_field_requiredHubSpot CreatedDate is set at migration time. Original Streak create date preserved as a custom datetime property for reporting continuity.
Company.nameCompany.namedirect
Company.domainCompany.domaindirect
Company.phoneCompany.phonedirect
Company.addressCompany.addressdirect
Company.cityCompany.citydirect
Company.stateCompany.statedirect
Company.zipCompany.zipdirect
Company.countryCompany.countrydirect
Company.linkedin_urlCompany.linkedin_company_pagedirect
Company.createdateCompany.original_create_datecustom_field_requiredHubSpot Company CreatedDate is set at migration time. Original Streak company create date stored as a custom datetime property.
Box.nameDeal.dealnamedirect
Box.amountDeal.amountdirect
Box.stageDeal.dealstagevalue_mappingStreak box stage maps to HubSpot deal stage by value within each pipeline. Probability and forecast category re-applied from HubSpot stage configuration.
Box.pipelineDeal.pipelinedirect
Box.closedateDeal.closedatedirect
Box.createdateDeal.original_create_datecustom_field_requiredHubSpot deal create date set at migration time; original Streak box create date preserved as a custom datetime field for historical reporting.

What to watch for in a Streak to HubSpot migration

The issues we plan around on this pair: limits and data-model gaps that the official import tools leave to you.

high

Gmail thread-to-deal association does not migrate as a native HubSpot timeline link

Streak boxes are fundamentally anchored to Gmail threads — every reply in the thread appears inside the box in Streak.

How we handle it

HubSpot's deal timeline logs emails as individual engagement records, not as a thread-level container. When migrating, we export the Gmail thread as a file attachment and link it to the HubSpot deal, but the inline thread view that makes Streak boxes useful for email-centric sales teams does not have a direct HubSpot equivalent. Teams should enable HubSpot's Gmail sidebar integration (available in HubSpot Sales Hub) to resume thread-level email tracking from the migration date forward, and treat historical thread exports as attachments rather than live timeline entries.

high

Streak pipelines with identical stage names require pipeline-scoped stage mapping in HubSpot

HubSpot deal stages are scoped per pipeline — the same stage name (e.g., 'Negotiation') can exist with different probability values in two separate HubSpot pipelines.

How we handle it

If a team uses multiple Streak pipelines with overlapping stage names, we must create separate stage records in each HubSpot pipeline and map the correct stage probability per pipeline. Failure to scope stage mapping correctly causes closed-won deals to land in the wrong pipeline stage with incorrect probability, corrupting revenue forecasting. We deliver a pipeline-to-pipeline stage mapping table before the migration runs so HubSpot admins can pre-configure the stage probabilities.

medium

Streak's API rate limits require batched extraction that extends planning time for large accounts

Streak's API enforces per-user rate limits that throttle bulk exports.

How we handle it

For accounts with more than 10,000 boxes, we must paginate extraction over multiple API sessions to avoid 429 errors, which adds time to the discovery and extraction phases. HubSpot's bulk import API accepts up to 10,000 records per batch, so the HubSpot side is not the bottleneck. The extraction phase is planned in batches of 1,000 records per session with exponential backoff between retries; accounts exceeding 25,000 total records should expect a 1–2 day additional planning window for API throttling mitigation.

medium

Box-level custom properties with user-picker type require manual HubSpot owner resolution

Streak custom properties of type 'User' store the assigned Gmail user's email address.

How we handle it

In HubSpot, owner assignment on deals and contacts uses HubSpot's native owner object. We resolve by email match — if the Streak user has a HubSpot account with the same email, the assignment transfers automatically. If the Gmail user has no HubSpot account, the custom property value is preserved as a string and the deal is assigned to a fallback owner, requiring post-migration manual assignment review. This is especially common for teams that onboard new sales reps between migration planning and go-live.

low

Multi-company contacts in Streak collapse to a primary company association in HubSpot

Streak allows a person record to be associated with multiple companies directly on the person object.

How we handle it

HubSpot's contact model links one primary company via the 'associated company' property, with additional company associations stored in the Contact-Company association table. We migrate the most-recently-used company association as the primary HubSpot company and surface additional company links in the association table. Teams relying on multi-company contact views in Streak should review the association table post-migration and use HubSpot list filters or custom views to replicate their multi-company segmentation.

How the migration runs

  1. Extract Streak data via API with batched pagination

    FlitStack AI connects to Streak via the Streak REST API using OAuth credentials scoped to read boxes, people, companies, tasks, notes, and custom properties.

    What this step covers

    We paginate extraction at 1,000 records per session to respect Streak's per-user API rate limits, using exponential backoff when rate-limit responses (429) occur. The extraction produces a structured JSON export per object type with original timestamps, owner email, and pipeline/stage metadata. All Streak custom property definitions are exported as a schema manifest before record extraction begins, so we know the full property inventory before field mapping starts.

  2. Build the Streak-to-HubSpot field map and create HubSpot custom properties

    We map every Streak standard field to its HubSpot equivalent (person→contact, company→company, box→deal, pipeline→pipeline) and flag custom properties requiring HubSpot custom field creation.

    What this step covers

    HubSpot custom properties are created in HubSpot via the CRM Objects API before any records are inserted — this ensures field IDs are available for the insert mapping. For Streak user-picker custom properties, we generate an owner-resolution table cross-referencing Streak user emails against HubSpot user IDs. The full field map and owner-resolution table are delivered as a pre-migration review artifact.

  3. Run a sample migration with field-level diff on 100–500 representative records

    A representative slice of Streak records — covering at least one box per pipeline, a mix of open and closed stages, records with custom properties, and records with attachments — migrates into a HubSpot sandbox or staging portal.

    What this step covers

    We generate a field-level diff comparing source values against destination field values for every mapped property. You review the diff to confirm stage mapping, deal amounts, owner resolution, and custom property values before the full run commits. Any mapping adjustments are made in this phase before production data moves.

  4. Execute the full migration with delta-pickup window and audit log

    Companies migrate first, then contacts, then deals — this sequence ensures that deal-to-company and deal-to-contact foreign keys resolve correctly in HubSpot.

    What this step covers

    All object relationships (box-to-person via email, person-to-company via domain) are resolved before insert. After the full migration completes, a delta-pickup window of 24–48 hours captures any Streak records modified during the cutover period. Every migration operation is logged to an audit trail. One-click rollback is available if post-migration reconciliation identifies mapping errors — the rollback reverts HubSpot to its pre-migration state without touching Streak.

  5. Deliver rebuild references for workflows, sequences, and email automations

    Streak workflows, mail-merge sequences, and stage-change automations are documented as rebuild specifications rather than migrated data.

    What this step covers

    We export each sequence's step order, email template body, delay rules, and enrollment trigger as a structured CSV and markdown reference. Your HubSpot admin uses these to recreate equivalent HubSpot Sequences (for email sequences) and HubSpot Workflows (for stage-change and field-update automations). The rebuild reference is delivered alongside the migration report on go-live day.

Streak HubSpot
  1. Connect
  2. Map
  3. Sample
  4. Migrate
  5. Verify
  • Contacts48,210 / 48,210 Done
  • Companies9,134 / 9,134 Done
  • Deals6,377 / 11,920 In progress
Example run
Restore points · HubSpotRollback ready
  1. Before sample runRestore point 01Restore
  2. Before full migrationRestore point 02Restore
  3. After verificationRestore point 03Current
Example

How long it takes, and what drives the quote

24–48 hours for under 25,000 Streak boxes and contactsTypical, smaller accounts
3–5 business days for setups with 25,000+ records, multiple pipelines, or extensive custom propertiesLarge or heavily customised accounts

Streak-to-HubSpot migration pricing depends on the total count of boxes (deals), people (contacts), and companies being migrated, plus the number of custom properties on each object. Pipelines with non-standard stage names require value-by-value stage mapping per pipeline, which adds schema planning time. HubSpot custom property creation (for Streak custom fields with no direct HubSpot equivalent) is scoped as a custom-field step. Sets with multiple Streak pipelines map to separate HubSpot deal pipelines, each needing individual stage probability configuration — this multiplies validation work and moves the quote toward the upper range. Every quote is scoped with you; there is no self-serve pricing.

Get a quote for Streak to HubSpot →

Why teams move from Streak to HubSpot

  • Streak's pipeline model caps out at basic stage tracking — as soon as a team needs lead scoring, multi-step automation, or revenue forecasting, they hit the ceiling of what a Gmail-embedded CRM can deliver. HubSpot's unified contact model with lifecycle stage and deal velocity reporting gives sales leaders the visibility that Streak's single-pipeline view cannot.
  • Streak removed its free CRM tier in 2024–2025, leaving solo users and small teams facing a $49/user/month bill for core CRM functionality. Teams that had relied on Streak's free Gmail power tools for email tracking and pipeline views found themselves paying for features that now justify evaluating HubSpot's free CRM tier as an alternative.
  • Teams using HubSpot's marketing automation, service hub, and CMS in addition to sales need a single CRM that shares the contact database natively. Running Streak alongside HubSpot marketing creates duplicate contact records, conflicting lifecycle data, and manual re-entry that erodes data quality across both platforms.
  • Streak's reporting is scoped to individual pipeline views — it cannot consolidate deal data across multiple pipelines, generate team-level forecasts, or feed deal velocity into HubSpot's analytics dashboards. Growing sales teams need reporting depth that outpaces Streak's basic stats and email open metrics.
  • When a team scales beyond a few reps, Streak's box-centric Gmail model creates a single point of failure — every deal, person, and activity is anchored to one Gmail thread, making it impossible to give non-Gmail stakeholders (operations, finance, leadership) meaningful CRM access without forcing them into a Gmail workflow.

Questions, answered

Streak to HubSpot migration questions

How long does a Streak to HubSpot migration take?

Most Streak-to-HubSpot migrations complete in 24–48 hours of clock time for under 25,000 total records (boxes, people, companies). Larger setups exceeding 25,000 records or those with more than 50 custom properties across objects extend to 3–5 business days. Streak's per-user API rate limits are the primary variable that affects extraction timeline — larger datasets require paginated batched extraction to avoid throttling, which can add 1–2 days to the planning phase before data moves.

Will my Streak workflows and mail-merge sequences migrate to HubSpot?

No. FlitStack AI migrates data and schema only — Streak workflows, mail-merge sequences, and stage-change automations have no portable export format and do not transfer. They must be rebuilt in HubSpot's Sequences tool (for email sequences) and HubSpot Workflows (for field-update and enrollment automations). We export each Streak sequence definition — step order, email template body, delay rules, and trigger conditions — as a structured rebuild reference for your HubSpot admin to implement after go-live.

What does a Streak box become in HubSpot?

Each Streak box migrates as a HubSpot deal. The box name becomes the deal name, the box pipeline becomes the HubSpot deal pipeline, and the box stage maps value-by-value to the corresponding HubSpot deal stage with probability re-applied. The box's monetary value becomes the deal amount, and the box create date is preserved as a custom datetime property (Original_Create_Date) on the deal. Email threads attached to the box are exported as file attachments and linked to the deal, since HubSpot's deal timeline logs individual email engagements rather than thread containers.

Can I migrate Streak custom properties to HubSpot custom properties?

Yes. Streak custom properties on boxes, people, and companies map to HubSpot deal custom properties, contact custom properties, and company custom properties respectively. The property type is preserved — Streak dropdown becomes HubSpot select, Streak checkbox becomes HubSpot single-checkbox, Streak number becomes HubSpot number, and Streak date becomes HubSpot date. User-picker custom properties in Streak resolve by email match to HubSpot owners. We create all required HubSpot custom properties before records insert, so field IDs are available during the migration run.

What happens to my Gmail thread associations when the boxes migrate?

Streak boxes store the Gmail thread ID and display all thread replies inline — this is the core of Streak's value for email-centric teams. HubSpot does not have a native thread-container construct; emails log as individual engagement records on the contact timeline. We export the full Gmail thread as an HTML file attachment linked to the migrated HubSpot deal and recommend enabling HubSpot's Gmail integration (Sales Hub) to resume live thread-level email tracking from migration date forward. Historical Streak thread exports become deal attachments rather than live timeline entries.

Does the migration affect my Streak account during cutover?

No. FlitStack AI uses scoped read-only API access to extract Streak data — your team continues working in Streak throughout the migration. A delta-pickup window of 24–48 hours after the initial migration run captures any boxes, people, or companies modified or created in Streak during the cutover period. Changes made in Streak after the delta window closes are the responsibility of your team to manually port or re-enter in HubSpot, though delta records are flagged in the migration report for manual review.

What happens to Streak boxes that have no associated person or company?

Streak boxes sometimes exist without a linked person record — for example, a box tracking an internal process or a deal opened against a company not yet in Streak's people database. In HubSpot, deals require an associated contact to attach to the deal timeline, but a deal can exist without a linked contact. We migrate orphan boxes as HubSpot deals with no primary contact association, flagged in the migration report for your team to link to a HubSpot contact after go-live. If the box references a company name but no person, we create a placeholder contact with that company name to anchor the deal relationship.

How do I handle Streak pipelines with overlapping stage names across multiple pipelines?

HubSpot deal stages are scoped per pipeline — the same stage name can appear in multiple pipelines with different probability values. If your Streak account uses multiple pipelines with overlapping stage names (e.g., 'Negotiation' appears in both Pipeline A and Pipeline B with different close probabilities), we create separate stage records in each HubSpot pipeline and map the correct probability per pipeline during migration. The pipeline-stage mapping table is delivered as a pre-migration review artifact so your HubSpot admin can confirm stage probabilities before the full run executes.

Get a quote

Moving from Streak to HubSpot?

Tell us roughly how many records and objects you have. We scope the mapping and the HubSpot setup with you, then send a quote.

Get a quote