Salesforce to HubSpot migration: what history gets left behind and who decides
A Salesforce to HubSpot migration typically moves accounts, contacts and deals but leaves some older activities, logged emails, notes and custom objects in the source org, depending on tool and plan. Consultants can flag that left-behind history to the owner before the Salesforce contract ends, so it is exported or assessed rather than deleted.
What history gets left behind in a Salesforce to HubSpot migration?
Migrations usually carry accounts, contacts, deals and a selected slice of activity, and leave much of the rest in the source org: older activities, logged emails, notes, attachments, custom objects and field-level history. The exact limits depend on the migration tool, the objects mapped and the HubSpot plan, so confirm them in each vendor's documentation rather than assuming. What is not migrated stays in Salesforce, which is why the cancellation date matters.
For a CRM consultant, the useful question is not "did it migrate?" but "what will exist only in the old org, and who decides its fate when the contract ends?"
Which records commonly stay in the source org?
| Record type | Why it is often left behind | Why it matters for the company |
|---|---|---|
| Task and event history | Volume, mapping effort, activity-type differences | Shows how deals actually progressed |
| Logged emails and attachments | Storage and association complexity | Rich context on negotiations and objections |
| Notes and chatter posts | Mapped to a single notes field, if at all | Qualitative record of customer conversations |
| Custom objects | No equivalent object in the target | Often hold the company's unique workflow |
| Opportunity stage history | Target tracks stages differently | The path from first touch to win or loss |
| Closed or lost deals | Excluded to keep the new CRM clean | Outcomes are the most useful part of the record |
| Reports and dashboards | Rebuilt, not moved | Reflect how management read the business |
Treat the table as a prompt for the scoping call, not as a statement about any tool's limits.
What makes this history valuable to AI buyers?
AI developers building agents need records of real work: multi-step sales cycles, decisions and their outcomes. A CRM with years of connected opportunities, activities and notes captures how a company qualified, negotiated and closed. Outcomes, structure and links to email and support systems are what separate it from an exported contact list.
Whether any given company's CRM is licensable depends on rights, privacy and consent. Customer personal data raises questions that SourceX and the company address with de-identification and redaction rules agreed before any work begins.
The 4-point migration flag
Add this to your discovery and cutover documents.
- Left-behind list. Record, by object name only, what the migration plan does not move.
- Contract date. Note when the Salesforce subscription ends and whether the org enters read-only or deletion afterwards. The Salesforce contract-end explainer covers the owner-facing question.
- Export owner. Name who at the client holds a full backup or export, and where it lives.
- Decision owner. Identify the authorized sponsor who decides whether the old org is kept read-only, exported or assessed.
If a client wants to keep the old org alive for a period, a read-only or reduced license may be an option; confirm the options and cost with Salesforce, not with this page.
When should the consultant raise it?
| Project phase | Question to ask the owner |
|---|---|
| Discovery | "What do you want to do with deal history we are not migrating?" |
| Data mapping sign-off | "Are you comfortable that these objects stay behind?" |
| Pre-cutover | "Has someone exported the old org, and who owns that export?" |
| Contract renewal date | "Should the old org stay in read-only mode until we have assessed it?" |
| Post-go-live | "Do you want an introduction to a service that assesses records for licensing?" |
Related migrations create the same issue elsewhere in the stack. See Box or Dropbox to SharePoint, Google Workspace to Microsoft 365 and Jira and Confluence cloud migration for the parallel cases.
How does the introduction work?
You do not need access to the company's data. You flag the left-behind history and offer an introduction if the owner is interested.
- The authorized sponsor agrees to an introduction.
- You submit the referral or share your referral link so the company applies at sourcex.si/apply with your credit attached.
- SourceX qualifies the company on size, history, data breadth and rights.
- The company completes a data inventory, helped by the data inventory builder.
- Price and terms are agreed, buyers review, and nothing is binding until signed.
- If the deal closes, the company is paid; any partner reward becomes payable only after the buyer pays and SourceX receives its fee.
Partners never export, upload or describe confidential records. A migration project does not give you permission to use the client's data for anything else.
How do rewards work for a CRM consultant?
Partners earn 25% of the eligible platform fees SourceX actually collects from the referred company's licensing deals, capped at $100,000 per referred company. The reward is paid only after the buyer pays and SourceX receives its fee; a lead, meeting or signed agreement alone does not trigger payment, and no reward is guaranteed. The reward is a share of SourceX's fee and is never deducted from what the company receives. See the CRM consultant referral page and the program terms. If your implementation contract limits referral fees from client engagements, check it first.
Limits
The history is not worth discussing for a company under 50 full-time employees at peak (contractors excluded), with only a few years of data, or with mostly consumer personal data and no basis to license it. Also skip clients whose CRM mainly holds their own customers' data under restrictive terms.
Next step
Add the 4-point flag to your next migration plan. When a qualifying client wants to explore, register as a partner and introduce them.
- Step 1Share your linkSend your personal link to a company you know.
- Step 2Company appliesThe company applies itself at /apply.
- Step 3Buyer selects and paysThe buyer selects and pays for the data and SourceX receives its fee.
- Step 4You get your rewardYour share of SourceX fees becomes payable.
Common questions
Does HubSpot import all Salesforce activity history?
Not necessarily. What carries over depends on the objects you map, the migration tool and your HubSpot plan, so check HubSpot's current import documentation for your case. Anything not migrated stays in Salesforce and is at risk once the subscription ends.
Should I keep Salesforce read-only after migrating?
It is an option some teams ask about while the team verifies the new system, and a way to avoid losing unmigrated history. Availability and cost depend on your Salesforce agreement, so confirm with Salesforce. The owner decides whether keeping it is worth the fee.
Is old CRM data valuable if it is messy?
Structure and outcomes matter more than neatness. Years of linked opportunities, activities and notes showing how deals were won or lost are the useful part. Whether a specific company's CRM qualifies is assessed by SourceX during qualification and inventory.
What about customer personal data inside the CRM?
It is handled through de-identification and redaction requirements agreed with the company before any work begins. Data mainly made of consumer personal information without a licensing basis is a red flag and may not be suitable.
Can I use client CRM data to find other prospects?
No. A migration engagement gives you access for the project only. Partners make introductions with the owner's consent and share basic fit information; they never export, upload or describe confidential records.
What if the client is moving the other way, HubSpot to Salesforce?
The same logic applies in reverse: engagement history, notes and custom properties may not map one-to-one, and the HubSpot account may be downgraded or closed. Ask the owner who holds an export and whether the old account will be preserved.
Related pages
- What happens to Salesforce data when the contract ends, and what to do before it does
- Box or Dropbox to SharePoint migration: what gets left behind
- Google Workspace to Microsoft 365 migration: what old mail gets left behind
- Jira and Confluence cloud migration: what happens to old projects and spaces
- Build a metadata-only business data inventory
- Referral opportunities for CRM consultants
Free resources
- Business valuation calculator — Enterprise and equity value from EBITDA, your multiple, cash and debt.
- Portfolio data opportunity scanner — Screen several companies in one session.
- Working capital calculator — Net working capital, current ratio and quick ratio.
- All free tools · MCP resource center
By SourceX Partnerships Team · Published 2026-10-09 · Updated 2026-10-09
Know a US company with valuable proprietary data?
Become a referral partner from anywhere we support, get your link and introduce an owner or authorized decision-maker.
Refer a company →I own a business
Explore licensing your company's data to AI developers worldwide. Start a short assessment; no uploads needed.
Start an assessment