Coming from another vendor? Want to bring existing cases into AllVoices?
You’re not alone. We’ve helped customers import thousands of historical cases from tools like Navex, Convercent, spreadsheets, and more.
We recommend completing your AllVoices customizations first, to make sure you’re happy with the form fields and structure before beginning the transfer. This way, you’re mapping your historical cases to the right set of new fields.
And we’re here to help you every step of the way.
How It Works
We won’t sugar coat it. Transferring thousands of historical cases will require some complex data work for a few reasons:
- Every vendor exports data differently, and is rarely all in one organized file. For example, they might export case notes into a separate file, or attachments are not organized with the corresponding Case IDs.
- Every vendor has different field structures. For example, AllVoices has Priority, Case ID, Case Name, etc. But other systems have different field structures and attributes. Because of this, its not a simple 1:1 sync.
But don’t worry, we’ve done this many times before. And our experienced team of experts has your back every step of the way.
Transfer Steps
- Export all your data from your prior vendor.
- Finalize customization of your AllVoices instance, so that all fields, questions, and drop-downs are live in our database.
- AllVoices provides a CSV template showing how your exported case data needs to be mapped.
- Map your exported case data to the new AllVoices form fields.* (This is the bulk of the work, but we’re here to help).
- AllVoices imports your data according to the completed mapped CSV.
*Case Mapping
Mapping is often the most substantial part of the project, and it requires advanced data analysis and aggregation. The scope of the work depends on several factors like the format of your exported data, the number of cases & attachments, and the structure of your new AllVoices forms.
Options for Mapping Support:
| Option 1: Customer completes mapping | $ |
| Option 2: AllVoices developers support mapping | $$ |
For specific pricing & timing, please ask your Account Executive for details. Already a customer? Reach out to your CSM or support@allvoices.co.
FAQs
If I complete the mapping myself, what should I expect?
The mapping work requires advanced excel expertise. We highly suggest having data analysts or developers available to help out. You’re often aggregating different data sources, and thousands or more lines of data, and mapping it into new structures.
What support will I have if I choose to map on my own?
Your Implementation Manager or CSM will be able to answer basic questions, but we cannot provide developer or technical resources if you choose this option.
Can I get started on mapping before I finish customizing AllVoices?
No. We need your AllVoices form setup first. We need to know what fields, drop-downs, and questions you will have in AllVoices, to understand where you will be mapping data in our system.
Can we include attachments?
Yes.
What happens to data that isn’t mapped directly to a field in AllVoices?
Sometimes customers have historical data they want to retain, but they don’t want to create a corresponding field in AllVoices. For this, we can map the historical field to AllVoices Notes section on the case. This way, you retain the information without creating a corresponding field.
Can I transfer data in chunks?
Yes. Once we begin the import, we can do another import within 60 days. After 60 days, it will be an additional cost.