If you’re moving your conversation data from Avoma to Jiminny, our migration tool can streamline the process. This guide outlines the steps for obtaining the necessary data, setting the migration scope, and understanding key limitations.
Obtaining the Data
To begin the migration, you’ll need to request an export of your conversation data from Avoma. Here’s what to do:
Export Data: Ask Avoma to export your conversation data into an S3 bucket created specifically for the migration. Jiminny will create the secure Cloud bucket and provide details to pass back to Avoma.
Metadata CSV File: Ensure Avoma also supplies a CSV file with metadata, including CRM details such as account record IDs and host emails. This file should be placed in the root directory of the S3 bucket.
Determine Scope
To keep the migration efficient, Jiminny provides filters to narrow down the conversations transferred from Avoma. Our team will work with you to define the scope based on your needs. Filtering options include:
Offset: Adjust the starting point for migrating conversations (e.g. skip old meetings).
Duration Limit: Control the minimum duration of conversations to migrate.
Migration Process
Once your data is ready, Jiminny will manage the migration within the designated environment. You’ll have options to assign users or skip conversations if any user data is missing, ensuring flexibility in how the data is handled during the transition.
Limitations
When migrating from Avoma to Jiminny, there are a few important limitations to be aware of:
Conversation Types: Only meetings and calls are migrated; other engagement types, such as emails, are not included.
Language: Conversations are imported with a default setting of English, as Avoma does not specify language data.
Data: Only Lead, Account, and Opportunity data (with stages) are imported from Avoma.
Conversation Analysis: Jiminny performs transcription and topic analysis on migrated conversations, but advanced analysis such as summaries or question tracking will not be included.