Migrating Away from HubSpot: A Complete Guide

HubSpot is the most popular CRM for startups and growing businesses — and it's also one of the most common sources of migration projects. The reasons vary: pricing surprises as you scale, frustration with feature gating, concerns about data ownership, or simply finding a tool that fits your workflow better.

Whatever brought you here, this guide covers the complete process: exporting your data, avoiding common pitfalls, evaluating alternatives, and executing the migration without losing anything important.

Why People Leave HubSpot#

Understanding why teams migrate helps you plan better and avoid ending up in the same situation with your next CRM.

Pricing at Scale#

HubSpot's pricing structure is designed to be cheap at the start and expensive as you grow. The free CRM is genuinely useful, but the moment you need marketing automation, reporting, sequences, or more than a few seats on certain features, you're looking at significant monthly costs.

The common shock point: a 10-person sales team with marketing automation and reporting can easily hit $5,000-15,000/month on HubSpot's professional and enterprise tiers. Teams that signed up on free and grew into paid have often not benchmarked what alternatives cost.

Feature Gating#

HubSpot gates features aggressively across tiers. Things that feel like they should be basic — custom report builders, advanced workflow triggers, predictive lead scoring, call recording — are locked to higher tiers. Teams that encounter these gates often face a choice between paying for the next tier or living without the feature.

Data Ownership Concerns#

Your contacts, deal history, email sequences, company data, and activity logs live on HubSpot's servers. You can export CSVs, but you can't run arbitrary SQL queries, connect your own BI tool directly, or access data in real time. For data-driven teams, this is a real constraint.

The AI Pivot#

HubSpot has added AI features aggressively, but many teams find them surface-level: summarize a note here, suggest a subject line there. Teams that want genuinely AI-native CRM workflows — natural language pipeline queries, AI-assisted outreach, intelligent enrichment — often find HubSpot's AI additions insufficient.

Before You Start: What to Export#

A complete HubSpot migration requires exporting more than just contacts. Here's the full checklist:

Core CRM Objects#

• Contacts — All contact properties, including custom properties
• Companies — All company properties and associations
• Deals — All deal properties, stages, and associated contacts/companies
• Tickets — If you use HubSpot Service Hub
• Products — If you have a product catalog

Activity Data#

• Notes — All contact/deal notes
• Calls — Call logs and recordings (if enabled)
• Emails — Email activity log (who sent what, when)
• Meetings — Meeting logs
• Tasks — Completed and open tasks

Marketing Assets#

• Email templates — Saved templates from the email editor
• Sequences — Automated outreach sequences
• Workflows — Marketing and sales automation workflows
• Lists — Static and dynamic contact lists
• Forms — Lead capture forms and submissions
• Landing pages — If hosted on HubSpot

Configuration#

• Pipeline stages — Deal stage names, probabilities, and order
• Custom properties — All custom field definitions with types
• Teams and user roles — User setup for the destination CRM
• Email signatures — Sales rep email signatures

How to Export from HubSpot#

Exporting Contacts#

1. Go to Contacts > Contacts
2. Click Actions > Export
3. Select all properties you want to include (include ALL custom properties)
4. Choose CSV format
5. HubSpot will email the export file when ready (can take minutes to hours for large databases)

Critical: Include all custom properties in the export. The default export only includes standard properties. Use "Select all properties" to avoid missing custom fields.

Exporting Companies#

Same process as contacts: Companies > Actions > Export > Select all properties > CSV.

Exporting Deals#

Deals > Actions > Export > Select all properties > CSV.

Important: the deal export doesn't include associated contact names by default. Export with associations enabled, or do a separate export of deal-contact associations.

Exporting Activity (Notes, Calls, Emails)#

Activity data is harder to export cleanly from HubSpot's standard export tools. Options:

Option 1: CRM Export The contact/company/deal exports include some activity data, but not all note content.

Option 2: HubSpot API The Engagements API lets you pull all activity for each contact programmatically. This requires technical work but gives you the most complete export.

Option 3: Browser Agent Tools like DenchClaw's browser agent can log into HubSpot, navigate to contacts, and systematically export activity data without writing code.

Exporting Workflows and Sequences#

Workflows and sequences can't be exported as portable configuration files — they need to be recreated in your destination CRM. Document them:

1. Go to Automation > Workflows
2. Open each workflow and take screenshots or notes of the triggers, conditions, and actions
3. Repeat for Sequences

This documentation becomes your blueprint for recreating automation in the new system.

Common Migration Mistakes#

Migrating Everything at Once#

The temptation is to dump your entire HubSpot database into the new CRM. Resist this. Data you haven't touched in 3 years is probably not worth migrating. A migration is an opportunity to clean up:

• Deduplicate contacts (HubSpot databases accumulate duplicates over time)
• Remove contacts that unsubscribed or bounced years ago
• Archive deals that are more than 2 years old
• Standardize company names and domains

Clean data is more valuable than complete data.

Not Mapping Custom Properties#

HubSpot lets you create unlimited custom properties. Your destination CRM likely has different names for the same concepts. Before importing, create a field mapping document: HubSpot property name → destination field name → data type.

Mismatched field types cause import errors. A HubSpot date field might import as text if the destination format is different.

Ignoring Associations#

Contacts are linked to companies. Deals are linked to contacts and companies. If you import contacts and companies as separate CSVs without preserving these links, you lose the relational structure of your CRM.

Most import tools let you specify a lookup field (usually email for contacts, domain for companies) to re-establish associations. Set this up before importing.

Forgetting the Audit Trail#

In many industries, the history of communications — who said what, when — has compliance implications. Make sure your export includes this data before you leave HubSpot, since you may not have access after your subscription ends.

Choosing Where to Land#

The right destination CRM depends on what drove you away from HubSpot. Here are the main categories:

If Cost Is the Driver#

DenchClaw: Free, open source, MIT licensed. Runs locally on your machine. No per-seat costs, no tier limits. Install with npx denchclaw. See what DenchClaw is for a full overview.

Pipedrive: Cheaper than HubSpot for pure sales CRM. Starts around $15/user/month. Less marketing functionality but better sales pipeline UX.

Zoho CRM: Comprehensive feature set at competitive pricing. Less polished than HubSpot but substantially cheaper at scale.

If Data Ownership Is the Driver#

DenchClaw: Your data is a DuckDB file on your laptop. Full SQL access. No cloud dependency.

SuiteCRM: Self-hosted, open source. Your data lives on your own server.

EspoCRM: Self-hosted, AGPL open source, clean UI, direct database access.

If AI Features Are the Driver#

DenchClaw: Native AI agent with conversational interface. Query your pipeline in natural language via Telegram or web chat.

Salesforce Einstein: More sophisticated AI than HubSpot, but expensive and requires significant setup investment.

Attio: Modern cloud CRM with real AI workflows. Not self-hosted, but cleaner AI integration than HubSpot.

Executing the Migration#

Phase 1: Preparation (Week 1)#

1. Audit your HubSpot usage: which features do you actually use?
2. Select your destination CRM
3. Set up the destination and test with 10 sample contacts
4. Create the field mapping document
5. Document all active workflows and sequences

Phase 2: Export (Week 2)#

1. Export all objects from HubSpot with all properties
2. Export activity data (notes, emails, calls) via API if needed
3. Export workflow and sequence documentation
4. Verify export file completeness — check row counts against HubSpot

Phase 3: Clean and Transform (Week 2-3)#

1. Deduplicate contacts in the export files
2. Normalize field values (standardize company names, clean up dates)
3. Map custom property names to destination fields
4. Split large files into manageable batches (most CRMs import better in chunks of 5,000 rows)

Phase 4: Import (Week 3)#

1. Import companies first (contacts will reference them)
2. Import contacts, linking to companies via domain
3. Import deals, linking to contacts and companies
4. Import activity data if your destination supports it
5. Verify row counts and spot-check data quality

Phase 5: Configuration (Week 3-4)#

1. Recreate pipeline stages in the new CRM
2. Recreate automation workflows
3. Reconnect email integrations
4. Train users on the new interface
5. Set up reporting and dashboards

Phase 6: Cutover (End of Week 4)#

1. Set a cutover date
2. Do a final delta export from HubSpot to catch anything created since the main export
3. Import the delta
4. Cancel HubSpot subscription on the next billing cycle (keep access until the end of the paid period)
5. Download an archive copy of the final export for records

Migrating to DenchClaw Specifically#

If you're moving to DenchClaw, the browser agent approach is the most efficient path:

1. Install DenchClaw: npx denchclaw
2. Tell the agent: "Import everything from my HubSpot — contacts, companies, deals, and notes"
3. The agent opens HubSpot in your browser (using your existing session), navigates to each export, downloads the files, maps the fields to DenchClaw's schema, and imports everything into DuckDB

This eliminates the manual export-clean-import cycle for most standard HubSpot data.

After the Migration#

Don't Cancel HubSpot Immediately#

Keep your HubSpot access for at least 2-3 billing cycles after migration. You'll inevitably discover something you forgot to export — a form submission, an old email template, a list segment. Read-only access is worth the temporary cost.

Audit Data Quality#

Spot-check 20-30 contacts in your new CRM. Do they have the right company? Are their notes present? Do deal associations look correct? Finding data issues early is better than discovering them in a sales call three months later.

Update Your Stack#

When you leave HubSpot, audit what else depends on it: integrations, Zapier flows, email DNS settings (SPF/DKIM if you were sending through HubSpot), form embeds on your website. Each one needs to be updated or migrated.

Frequently Asked Questions#

How long does a HubSpot migration take?#

For a small team (under 5 users, under 10,000 contacts), 2-3 weeks with proper planning. For larger teams with complex workflows and extensive customization, 4-8 weeks is realistic.

Can I migrate HubSpot sequences to another CRM?#

HubSpot sequences can't be exported as portable configurations. You'll need to document them manually and recreate the logic in your destination tool. Most CRMs have similar concepts — email cadences, automated follow-ups — with different UIs.

Will I lose email history when leaving HubSpot?#

Your email history in HubSpot is recorded in the activity log. Export it before leaving. The exported format (CSV or via API) can be imported into CRMs that support activity imports. Email that was sent through HubSpot won't be in your personal email inbox — only the log of what was sent and when.

What happens to HubSpot forms on my website?#

After canceling HubSpot, embedded HubSpot forms will stop working. Before migrating, identify all HubSpot forms on your site and replace them with alternatives (native forms, Typeform, or your new CRM's form tool).

Is it possible to sync HubSpot with a new CRM in parallel?#

Yes, as a transition measure. Tools like HubSpot's native sync, Zapier, or third-party sync tools can pipe new contact creation and update events from HubSpot to your destination CRM during a transition period. This reduces migration risk for teams that can't do a hard cutover.

Ready to try DenchClaw? Install in one command: npx denchclaw. Full setup guide →