Streak to HubSpot
A CRM that runs inside Gmail and organises work as pipelines, boxes (deal records), stages, contacts and organizations.
Streak data can move into HubSpot, landing mainly in Sales Hub. 3 of 11 mapped objects move directly (Boxes (pipeline rows), Contacts and Organizations); 5 items need manual work and 2 do not move. Plan roughly 1-2 weeks for a small move and 6-12 weeks for a large one.
Migration checklist for Streak
Three phases, specific to this system. Tick steps off as you go.
Before
0 of 5 doneDuring
0 of 5 doneAfter
0 of 5 doneWhat will it take?
No price list: cost follows volume, custom objects and how much logic must be rebuilt. Answer four quick questions for a planning range.
The three scenarios
Small migration
<5k boxes and contacts, 1-2 pipelines
Sheets and CSV import.
Mid migration
5k-50k records, 3-6 pipelines
Adds API pulls for comments and files, and a workflow rebuild.
Large migration
50k+ records, many pipelines and teams
Needs ETL or API scripts, custom objects and staged cutover.
What moves the number
Timeline ranges are planning estimates, not a quote. A partner confirms scope after discovery.
Access, mapping and limits
Start with how data leaves Streak: what you need to get in, what lands in HubSpot, and what will not.
REST (v1 and v2)
A personal Streak API key from the account of a user who can see the pipelines. Keys are tied to a single user.
Not documented. The user needs access to the pipelines being exported.
No hard limit. Streak asks to be told before you exceed 10 requests/second. Google limits projects to 20 requests/second. Responses return up to 100 records per page.
Choose your route
How will you move the data?
No native connector was found.
- You need: A personal Streak API key from the account of a user who can see the pipelines. Keys are tied to a single user.
- Permission: Not documented. The user needs access to the pipelines being exported.
Native imports often bring over only some data, so check coverage per object in the mapping below.
Export each object, clean it, then import it into HubSpot.
- Pipeline exporter to Google Sheets (full pipeline, selected boxes or a saved view). It covers boxes, contacts and organizations by default, with optional newsfeed, call logs/meeting notes and tasks.
- Scheduled exports, available on Pro+ and Enterprise plans only
- Download each Sheets tab as CSV
- REST API extraction of boxes and comments
- Export jobs endpoint (POST /pipelines/{key}/exportjobs), shown in Streak's Zapier guide
Limits: No hard limit. Streak asks to be told before you exceed 10 requests/second. Google limits projects to 20 requests/second. Responses return up to 100 records per page.
Migration and sync tools can move more than a plain import. Confirm which objects each one supports before you choose.
Best when volume is high, custom objects are many or automation is heavy. That is the Large scenario: 6-12 weeks, usually phased.
Talk to a partnerWhere each object lands
In Streak
In HubSpot
Hover or tap anything on the left to see where it lands.
| Source object | In HubSpot | Moves | Notes |
|---|---|---|---|
| Boxes (pipeline rows) | Deals | yes | The export includes all columns visible in the pipeline view and a box key for joins. Each pipeline maps to a HubSpot deal pipeline. Non-sales pipelines (hiring, support, projects) may fit Tickets or Custom objects better. |
| Stages | Deals | partial | Stage appears as a box column. Rebuild HubSpot pipeline stages first, then map the values. |
| Contacts | Contacts | yes | Exported by default. Import these before deals. |
| Organizations | Companies | yes | Exported by default. Import these first. |
| Tasks | Tasks | partial | Optional in the export. Recreate open tasks and archive the rest. |
| Call logs and meeting notes | Calls | partial | Optional in the export. Load as Calls, Meetings or Notes via the HubSpot import or API. |
| Pipeline newsfeed (activity history) | Notes | manual | Exports to CSV or Sheets. It is best kept as an archive, or loaded as Notes if history is needed. |
| Email threads | Emails | no | Threads stay in Gmail and the export does not record which threads belonged to which box. |
| Files | Files | manual | Files are not exported. Download them from each box, or use file keys via the API. |
| Comments | Notes | manual | Not in the export. Pull them via the API. |
| Users (owners) | Contacts | manual | Owner and assignee values are only text in the export. Map them to HubSpot users yourself. |
What to expect
The export does not include threads, and it does not record which threads belonged to which box.
The sources describe the API as covering core objects. Gmail-specific features such as tracking and mail merge are not available through it.
Automation rules are not part of the data export.
Permissions are not exported. This is a category-level assumption.
Only raw data is exported, and reports are not.
Both are excluded from the exporter.
Each data type exports to its own tab, and the box key is the join field.
Connect Gmail to HubSpot and log key threads. Alternatively, use the API to list thread keys per box before cutover.
Use a dedicated, stable admin user's key for extraction.
Profile each column and map it to a typed HubSpot property or dropdown.
Use the box key as a unique ID on the HubSpot side.
Use the API or an ETL tool for large volumes.
Data governance and compliance
Decide what is allowed to move before anything is exported. Tick each gate once it is agreed.
How we researched this page
How much to trust each section, and where it comes from.
Export paths, API auth and rate guidance are backed by Streak docs and third-party guides. I found no HubSpot-specific doc for Streak, and I did not check security or certification pages. Governance and the mapping to HubSpot objects are category-level analyst judgement.
Sources
Related migrations
Frequently asked questions
How do I migrate Streak to HubSpot?
1. Inventory pipelines, columns and saved views, and decide which become Deals, Tickets or Custom objects. 2. Get the API key from a stable admin user and test GET /users/me against api.streak.com. 3. Check whether your plan includes the scheduled export (Pro+), or plan a one-off manual export. 4. Create HubSpot properties, deal pipelines and stages to match the Streak columns.
What data can move from Streak to HubSpot?
These objects move directly: Boxes (pipeline rows), Contacts and Organizations. Check the mapping table for partial and manual items.
What does not move from Streak to HubSpot?
Email threads linked to boxes and Streak automations, mail merge and email tracking. Plan to rebuild or retire these.
How long does a Streak to HubSpot migration take?
Small (<5k boxes and contacts, 1-2 pipelines): 1-2 weeks. Mid (5k-50k records, 3-6 pipelines): 3-6 weeks. Large (50k+ records, many pipelines and teams): 6-12 weeks. These are planning estimates, not a quote.
What access do I need to export from Streak?
A personal Streak API key from the account of a user who can see the pipelines. Keys are tied to a single user. Not documented. The user needs access to the pipelines being exported.
What compliance issues apply when moving Streak data?
Check: Free-form notes may contain health, financial or minors' data. Review before moving.. Agree consent, retention and access rules before exporting.
Moving Streak into HubSpot?
A network of 153+ tiered HubSpot partners and 1,800+ accounts of experience. Tell us what you are moving and which hub matters most.
Talk to a partner