Migrating from Gong

Outdoo can migrate your conversations from Gong using their public API.

To do this, you'll need to retain access to the Gong platform during the migration. The conversations will function as a normal activity once the migration is complete, so you can search, comment, share and coach them. All languages are supported.


Migration Guide

1. Generate a Gong API Key.
To obtain credentials, you must be a Gong administrator. In Gong:

  • Go to Admin Center > Ecosystem > API.
  • Click Get API Key to receive the access key and the access key secret.
  • Make a copy of these and securely pass them along with the Base URL to your Outdoo Account Manager.

2. Decide the Migration Scope.
Consider which data you'd like to migrate over. Let us know:

  • Which workspaces, user's data 
  • Which period you'd like e.g. the last 3 months
  • Which systems you'd like e.g. Zoom, Dialpad

3. Schedule the Migration.
Depending on the number of systems and period you'd like to migrate, you need to provide at least 1 week's notice to Outdoo.


What gets migrated?

During the migration, Outdoo will map Gong users based on their email addresses. The following data is copied across:

  • Call metadata: time, duration, customer, and attendees
  • Conversation transcript
  • Conversation with speaker separation, playable audio, and video (if applicable)

If the user does not exist in Outdoo (or hasn't accepted an invitation) an account will be created for them with an Insights role

⚠️ We don't currently import call comments from Gong. As the data is migrated, we do not generate summary and action items upon import.


Themes, Topics and Triggers

As part of onboarding, we will build out your Themes, Topics and Trigger words together to ensure correct configuration from the start with Outdoo.

Export your trackers from Gong and we can convert and import them into Outdoo.

All of your meetings will be brought over and analyzed by our platform to give you complete statistics and CI data. This means that you'll have all of your calls analyzed and ready to be coached once you migrate over.


What can cause a call to not get migrated?

  • If the call was not recorded in Gong, it cannot be imported.
  • If the host of the call did not join, we cannot import it.

Was this article helpful?