How to switch from Gong to Avoma: A migration guide
Table of Contents:
Switching from Gong to Avoma comes down to one question for most teams: what happens to the conversation history you've built up in Gong?
Your team still uses it. A manager pulls up an old call to coach a rep. A CSM checks what was promised during the sale. This guide covers what moves over, what Avoma generates for you, how privacy settings carry over, and what you need to decide before the migration starts.
TL;DR
- Historical Gong conversations import in the background while your team records new meetings in Avoma.
- For eligible migrations, Avoma includes the previous 12 months of Gong recordings and transcripts at no additional cost, for the users moving to Avoma.
- Recordings and transcripts migrate by default. Notes and scorecards are generated in Avoma on request.
- Meetings Gong marks as private stay Private in Avoma.
What moves from Gong to Avoma
A Gong to Avoma migration brings your historical recordings and transcripts into Avoma, so your old and new calls are in one place. Avoma retrieves them through the Gong API.
| Gong information | What happens in Avoma |
|---|---|
| Recordings and transcripts | Migrated from Gong by default |
| Meeting privacy | Set from the privacy value Gong provides |
| Notes and scorecards | Generated in Avoma from the migrated conversation, on request |
| Other conversation outputs | Scoped case by case with the Avoma team |
Recordings and transcripts are copied from Gong as they are. Notes and scorecards are created fresh in Avoma from the migrated call, so they use Avoma's format and your Avoma settings.
Key Takeaway: If your team relies on notes or scorecards when it opens an old call, request them before the migration begins.
When to start
Start planning as soon as you know your Gong subscription end date. You need to finish the migration and check the results before then, while you can still open the same calls in Gong.
Check your contract for a second date too: any notice deadline for cancelling or changing the renewal. It can fall weeks or months before your access ends.
Your team can start recording meetings in Avoma on day one while the Gong history imports in the background.
Common Mistake: Treating the Gong expiration date as the migration date. Starting on the last day leaves no time to compare imported conversations against Gong or fix anything unexpected.
The 3 decisions that shape your migration
Avoma needs 3 answers from you to scope the migration.
| Decision | Question to answer | What it determines |
|---|---|---|
| 1. End date | When does your Gong subscription end? | The timeline for migration and review |
| 2. History window | How far back do you need conversations, and for which users? | Whether the included 12 months covers you |
| 3. Conversation content | What does your team use from the old calls? | Whether notes or scorecards need generating |
For many teams, 12 months covers open deals and current customers. If your sales cycle runs longer than a year, or a key account has years of history you want to keep, tell the Avoma team before the migration starts. They'll confirm the scope and any extra cost first.
Size the history window by what your team will open after Gong is gone.
Pro Tip: Ask a few managers and reps when they last opened an old Gong call and why. Their answers tell you more about the history and outputs you need than a count of stored calls.
What happens during the migration
Once your scope is agreed, here's what Avoma handles:
- API access: Avoma uses a Gong API Access Key and Secret Key to retrieve your conversations. Your Gong administrator may need to create them. The Help Center steps show where to find them. This page on how Avoma handles data security explains how your data is protected.
- Background import: Recordings and transcripts come across while your team keeps working in Avoma.
- Privacy: Meetings Gong identifies as private are set to Private in Avoma. Everything else is set to Visible to organization. You don't have to change privacy settings call by call.
- Generated outputs: If you requested notes or scorecards, Avoma generates them from the migrated conversations.
How to know the migration worked
Review a few migrated conversations before your Gong access ends. A handful is enough if they cover what you asked for.
| Conversation to review | What it confirms |
|---|---|
| One near the earliest date you requested | The full history window came across |
| A private conversation | Privacy settings carried over |
| One from an important active account | The history your team relies on most is there |
| One with requested notes or scorecards | Generated outputs are present |
If something looks wrong, tell the Avoma team before your Gong access ends, so they can compare the call against the original.
What to bring to your first migration conversation
Have these answers ready for your first call with the Avoma team:
- Your Gong end date and any notice deadline
- The users moving to Avoma
- How much history you need
- Whether you need notes, scorecards, or other outputs generated
- Who can provide Gong API access
- Any accounts or conversations you must preserve
Planning a move from Gong?
Avoma records and transcribes your team's meetings and keeps them searchable. After the switch, a manager can open a call imported from Gong in the same place as this week's calls. If you're still weighing the move, this side-by-side look at Avoma and Gong covers features and pricing, and this breakdown of what Gong costs today shows the numbers behind it.
For eligible migrations, Avoma includes the previous 12 months of Gong recordings and transcripts at no additional cost. Review Avoma's plans and pricing or book a call with the Avoma team to scope your migration.
Frequently Asked Questions
For eligible migrations, Avoma includes the previous 12 months of Gong recordings and transcripts at no additional cost, for the users moving to Avoma. Longer history windows, very high conversation volumes, or additional requirements may incur additional costs, which the Avoma team confirms before the migration begins.
The included migration covers the conversation history of the users moving to Avoma. If a team needs history for other users, such as former employees, that requirement should be discussed with the Avoma team before the migration starts so they can scope it.
Existing Gong notes and scorecards are not copied into Avoma. When requested before the migration, Avoma generates supported notes and scorecards from the migrated conversations, using Avoma's formats and the team's Avoma setup. Teams that rely on historical scorecards for coaching should include them in the migration requirements.
Most standard migrations do not run into a specific call limit. Organizations with very high conversation volumes may need additional scoping, and additional costs may apply. Avoma confirms the scope and any extra cost with the customer before the migration begins.
What's stopping you from turning every conversation into actionable insights?
