Learn about Savio
- Getting Started
- How Savio Works
- Triaging Feedback
- Managing Users
- Closing the Loop
- Voting Boards
- Importing People, Companies, and Attributes
- Connecting Your Support Tool
- Chrome Extension
- Emailing Feedback
- Integration for Slack
- Creating Feedback Templates
- Tips for Triaging Effectively
- Managing Custom Attributes
- Canned Filters
- Hubspot Integration
- → Importing Historical Data
- Using Savio's API
- Setting “Feedback From”
- Exporting Your Data
- Feature Request Details Page
- Setting Up Savio
- How To Be Successful with Savio
- The Four Problems Savio Solves
- Segment Integration
- Help Scout Integration
- Zendesk Integration
- Intercom Integration
- Salesforce Integration
- Customizing Feature Request List Columns
- Customizing Feature Request and Feedback Attributes
- Moving Feedback
- Savio's Integrations and Their Features
- Daily Digest Email
- Running a Product Meeting
- Zapier Integration
- Voting on Behalf of (VOBO)
- Single Sign-On
- Configuring Voting Board Access
- Using Feedback Forms
- The My Feedback Page
- Using Tags
- Filtering Feedback and Feature Requests
- Jira Integration
- Shortcut Integration
- Using the Zendesk App
- Using Products and Product Areas
- Using Roadmaps
- Using Comments
Importing Historical Feedback Data into Savio
Switching to Savio from another platform? Not to worry—we can import the feedback and feature requests from your previous system. There are four main ways to do that:
In each case, if you provide us with the data, we’ll help you import it and get it set up in Savio.
Importing historical data into Savio using a .csv file
We can take data about your feedback and feature requests from a .csv file and turn it into a complete feedback vault in Savio. Each field in the .csv will be used to fill in the feature request and feedback entries in Savio.
For each piece of feedback, you’d fill in as many of the following fields as possible:
User email: This is the email address of the person who gave a particular piece of feedback.
User name: This is the full name of the person who gave a particular piece of feedback. This is a required field.
User internal ID: This is the ID you use in your own internal system to keep track of the user who gave a particular piece of feedback. If you don’t have an internal ID for your customers, you can leave this blank.
Company name: This is the name of the company that the person who gave a piece of feedback works for. If you don’t use companies, you can leave this blank.
Company internal ID: This is the internal ID that you use in your system to keep track of the companies that are your customers. If companies aren’t relevant to you or you don’t give them an internal ID, you can leave this blank.
Company FA plan: This is the name of the plan that the company or person has purchased from you.
Company FA spend: This is the amount of revenue that this company or person pays you every month. We use it to calculate the MRR for each feature request.
Feedback problem: This is the verbatim description of the feedback a person gave you. This is a required field.
Feedback created: This is the date the feedback was received.
Feedback source URL: This is the URL to the source of the feedback if it is housed in your support tool, CRM, Google Docs, or other web apps.
Feedback tags: These are any tags that apply to the piece of feedback. Multiple tags can be included, separated by commas.
Feature request title: This is the title of the feature request.
Feature request description: This is the description of the feature request.
Feature request state: This is the status of the feature request in Savio. Valid entries are: “Untriaged”, “Under Consideration”, “Planned”, “In Progress”, “Shipped”, “Customer Notified”, or “Won’t Do”.
Feature request priority: This is your judgment of the importance of the feature request. Valid entries are: “High”, “Medium”, or “Low”.
Feature request tags: These are any tags that apply to the feature request. Multiple tags can be included, separated by commas.
Tip: The only fields that are required to import a feature request are the “User name” field and the “Feedback problem” field. Of course, the more information you include, the better.
Importing conversations from Intercom
We can import feature requests and feedback from Intercom. Here’s how to do it:
1. Connect Savio to Intercom. Find instructions for connecting your support tool here.
2. Choose the tags you’d like Savio to import as feature requests. Each tag will become its own feature request.
3. We’ll help you with the rest. Just email us.
Tip: Any tags you give Savio will be turned into a feature request. Conversations with messages to which that tag is applied will be included in Savio as a single piece of feedback.
For example, if you have a tag called “Zapier Integration”, Savio will import that tag as a feature request called “Zapier Integration”. And if you have 6 conversations with messages that are tagged as “Zapier Integration”, each of those conversations will be turned into a piece of feedback and added to the feature request. In the end, you would have one feature request called “Zapier Integration” that has 6 pieces of feedback attached to it.
Import vote data from Canny
We can help you import vote data from Canny.io. Here’s what you’ll need to do:
1. Export your Canny data as a .csv. Full instructions for how to do this can be found on Canny’s support page.
2. We’ll help you with the rest. Email us and we’ll help you import that .csv to your Savio feedback vault.
Importing data from another tool
We're always happy to write new importers for customers. So if it's challenging to fill out the .csv, drop us a line and let us know what you need.Last Updated: May 23 2021