Gong is a revenue intelligence platform that records, transcribes, and analyzes sales calls — and when it’s connected properly to your CRM, it becomes significantly more powerful. But “connected properly” is doing a lot of work in that sentence. Teams that implement Gong before cleaning up their CRM often find that the integration creates noise instead of signal.
Before you roll out Gong, there are a handful of CRM-side tasks that will determine whether the integration actually helps your team or just adds another tool they have to manage. This checklist is based on the common issues teams run into when the prep work is skipped.
Why CRM Preparation Matters Before Implementing Gong
Gong pulls data from your CRM — deal stages, contact names, company names, deal values, close dates — to contextualize what’s happening in recorded calls. If those CRM fields are inconsistent or inaccurate, Gong will surface inaccurate analysis. You’ll see deals tagged to the wrong stage, calls matched to the wrong contact, or activity insights that don’t reflect reality.
The goal of preparing your CRM before implementing Gong is to make the data that Gong reads trustworthy. That means your pipeline stages, contact records, and deal ownership fields need to reflect what’s actually happening in your sales process — not what they were set to six months ago and never updated.
CRM Preparation Checklist for Gong Rollout
1. Audit and Clean Your Deal Stages
Gong uses deal stage data to categorize conversations and track movement through your pipeline. If you have deal stages that no one uses, stages with inconsistent naming, or deals sitting in “Proposal” that should have been closed months ago — clean this up first.
- Archive or remove unused pipeline stages
- Standardize stage names across teams if you have multiple pipelines
- Move stale deals to Closed Lost or Closed Won so active pipeline reflects reality
2. Verify Contact and Company Record Accuracy
When Gong logs a call, it tries to match it to a contact in your CRM using email addresses and phone numbers. Duplicates and missing data break this matching.
- Deduplicate contact records — most CRMs have a built-in merge tool
- Ensure email addresses are present and correct for active prospects
- Check that phone numbers are formatted consistently (or remove ones that are junk)
3. Confirm Deal Ownership Is Up to Date
Gong assigns insights to rep performance based on deal ownership in your CRM. If a rep left six months ago and their deals were never reassigned, Gong will attribute calls to a ghost.
- Reassign open deals from departed reps to active owners
- Confirm that deal owner matches the rep who is actually running the account
4. Set Up Required Fields for Gong Triggers
Many teams configure Gong to trigger alerts or workflows based on CRM field values — like when a deal reaches a certain stage or when a close date is within 30 days. Those triggers are only useful if the fields they rely on are filled in consistently.
- Identify which CRM fields Gong will reference in your intended workflows
- Make those fields required in your CRM layout going forward
- Backfill missing values for active deals where possible
5. Align on CRM Update Expectations With Your Sales Team
Gong’s deal intelligence is only as current as your CRM. If reps aren’t updating deal stages and close dates regularly, Gong’s risk alerts and pipeline forecasts will be inaccurate.
- Set clear expectations that CRM hygiene is part of using Gong
- Consider adding a CRM update step to your post-call checklist
- Use Gong’s CRM writeback features to reduce manual entry where possible
6. Review Your CRM Integration Permissions
Gong connects to your CRM via OAuth (for HubSpot and Salesforce) or API key. The account used for the connection determines what data Gong can read and write.
- Use an admin-level service account for the integration — not a personal rep login that could be deactivated
- Confirm the connecting account has access to all pipelines and deal records you want Gong to see
- Document which account is used so there’s no mystery if the connection breaks later
After the CRM Is Clean: Timing the Gong Rollout
Gong needs historical call data to start surfacing meaningful patterns. That means the longer you wait to roll it out, the longer you wait to get insights. Once your CRM prep is done, there’s no benefit to delaying.
A reasonable rollout sequence: connect Gong to your CRM, run a pilot with one or two reps for two weeks, review the data quality together, then expand to the full team. That pilot period will surface any remaining CRM data issues before they scale.
Teams that skip CRM prep before implementing Gong usually come back to it anyway — just after they’ve already been confused by inaccurate data for a month. Doing it first is the faster path.
How to Connect Gong with HubSpot or Salesforce for Pipeline Insights
Once your CRM is clean, the actual connection between Gong and your CRM takes less time than the preparation. Here is how both integrations work.
Connecting Gong to HubSpot
- In Gong, go to Settings → Integrations → CRM and select HubSpot
- Authenticate with a HubSpot admin account — use a service account, not a personal login
- Map Gong’s call activity to HubSpot objects: calls log to Contact and Deal records automatically once connected
- Enable CRM writeback so Gong pushes call summaries, next steps, and key topics back into HubSpot deal notes
- Set the deal field mapping so Gong reads deal stage, close date, and deal value from HubSpot correctly
After the connection, Gong surfaces pipeline insights — deals at risk, competitor mentions, stalled conversations — based on the deal data it reads from HubSpot. The more accurate your HubSpot deal records are, the more useful those insights become.
Connecting Gong to Salesforce
- In Gong, go to Settings → Integrations → CRM and select Salesforce
- Authenticate via OAuth using a Salesforce admin or a dedicated service account with API access
- Confirm that the connected account has read/write access to Opportunities, Contacts, Accounts, and Activities
- Map Gong activities to Salesforce tasks — Gong can log calls as Task records on Opportunity and Contact pages
- Enable Gong’s Salesforce writeback to push call summaries into Salesforce note fields or custom objects
For Salesforce specifically, check that your connected user has access to all Opportunity record types and pipelines you want Gong to analyze. A common issue is connecting with an account that only sees a subset of the pipeline due to Salesforce sharing rules.
What Pipeline Data Gong Surfaces After Integration
Once connected to either CRM, Gong’s pipeline intelligence includes: deals with no recent call activity, deals where competitors were mentioned in calls, opportunities where the close date is approaching but engagement has dropped, and rep-level conversation patterns compared against closed-won deals. These insights appear in Gong’s Deals view and can be filtered by pipeline stage, rep, and time period.
Frequently Asked Questions
How to prepare my CRM before implementing Gong?
Clean your deal stages, deduplicate contacts, reassign deals from departed reps, and make sure required fields are filled in for active deals. The checklist above covers each step in detail. The goal is to ensure Gong reads accurate data from day one — not the stale records that often sit in CRMs unnoticed.
Does Gong work with both HubSpot and Salesforce?
Yes. Gong has native integrations with both HubSpot and Salesforce. The connection setup is similar for both — OAuth authentication, field mapping, and CRM writeback configuration. Gong also integrates with Microsoft Dynamics and other CRMs, but HubSpot and Salesforce are the most commonly used and best-supported.
How long does Gong take to surface useful pipeline insights after connecting to the CRM?
Gong needs a volume of call recordings to start identifying meaningful patterns — typically two to four weeks of active use before deal-level insights become reliable. Pipeline risk alerts based on deal stage data are available immediately after the connection, but the conversation intelligence features improve significantly as Gong builds a baseline from your team’s calls.