Migrating From HubSpot or Salesforce to a Custom CRM: What to Expect
Migrating from HubSpot or Salesforce to a custom CRM means sorting your data into what migrates as-is, what transforms, and what you rebuild by hand. Here are the export limits, a move-off ledger, and a realistic timeline for a 10 to 15 person team.
Migrating from HubSpot or Salesforce to a custom CRM splits your data into two piles: records that export in an afternoon and history you rebuild by hand. Contacts, companies and open deals move cleanly. Stage-entry dates, logged inbox email, workflows and reports don't, and they decide how long the switch really takes.
Who this is for: a small business owner with roughly 5 to 20 people, currently paying for HubSpot or Salesforce, who is weighing a custom build and wants to know what the move involves before talking to anyone.
- A HubSpot record export gives you current property values and associations, but not the full activity history behind each deal or the bodies of every logged email.
- Salesforce's Data Export Service runs weekly on Enterprise, Performance and Unlimited editions and only every 29 days on Professional Edition, so your final export date needs planning.
- Salesforce's Master Subscription Agreement gives you 30 days after termination to request your data, which makes export timing a contract question as well as a technical one.
- Workflows, sequences, Flows, reports and integrations never export from either platform; they are rebuilt by hand in the new system.
- For a 10 to 15 person team, the controlling risk in a migration is data lock-in and lost history, not per-seat licensing math.
What Do You Actually Export From HubSpot or Salesforce Before You Start?
You export every object as structured data: contacts, companies or accounts, deals or opportunities, activities, custom properties and the association IDs that tie them together. The record export is the easy part. The parts that cause trouble are activity history, stage timestamps and the time windows each platform puts around exports.
Here's the naive version of this comparison: "it's all just CSVs, we'll download them and load them." That works for most of the records. What doesn't come along is the stuff your team actually relies on to sell, which is why it's worth an inventory before anyone writes code. If you're still deciding whether to leave at all, our 10-point checklist for outgrowing a generic CRM is a better first stop.
HubSpot's export limits
HubSpot's Export Records documentation spells out the mechanics. You can run up to 300 exports in a rolling 24-hour window and up to three at once; anything beyond that queues. CSV and XLSX exports with more than 1,000,000 rows arrive as multiple files, and XLS files split at 65,535 rows.
For a small business, none of those caps will bite. A 12-person team rarely has more than tens of thousands of contacts. The bigger issue is scope: HubSpot describes the record export as downloading "current property values and associations." Current. Not the trail of how a record got there.
Salesforce's export cadence and the 30-day window
Salesforce gives you two native routes: the Data Export Service in Setup and Data Loader for bulk pulls. Per Salesforce's Trailhead module on data export, weekly exports are available on Enterprise, Performance and Unlimited editions. Professional and Developer editions can only generate a backup every 29 days.
Two more dates matter. Export files stay available for 48 hours after Salesforce generates them, then they're deleted. And Salesforce's Master Subscription Agreement says it will make your data available for export if you request it within 30 days after termination. Treat that window as a safety net, not your plan.
What the export files leave out
So what's missing? Mostly the context around the records:
- Email bodies logged from connected Gmail or Outlook inboxes (often partial, sometimes just metadata)
- The full history of stage changes, especially for stages you deleted when restructuring a pipeline
- Calls, notes and tasks, which usually need an API pull rather than a standard record export
- Anything that's logic rather than data: workflows, sequences, Flows, Apex, validation rules, report definitions
The Move-Off Ledger: What Migrates, What Transforms, and What You Rebuild
Every item in your CRM falls into one of three buckets: it migrates as-is, it transforms into a new shape, or you rebuild it by hand. Contacts and companies mostly migrate. Stage history and associations transform, and workflows, reports and integrations are always rebuilt.
This is the real comparison. Not HubSpot versus custom, but "what survives the trip" versus "what doesn't." The table below is the ledger we'd fill in with you during an audit, and you can do a rough version yourself before talking to any developer.
| Item | Migrates as-is | Transforms | Rebuild by hand |
|---|---|---|---|
| Contacts | Yes, after dedupe and cleanup | Owner and lifecycle values remap to new users and stage names | No |
| Companies / accounts | Yes | HubSpot is contact-centric, Salesforce is account-centric; your new schema picks one model | No |
| Deals / opportunities (current state) | Yes: amount, close date, current stage | Stage names map to your new pipeline | No |
| Deal stage history and stage-entry timestamps | No | Exported date columns load into custom date fields or a stage-history table | Deleted stages are usually gone |
| Associations (deal to contact, contact to company) | Not reliably | Rebuilt from legacy record IDs in a join table | Re-link any that fail validation |
| Notes, calls, tasks | Partly, via API | Salesforce Tasks and Events need WhoId and WhatId links re-pointed | No |
| Connected-inbox email history | Often incomplete | Archive bodies separately and match by email address | Accept gaps, or keep a read-only archive |
| Custom properties / fields | Values, yes | Picklists and field types get re-typed | Field definitions recreated |
| Workflows, sequences, Flows, Apex | No | No | Yes, as code or automation workflows |
| Reports and dashboards | Underlying data only | No | Yes, definitions don't export |
| Third-party integrations | No | No | Yes, reconnected through APIs or webhooks |
| Users, roles, permissions | User list | Roles map to new roles | Permission rules rebuilt |
Trap 1: associations that don't survive
Associations are the line item people skip. Records and relationships travel separately: the export lists association IDs, but every one of those links has to be matched to a new record ID on import. Any link pointing at a record you skipped, merged or deduplicated simply fails. You can end up with every contact and every deal present and far fewer of them connected.
The fix is boring and reliable. Keep each record's old ID in a legacy-ID field, load associations as a separate step, then count orphaned deals before go-live.
Trap 2: stage history
HubSpot tracks "date entered" values per stage, and you can export them as columns. But if you ever deleted or merged stages, that history may already be gone. It's a question raised in the HubSpot Community thread on restructuring deal stages, where the answer is that most reporting survives but new stages only collect data going forward. In a custom CRM, those dates land in a stage-history table so sales-cycle reports keep working. We covered what that makes possible for alerts in what HubSpot can't do with deal stage alerts.
Trap 3: inbox email
Email logged from a connected inbox is the item owners ask about most and agency guides answer least. Pull it through the API early, spot-check 20 or 30 records against the original mailbox, and decide whether gaps are acceptable or whether you need a separate archive.
How Long Does Migrating From HubSpot or Salesforce to a Custom CRM Take?
For a 10 to 15 person team, plan on roughly 8 to 12 weeks from first export to cancelling the old subscription. The core build is the longest stretch, and the audit, workflow reconnection and parallel run wrap around it.
Our own custom CRM builds typically run 4 to 8 weeks for the first phase, which replaces the single most expensive tool in the stack first. That's our published service commitment, not an industry average, and it's delivered in phases rather than as one big launch.
Workflow automation work that connects what is left of the old system typically runs 1 to 3 weeks, separate from the CRM build itself. That's the piece people forget. If you keep a form tool, an email platform or an accounting system, something has to wire them to the new CRM.
Here's how we'd sequence it for a small team:
| Phase | Duration | What happens | Who owns it |
|---|---|---|---|
| 1. Audit and export | About 1 week | Fill in the ledger, run full exports, test an API pull of activities, archive inbox email | You and the developer |
| 2. Core CRM build | 4 to 8 weeks | Schema, pipeline, test data loads, first-phase features, weekly reviews | Developer |
| 3. Reconnect kept tools | 1 to 3 weeks, overlapping the end of phase 2 | Forms, email, accounting and calendar wired in through workflows | Developer |
| 4. Parallel run | About 2 weeks | Both systems live; your team compares records and reports | Your team |
| 5. Cutover and training | About 1 week | Final delta export, role-based training, old CRM set to read-only | You |
Now, the 2-week parallel run is where small teams save or lose the most. Shorter, and you find problems after you've cancelled. Longer, and people quietly keep using the old system. Our week-by-week walkthrough of the custom CRM build process goes deeper on phase 2.
Why Can't You Just Export Your Data and Go?
Because a SaaS CRM stores your data in its format and your logic in its engine, and only the first one comes with you. You can download the records, but the rules that made them useful stay behind.
Our custom-build FAQ draws the contrast directly. With a SaaS vendor, leaving can mean you lose your data and workflows with no migration path. Code you own is documented and version-controlled in Git, so a developer handoff is straightforward.
Here's the thing most cost comparisons miss. Every top-ranking TCO table targets bigger companies: break-even points at 50 to 100 users, three-year models at 30 seats, healthcare examples in the millions. At 10 to 15 people, per-seat licensing is real money but rarely the deciding number. What decides it is what you'd lose if you had to leave quickly: the 29-day export cadence on Salesforce Professional, the 48-hour download window, an activity history that needs API work to extract.
That's lock-in at small-business scale. And it compounds. The longer you run on a platform, the more of your process lives in workflows you can't export. If you do build, the integration patterns post shows how to keep the new system open to other tools from day one.
What Does Migrating From HubSpot or Salesforce to a Custom CRM Cost?
The cost has three parts: the build itself, the subscription you keep paying during the overlap, and your team's time during the parallel run. Most guides price only the first.
Say your 12-person team pays $100 per seat per month (a hypothetical round number, not a vendor quote). That's $1,200 a month, or $14,400 a year. A 3-month overlap from first export to cancellation adds $3,600 in subscription cost alone, before counting the hours your team spends double-checking records in two systems.
Third-party models give you a reality check on the build side. Vizologi's build-vs-buy analysis puts three-year cost at 30 seats at $117,700 for HubSpot, $127,000 for Salesforce and $148,800 for custom, with buying winning at that size and the math flipping around 60 seats. It also budgets 15% to 25% of build cost per year for maintenance and a $10,000 line for migration.
So for a small team, the build rarely wins on licensing alone. It wins when the fit problem is the expensive part. Rain Automation's Custom CRM Build service was written for exactly that reader: "Businesses that have tried configuring HubSpot, Salesforce, or GoHighLevel and spent thousands on consultants only to end up with something that still doesn't fit." We quote after scoping your ledger, because the rebuild column drives the price more than seat count does.
To run your own numbers, use the CRM ROI calculation guide and the custom CRM vs SaaS cost analysis. If you'd rather walk through your exports with someone who builds these, get in touch and we'll go through the ledger with you.
Cost figures in this section are illustrative planning numbers and third-party estimates, not quotes or guarantees. Check current pricing and contract terms with HubSpot or Salesforce before you give notice.
When Should You Stay on HubSpot or Salesforce Instead?
Stay if your process fits the platform with light configuration, your team actually uses it, and your main frustration is price rather than fit. A custom build fixes workflow mismatch; it doesn't fix low adoption.
The most common advice on r/smallbusiness and r/CRM is to start simple, with HubSpot's free tier or Pipedrive, because the real friction for small teams is getting people to use the CRM at all. That advice is right more often than agencies like to admit. Some teams abandon a CRM mid-switch and drift back to spreadsheets, which is worse than either option.
The SBA's checklist for choosing business software makes a related point from the buyer's side: weigh ease of use, how well the software integrates with what you already run and the vendor's upgrade path, and be wary of software more complex than your business needs.
Stay on HubSpot or Salesforce if:
- Your pipeline matches their default objects with a few custom fields
- Fewer than half your seats log in weekly (fix adoption first)
- You haven't documented your process well enough to describe it to a developer
Consider a custom build if:
- You've paid for configuration or consultants and still work around the tool every day
- Your process depends on objects or steps the platform can't model without hacks
- Losing your workflow logic on exit is a risk you're no longer willing to carry
Our build vs buy CRM framework lays out the six questions we ask before quoting, including the ones that lead to "don't build."
What Should Be on Your CRM Data Export Checklist?
Before you call anyone, confirm you can export every object, pull activity history, keep legacy IDs and know your contract dates. If you can tick these off, the migration itself becomes predictable.
- List every object you use, including custom objects and the ones nobody has touched in a year.
- Run a full test export now, not at cancellation. On Salesforce Professional, note when your next 29-day export is available.
- Pull a sample of calls, notes and emails through the API and compare 20 or 30 against the source.
- Export stage "date entered" values as columns for every deal.
- Make sure every export includes record IDs and association IDs.
- Write down every workflow, sequence and integration (these get rebuilt, so the list is your spec).
- Check your renewal date and notice period, and on Salesforce, the 30-day post-termination request window.
- Decide who on your team owns the parallel run.
Item 6 doubles as a hiring tool. Hand it to any developer you're vetting, along with our 10 questions to ask before hiring a custom CRM developer.
Frequently Asked Questions
These are the questions small business owners ask most before leaving HubSpot or Salesforce for a custom CRM. Each answer stands on its own.
If your question is about the build itself rather than the move, our custom development services page covers scope and process.
Can I export my HubSpot email history before switching CRMs?
Partly. HubSpot's standard record export gives you current property values and associations, not the full body of every logged email. Pull email and other activity history through HubSpot's API before you cancel, then spot-check emails logged from connected Gmail or Outlook inboxes, because those are the records most likely to come back incomplete.
What happens to my deal stage history when I migrate to a new CRM?
It doesn't move on its own. Export HubSpot's "date entered" stage values or Salesforce's opportunity history as columns, then load them into custom date fields or a stage-history table in the new CRM. History for stages you deleted before migrating is usually unrecoverable, so export before restructuring anything.
How long does it take to build a custom CRM?
A first-phase custom CRM build typically takes 4 to 8 weeks under our published service commitment. Add about a week for audit and export up front, 1 to 3 weeks of workflow automation to reconnect the tools you keep, and roughly two weeks of parallel running before you cancel the old subscription.
Is it cheaper to build a custom CRM than to keep paying for HubSpot or Salesforce?
Not always, especially for small teams. Vizologi's three-year model found HubSpot and Salesforce cheaper than a custom build at 30 seats, with the math flipping near 60 seats. A custom build pays off when working around a poorly fitting tool costs more than the subscription, or when owning your data and logic matters.
What data can't be migrated out of Salesforce?
Logic is what can't leave Salesforce. Apex code, Flows, validation rules, report definitions and permission sets only run inside Salesforce, so they are rebuilt. Records export through the Data Export Service or Data Loader, but Tasks and Events need their WhoId and WhatId links re-pointed to the new records.
Do I need to keep paying for HubSpot or Salesforce while a custom CRM is being built?
Yes, plan on it. Your team keeps working in the old CRM during the build and the parallel run, so cancel only after a final delta export and a verification pass. Salesforce gives you 30 days after termination to request your data, but treat that as a safety net, not your export plan.
How do I avoid losing deal-to-contact links during migration?
Export association IDs with your records and load them as a separate step. Store each record's original HubSpot or Salesforce ID in a legacy-ID field, then run a query counting deals with no linked contact before go-live. If that count isn't zero, fix the links before your team starts working in the new system.