Cancellation playbook · Operator diary · 2026
How to cancel HubSpot without losing data
HubSpot cancellations fail in one of two ways: missing the 60-day notice window (locking you in for another year), or canceling before fully exporting data (losing workflows, custom properties, and engagement history). Both are preventable with the 5-step framework below. 8-15 hours of focused work over 60-90 days. At solo-founder through 5-person scale, the savings from canceling are typically $300-1,500/month — the migration pays back within 30 days.
The 5-step framework
Step 1 — Track the renewal date and the 60-day notice window first
HubSpot Sales Hub and Marketing Hub contracts auto-renew unless you provide written notice 60-90 days before renewal (check your specific MSA — Sales Hub typically 30 days for monthly, 60 days for annual; Marketing Hub typically 60 days for annual). Miss the window and you are locked for another year. Before anything else, find your renewal date and count backwards 90 days. That is your migration deadline. Set 3 calendar reminders: 90 days out (start migration), 60 days out (data export deadline), 30 days out (cancellation notice deadline). Single biggest cancellation failure is missing the notice window, not picking the wrong replacement.
Operator tip: Your contract end-date lives in HubSpot under Account Settings → Account Defaults → Billing → Contracts. Pull the exact date today. If you are inside the notice window already, your options collapse to (a) negotiate a one-month extension to land outside the window, or (b) accept the annual lock and plan migration for next year.
Step 2 — Export EVERYTHING before cancellation — contacts, deals, properties, custom fields
HubSpot allows full data export via Account Settings → Account Defaults → Tools → Export. Export everything: contacts (CSV with all custom properties), companies, deals (with stage history and custom fields), tickets if you use Service Hub, all custom properties (do not assume they will translate cleanly), email engagement history (opens, clicks, replies), call recordings if you use Calling Hub, and meetings booked. Most exports are CSV; calls are MP3 with a metadata CSV. Run the exports 60-75 days before renewal so you have time to validate the data is complete. Keep the export files in a folder for 12 months minimum in case something is missing post-migration.
Operator tip: Export the workflow definitions, not just the contacts in workflows. Workflows have logic (if X happened, do Y) that is HubSpot-specific and will need to be rebuilt in the new tool. Document each workflow in plain text (a Notion doc works) so the replacement tool implementation has a spec to build off, not just contact lists.
Step 3 — Pick the replacement and run parallel for 2 weeks
For solo-founder through 5-person teams replacing HubSpot Sales Hub: Close ($59-329/seat — full CRM + dialer + sequences), Pipedrive ($20-99/seat — visual CRM + light sequences), Folk ($24-99/seat — relationship-led CRM), Attio ($29-119/seat — data-model B2B CRM), or HubSpot Sales Hub Starter ($20/seat — if you only want to drop the Marketing Hub seat). For Marketing Hub replacement: Brevo ($25-99/mo — email + marketing automation), Customer.io ($100+/mo — workflow-heavy), Loops.so ($49+/mo — engineer-friendly), or downgrade to HubSpot Free Marketing tier. Pick the replacement based on the job-overlap map (see /how-to-audit-my-sales-stack). Import the exported data into the replacement. Run BOTH tools in parallel for 2 weeks before canceling — your team uses both, you compare workflows, you confirm nothing critical is missing in the replacement. 2 weeks is the minimum; 4 weeks is safer.
Operator tip: During parallel run, do NOT split traffic between tools (e.g., new leads to HubSpot, old leads to Close). Both tools should see the same activity. This is the only way to compare them honestly. If the team uses HubSpot for some activity and Close for others, the test is invalid — you have not actually evaluated whether the replacement can do the full job.
Step 4 — Send the written non-renewal notice (and copy your CSM email)
HubSpot requires written non-renewal notice via email to your CSM with cc to the legal address listed in your MSA. Template: "Per Section [X] of our MSA dated [date], this email serves as written notice that [Company Name] will not renew the [Sales Hub / Marketing Hub / Service Hub] subscription. Our contract end date is [date]. Please confirm receipt of this notice and provide the data export and account closure procedure." Send 65-75 days before contract end (giving a small buffer past the 60-day window). Keep the email response — HubSpot CSMs typically reply within 3-5 business days with confirmation and the retention pitch. Do not delete the confirmation email — it is your proof of timely notice if there is a dispute later.
Operator tip: Expect a retention call within 1-2 weeks of sending the notice. HubSpot will offer 20-40% discount to keep you. If your decision is based on consolidation (replacing HubSpot with Close), the discount is irrelevant — say so. If your decision is on cost only and the discount makes HubSpot competitive again, take it. Either way, the retention call is a forcing function for the consultant or sales team to surface the actual best price — useful data even if you do not renew.
Step 5 — Cancel on the contract end date — not before
After the notice is sent and confirmed, the contract continues running through its end date. Do not cancel mid-term — you lose the remaining paid time. Continue using HubSpot through the end date (or as long as the team needs to during the parallel run). On the contract end date, the account auto-cancels per your notice. Verify the cancellation by logging in 3-5 days after the end date — the account should be locked or downgraded to Free tier. Save the final invoice as the closing record. If HubSpot continues billing past the end date, dispute the charge via the credit card and provide the notice email + confirmation as evidence.
Operator tip: Some HubSpot accounts retain Free-tier access after paid cancellation — this is fine and does not extend the paid contract. You can keep a Free account for reference (contact lookups, old reports) for as long as HubSpot offers Free tier. The Free tier costs nothing and gives you a backup view if the migration uncovers a missing data point later.
Three approaches considered
| Approach | Structure | Pro case | When it fits |
|---|---|---|---|
| DIY 5-step migration (this article) Recommended | Founder tracks renewal date, exports all data, picks replacement, runs parallel for 2 weeks, sends written notice 65-75 days before renewal, cancels on contract end date. 8-15 hours of focused work over 60-90 days. | Free. Founder owns the migration knowledge. Documentation becomes the artifact for future tool migrations. Pays back instantly (HubSpot Sales Hub Pro starts at $1,500/mo for 3 seats — 1 month of savings funds the migration time). | Requires founder time and discipline. The parallel-run validation period is non-negotiable; rushed migrations break workflows and lose data. |
| Run StackScan to audit consolidation candidates | Paste current stack into StackScan. Receive ranked recommendations including HubSpot consolidation analysis with replacement options and savings math. | Removes the cognitive load of comparing replacement options. Dollar-specific recommendations. Useful as input to the DIY migration steps. | Audit is the analysis layer, not the migration execution layer. You still need to run the 5-step migration after StackScan tells you what to swap to. |
| Hire a migration consultant | Engage a consultant to handle the migration end-to-end. Typical $2K-8K project (HubSpot-specific migration specialists exist). | Outsourced execution. Consultant knows HubSpot data quirks and replacement tool import patterns. Faster than DIY for large data volumes. | At solo-founder through 5-person scale, $2K-8K is real money for a migration that takes 8-15 hours of DIY work. Better at 10-30 person scale with complex workflows. At smaller scale, DIY with StackSwap consulting at $250/hr for spot questions is more cost-effective. |
Common mistakes
- Missing the 60-day notice window. Single biggest cancellation failure. Track every renewal date in one calendar with 90-day reminders. The notice window is non-negotiable.
- Canceling before exporting data. Once the account closes, data access becomes restricted or impossible. Export EVERYTHING 60-75 days before cancellation, with 2-week validation window.
- Skipping the parallel-run period. 2-4 weeks running both tools is the only honest test of whether the replacement covers the full job. Migrations that skip this step lose workflows and break team productivity.
- Not exporting workflow definitions. HubSpot workflow logic is platform-specific. Export contacts AND the workflow specs (Notion docs work) so the replacement implementation has a spec to build off.
- Accepting a retention discount without re-evaluating fit. A 30% discount on the wrong tool is still the wrong tool. If your decision was consolidation-driven, the discount is irrelevant. If cost-driven and the discount makes HubSpot competitive, take it.
- Hiring a migration consultant at solo-founder scale. $2K-8K for a migration that DIY takes 8-15 hours is over-engineered for stage. Better at 10-30 person scale with complex workflows.
Related operator reading
- The SaaS renewal negotiation playbook — before canceling, try negotiating. Can cut 20-40% on renewal without changing tools.
- Are you wasting money on HubSpot? — the 7-sign diagnostic for whether cancellation is the right move at your stage.
- How to audit your sales stack — the broader framework that surfaces HubSpot cancellation as one of several consolidation candidates.
- Consolidating sales tools at 5 employees — the consolidation framework typical post-HubSpot stacks land at.
- StackSwap services — $250/hr scoped consulting for HubSpot migrations. Typical 4-8 hour project = $1,000-2,000 for full migration support.
FAQ
Canonical URL: https://stackswap.ai/how-to-cancel-hubspot-without-losing-data