How to migrate historical Gong conversations to Avoma

When you move from Gong to Avoma, Avoma can migrate your historical Gong conversations. Your team keeps access to past recordings and transcripts in Avoma.

For eligible migrations, Avoma migrates the previous 12 months of Gong recordings and transcripts at no additional cost.

Before you begin

This article is for Avoma admins coordinating the move from Gong.
You need admin access to Gong to get the API Access Key and API Secret Key.
Have your Gong subscription end date ready.
Know which users’ conversation history you want to migrate.
Decide whether you need more than 12 months of history.
Decide which additional insights, such as notes or scorecards, you want generated.

Key sections

What gets migrated
Migration eligibility
How to migrate your Gong conversations
How meeting privacy is applied
How to verify your migrated conversations
Frequently asked questions

What gets migrated

By default, Avoma migrates recordings, transcripts, and the privacy status of each meeting. You can request notes, scorecards, and other insights, which Avoma generates from the migrated conversations.

Data	What happens in Avoma
Recordings	Migrated by default
Transcripts	Migrated by default
Meeting privacy	Set from the privacy status Gong provides
Notes	Generated in Avoma when requested
Scorecards	Generated in Avoma when requested
Other insights	Confirm requirements with your Avoma contact

Note: Notes, scorecards, and other insights aren’t transferred from Gong. When you request them, Avoma generates the supported insights from the migrated conversations.

Migration eligibility

The included 12-month migration covers the conversation history of the users moving from Gong to Avoma. Your Avoma subscription should include those users.

For example, if you’re moving 100 Gong users and want their conversation history in Avoma, your Avoma subscription should include those 100 users.

Most standard migrations fall within the included service. Additional costs may apply if:

You need more than 12 months of history.
Your organization has a conversation volume well above a standard migration.
You have migration requirements beyond the standard scope.

Check with your Avoma contact to confirm the migration scope with you before processing begins.

How to migrate your Gong conversations

Avoma uses the Gong API to retrieve your historical conversations. You provide the API credentials and migration details, and Avoma handles the rest.

Get your Gong API credentials

1. In Gong, get your API Access Key and API Secret Key.

2. Receive access to the API.

Send your migration details to Avoma

3. Send your Avoma contact the following:

- Your Gong subscription end date
- The users whose conversations should be migrated
- Whether you need more than 12 months of history
- Your Gong API Access Key and API Secret Key
- Any additional insights you want generated

4. Wait for your Avoma contact to confirm the migration scope.

Avoma migrates your conversations

After the scope and API access are confirmed, Avoma processes your historical Gong conversations. Recordings and transcripts are migrated by default, along with any insights you requested.

Note: Your team can record new conversations in Avoma while the historical conversations are being processed.

How meeting privacy is applied

Gong provides the privacy status of each meeting during the migration. Avoma applies it as follows:

Gong privacy	Avoma privacy
Private	Private
Not private	Visible to organization

You don’t need to update the privacy of each migrated conversation yourself.

How to verify your migrated conversations

When the migration is complete, open a sample of your historical conversations in Avoma and confirm that:

Recordings are available and play.
Transcripts are available.
Conversations cover the expected historical period.
Conversations that were private in Gong are marked Private.
Any notes, scorecards, or other insights you requested are available.

Tip: Check at least one conversation close to the earliest date in your migration. This confirms the full historical period came through.

If something is missing or incorrect, share an example conversation with your Avoma contact so the team can investigate.

Frequently asked questions

Is Gong migration included with Avoma?

Yes, for eligible migrations. Avoma includes the previous 12 months of Gong recordings and transcripts at no additional cost, for the users moving to Avoma. Migrating more than 12 months, a conversation volume well above a standard migration, or additional requirements may cost extra.

Can I migrate Gong data for users who don’t have Avoma seats?

The included migration covers the users moving to Avoma, so the users whose Gong history you migrate should match the users in your Avoma subscription. If your requirements are different, discuss them with your Avoma contact before the migration starts.

Can I migrate more than 12 months of Gong history?

Yes. You can request a longer historical period. Anything beyond the included 12 months needs additional review and may cost extra.

Is there a limit on the number of calls Avoma can migrate?

Most organizations don’t need to plan around a call limit for a standard migration. A conversation volume well above a standard migration may need additional scoping and may cost extra. Your Avoma contact confirms this before the migration begins.

Are Gong notes and scorecards migrated?

No. Recordings and transcripts are migrated by default, but Gong-generated notes and scorecards aren’t transferred. If you need notes, scorecards, or other supported insights for historical conversations, request them as part of your migration and Avoma generates them from the migrated conversations.

Can my team use Avoma while the migration is in progress?

Yes. Your team can record new conversations in Avoma while historical Gong conversations are being processed.

What happens to private Gong meetings?

Meetings marked Private in Gong are set to Private in Avoma. All other migrated meetings are set to Visible to organization.

What do I need to provide to start the migration?

Send your Avoma contact your Gong subscription end date, the users whose conversations should be migrated, your Gong API Access Key and API Secret Key, whether you need more than 12 months of history, and any additional insights you want generated.

What should I do if a migrated conversation is missing?

Share an example of the missing conversation with your Avoma contact. Include its date and any other identifying details available in Gong.

Recap

You know what Avoma migrates from Gong, what to send your Avoma contact, how privacy carries over, and how to check the results.

If you have any questions, contact our team at help@avoma.com