Addressing Four Core Problems to Build One Connected Revenue Stack

From mismatched data and attribution gaps to a clean, bi-directional system of record!

Background

A growing SaaS company came to Zola Consulting with a common but complex problem: they were running HubSpot as their marketing automation platform and Salesforce as their CRM — but the two systems were not working cohesively. The integration was in its early stages of being set up but needed proper architecture decisions in place. We needed to address mismatched data, attribution blind spots, and a marketing-to-sales handoff that had a trackable accountability layer.

The engagement also included working with migrated legacy data; historical records brought into the new system also needed source attribution — a notoriously difficult problem to solve cleanly.

The Challenges

Challenge 1: Top-of-Funnel Tracking & Source Attribution

• A few lead capture channels existed (forms for different use cases, legacy data uploads, manual UI data entry, etc.) — each with different tracking data points.
• Due to data migration and an emerging business process, consistent source attribution needed to be established, so the business could have a reliable way of knowing where all new leads and existing contacts came from.
• Legacy data uploaded further complicated the picture, as historical records arrived with no original source info attached.

Challenge 2: Integration Errors & Field-Level Sync Conflicts

• Integration errors at the object level (Contacts, Companies, Deals) resulted in an inconsistent data feed between HubSpot and Salesforce.
• Field-level sync conflicts caused data to be overwritten unpredictably — with no rules defining which system should be the source of truth for each data point.
• A structural mismatch between platforms compounded the issue: Although HubSpot supports one-to-many Contact to Company relationship, when it came to the integration matching rules for Companies, HubSpot assumed a one-to-one Contact-to-Company relationship match which didn’t always match with Salesforce’s one-to-many scenario — causing duplicate records to be created on sync.

Challenge 3: Leaky Marketing-to-Sales Handoff

• The critical handoff point from Marketing (MQL) to Sales (SQL) needed a validation mechanism as manual validation for each Lead between both systems was time consuming and not scalable.
• Leads had a high probability of falling through the cracks with no visibility into whether a passed lead had been successfully picked up in Salesforce and assigned to a sales owner.

Challenge 4: No Bi-Directional Data Feed for Attribution Reporting

• Sales activity, follow-ups, and closed won data were not feeding back to HubSpot.
• Marketing had no visibility into which campaigns or sources were driving actual revenue outcomes — beyond top-of-funnel activity.

The Solutions

Solution 1: Custom Source Attribution for Legacy & New Data

• Since original source fields are read-only and cannot be overwritten, creating a custom source field was a solution to capture the original source for all legacy records.
• From a reporting standpoint, both the custom field and HubSpot’s original source field were usable, giving the reporting layer a complete and accurate picture of lead origins — both historical and new.
• Tracking was implemented across all active lead capture channels to ensure every new interaction is attributed from the very first touch.
  

Solution 2: Object Architecture Review & Field-Level Sync Rules

• A full review of which objects actually needed to be connected between the two platforms was conducted — eliminating unnecessary syncs that were contributing to mismatches.
• The one-to-one vs. one-to-many relationship conflict between Salesforce and HubSpot’s Company matching was identified and factored into the decision of what data was actually necessary to sync while respecting both platforms’ structural requirements. Since Companies are created during Lead conversion in Salesforce, and Company Name and profile info was part of the Contact record, the Company level sync was actually not necessary. The Contact record was populated with the additional Company data needed to sync to HubSpot.
• Field-level data sync rules were established for each data point, designating a source system. This ensures the correct system always wins — with no unintended overwrites.

Solution 3: Leak-Proof MQL Handoff Validation

• A validation view was built within HubSpot’s Marketing platform to surface all leads passed from Marketing to Sales as MQLs.
• The view includes the Salesforce CRM record ID and assigned Sales Owner for each lead. Any record missing these fields is immediately flagged as a handoff failure — giving the team real-time visibility into leads that have fallen through.
• This created an accountability layer between Marketing and Sales with zero engineering overhead.

Outcomes

Zola Consulting LLC • HubSpot Partner & Consultant • Salesforce Partner & Consultant • Upwork Expert-Vetted Top 1%