HubSpot Migration
The migration is done. Data is in HubSpot. The team is trained. Now the CMO opens the dashboard and the numbers do not look right. Not wrong, exactly. Just different. And different is a problem when the board meeting is in two weeks.
This is the most predictable post-migration crisis in B2B revenue marketing. HubSpot and Salesforce measure the same outcomes differently. Understanding those differences before go-live is the difference between a smooth transition and a reporting credibility crisis.
Three things change the day you migrate from Salesforce to HubSpot. All three affect reporting. None of them are problems if you know they are coming.
Salesforce uses campaign member records to attribute revenue. HubSpot uses a combination of original source tracking, contact properties, and attribution reports (available in Marketing Hub Professional and Enterprise). The output can look very different even when both systems are tracking the same reality.
The first time a CMO runs HubSpot's attribution report and sees different numbers than Salesforce produced, the instinct is to assume the data migrated incorrectly. Often the data is correct. The model is just different.
Salesforce's opportunity forecasting uses a combination of close date, probability, and forecast category. HubSpot's deal forecast uses close date, deal stage probability, and deal score (if configured). The two systems will produce different forecast numbers for the same pipeline if you do not align the deal stage probabilities during configuration.
Salesforce logs calls, emails, and meetings as tasks and events, with separate objects for each. HubSpot logs them as activities within the contact and deal timeline. The count methodology differs. A meeting with 3 attendees counts differently in Salesforce than in HubSpot. Sales managers will notice this within the first two weeks.
HubSpot is not worse than Salesforce at reporting. It is different. And for most mid-market and growing enterprise B2B companies, several aspects of HubSpot reporting are meaningfully better.
HubSpot Reporting Advantages: Session-to-contact attribution is native in HubSpot. Every form submission, live chat, and tracked email click links automatically to contact records and deal activity. In Salesforce, this requires custom coding or a separate marketing attribution tool. HubSpot's out-of-the-box contact timeline is the most complete behavioral record most B2B revenue teams have ever had access to.
HubSpot's native web tracking connects every page visit, form submission, and CTA click directly to contact records. Salesforce requires a separate marketing automation integration to get equivalent data. This is not a marginal improvement. It eliminates an entire category of attribution gap.
HubSpot's attribution report ties marketing touchpoints directly to deals in the same interface. In Salesforce, connecting campaign history to opportunity revenue requires custom reports or a BI tool. For most B2B companies, the HubSpot version is meaningfully easier to explain to a CFO.
HubSpot's custom report builder allows non-technical users to build multi-object reports without writing SOQL. Revenue operations teams that needed a Salesforce admin for every new report can now self-serve most reporting needs in HubSpot.
Honesty about this is the most important thing a migration partner can provide. There are reporting capabilities Salesforce has that HubSpot does not fully replicate. Most do not affect most companies. Some affect certain companies significantly.
Salesforce Reporting Capabilities HubSpot Does Not Match: Salesforce's Einstein Analytics (now Tableau CRM) is a BI-grade analytics layer that HubSpot does not attempt to replicate. For companies using Einstein for advanced revenue forecasting, territory analysis, or complex quota modeling, HubSpot's native reporting is not equivalent. These companies typically add a BI layer (Looker, Tableau, Power BI) on top of HubSpot after migration.
Salesforce has native territory management with territory-based pipeline and quota reporting. HubSpot has teams and team-based reporting, which approximates territory reporting for most mid-market companies but lacks the hierarchical complexity Salesforce supports for enterprise organizations with complex territory structures.
Salesforce supports split credit across multiple sales reps on a single opportunity. HubSpot does not have native split credit functionality. For sales compensation models built on split revenue, this gap matters.
Salesforce supports fully custom fiscal year periods. HubSpot supports fiscal year start month configuration but not fully custom period structures. Companies with non-standard fiscal calendars may find HubSpot's time-period reporting less flexible.
| Reporting Capability | Salesforce | HubSpot | Impact of Difference |
|---|---|---|---|
| Multi-touch attribution | Via campaigns + custom reports | Native (Marketing Hub Pro+) | HubSpot wins for most B2B |
| Web analytics integration | Requires MA integration | Native tracking, native reports | HubSpot significantly better |
| Pipeline forecasting | Forecast categories + Einstein | Stage probability + deal score | Comparable with configuration |
| Custom report builder | Powerful, requires SOQL for complex | No-code, multi-object | HubSpot faster for non-technical |
| Territory management | Full hierarchy, native | Teams-based, less flexible | Salesforce wins for complex org |
| Revenue splits | Native split credit | Not supported natively | Gap for split-comp models |
| BI layer (advanced analytics) | Tableau CRM (Einstein) | Integrates with Looker/Tableau/PBI | Salesforce wins for BI power users |
| Activity logging and timeline | Tasks and events | Unified timeline, richer context | HubSpot better for sales context |
The first 90 days after migration, someone will ask why HubSpot shows a different number than Salesforce for the same metric. Here is the framework for answering that question without losing credibility.
Run the same date range in both systems for a metric you trust (total contacts created in Q1, for example). If the numbers match, the data migration is clean and the difference you are seeing is a methodology difference. If the numbers do not match, there is a data migration gap that needs diagnosis.
For every key metric that produces a different number in HubSpot versus Salesforce, write a one-paragraph explanation of why. This documentation becomes the answer to every "why is this number different" question for the next 12 months.
Within 90 days of go-live, the organization should align on HubSpot as the system of record. This means HubSpot numbers are correct by definition, and historical Salesforce comparisons are labeled as such. The longer a team compares HubSpot to Salesforce, the longer HubSpot's credibility is in question.
"The CFO who asked 'why is HubSpot showing a different number than Salesforce?' in month one became the CFO who defended the HubSpot numbers to the board by month six. The key was explaining the methodology difference, not defending the data."
Planning a Migration or Building Post-Migration Reporting?
TPG configures HubSpot reporting for CMOs and CROs who need board-ready dashboards from day one. Let us show you what the reporting should look like before you migrate.
Talk to a Reporting Specialist
Why do HubSpot and Salesforce show different numbers for the same metric after migration?
Three reasons: the attribution models use different logic and count touchpoints differently, deal stage probability assignments differ between the two systems so forecast numbers diverge, or there is an actual data migration gap. The fastest diagnostic is to run a clean metric (contacts created in a specific quarter) against both systems. If that matches, you have a methodology difference to document. If it does not match, you have a data problem to fix.
Does HubSpot have better reporting than Salesforce?
HubSpot has better reporting for most mid-market B2B companies in three specific areas: native web analytics integration that ties page visits and form submissions directly to contact records, deal-level marketing attribution without requiring a separate BI tool, and a no-code custom report builder that does not require SOQL. Salesforce wins for territory-based reporting, revenue splits, and advanced analytics through Tableau CRM for enterprise organizations with complex quota models.
What HubSpot reporting capabilities require additional configuration after migration?
Pipeline forecasting requires aligning deal stage probability percentages to match the logic your team used in Salesforce. Attribution reporting requires the correct property architecture (designed pre-migration). Activity reporting requires understanding that HubSpot counts activities differently from Salesforce tasks and events, and documenting that methodology difference for sales managers before they surface it themselves.
How do we handle the "new baseline" conversation with our CFO after migrating to HubSpot?
Within 90 days of go-live, align on HubSpot as the system of record. For every key metric that diverges from Salesforce, provide a one-paragraph explanation of why, which system is more accurate for that use case, and when the comparison period ends. The CFO who understands the methodology difference becomes an advocate for the new numbers. The CFO who does not understand it becomes an ongoing source of reporting credibility questions.
Does HubSpot support revenue splits for sales compensation?
Not natively. HubSpot does not have split credit functionality across multiple sales reps on a single deal. This is a known gap for organizations with split-compensation models. Companies that need revenue split reporting typically address it through a BI layer (Looker, Tableau, or Power BI) connected to HubSpot, or through a custom property structure that approximates splits for reporting purposes.
How long does it take for HubSpot AI forecasting features to be accurate after migration?
HubSpot's AI forecasting and deal scoring features require 12 or more months of native HubSpot deal history to calibrate accurately. For companies that migrate with Salesforce deal history, the model has data to work with but needs time to learn HubSpot-native behavioral signals. Plan to use the AI forecasting features as a complement to manual forecast judgment for the first year post-migration.
The Pedowitz Group | pedowitzgroup.com | Revenue Marketing Experts Since 2007