Jiminny can migrate your conversations from Chorus using their public API. This allows you to seamlessly transfer your data and keep your workflows intact in Jiminny.
Migration Guide
Generate a Chorus API Key
To obtain the required credentials, you must be a Chorus administrator. In Chorus:Go to Settings > API Access.
Click Create API Key to generate the access key.
Copy the API key and securely pass it to your Jiminny Account Manager.
Decide the Migration Scope
Consider which data you'd like to migrate over. Let us know:The period you’d like to cover (e.g. the last 6 months).
The systems you want to migrate (e.g. Zoom, Google Meet).
Schedule the Migration
Depending on the volume of data and systems to migrate, provide at least 1 week's notice to Jiminny for planning and preparation.
What Gets Migrated?
During the migration process, Jiminny will map Chorus users based on their email addresses. The following data will be copied:
Call metadata (time, duration, customer, attendees).
Conversation transcript with speaker separation.
Playable conversation, including video (if applicable).
If the user doesn't exist in Jiminny (or hasn’t accepted an invitation), an account will be created for them with an Insights role. Please note, we don't currently import call comments from Chorus.
Important: Upon import, Jiminny won’t automatically generate call summaries or action items.
Themes, Topics, and Triggers
During onboarding, we’ll work together to configure your Themes, Topics, and Triggers in Jiminny.
You can export your trackers from Chorus, and we will help convert and import them into Jiminny.
Once your data is imported, all meetings will be analysed by Jiminny’s platform, and statistics and CI data will be available for coaching.
Potential Migration Limitations
Calls that were not recorded in Chorus will not be imported.
If the host of the call didn’t join, the call can’t be migrated.