Importing feedback from other tools
Prepare a CSV file, map its fields, and check Requests imported from another feedback tool.
Written By Bruno H
Last updated About 1 hour ago
Overview
Import feedback from another tool or spreadsheet with a CSV file. The importer lets you map your columns to Request fields and match existing categories and statuses.
CSV import brings in Request data. It is not a complete transfer of comments, individual Requesters, or every object from another product.
Import a CSV file
1. Prepare your data
Use one row per Request and a header row that identifies each column. Keep the original export as a backup while you prepare a copy for import.
The importer supports:
Request content: Title and content
Organization: Category, status, and labels
History: Creation date and upvote count
Author: Name, email, and profile picture
Every Request needs a title with at least two characters. Check dates and email addresses before importing.
Use comma-separated names within a labels cell when a Request has multiple labels. The importer reuses an existing label when the name matches and creates any other label as a public label. Create labels that must remain private before importing, and use the same names in your file.
Create your categories and statuses first so each imported value has a clear destination. Review category access before adding customer feedback to it.
Important: An imported upvote count does not identify the people who voted. Do not treat it as an imported Requester or email subscriber list.
2. Upload and map fields
Go to Settings → Data → Imports & Exports and click 'Import Data'
Upload your
.csvfileUse the dropdown above each column to choose its Featurebase field
Map your title column to 'Title (required)'
Leave columns you do not want to import as 'Unselected'
Map a source tool's board or category column to 'Category', its Request text to 'Content', and its vote total to 'Upvotes'. The importer shows sample values below each mapping so you can check the choice.
3. Match categories and statuses
If you mapped a category or status column, click 'Next'. Choose the Featurebase category and status for each value in your file, then click 'Start Importing'.
If neither column is mapped, 'Start Importing' is available directly after field mapping. The import runs in the background. The completion screen confirms that it has started; Requests then appear in your dashboard.
Tip: Map the category and status columns explicitly. This gives you more control over where Requests arrive.
4. Check the imported data
Review a sample of Requests in Requests & Insights → Requests before you begin collecting new feedback:
Titles and descriptions contain the expected text
Categories and statuses match your choices
Labels and dates have the expected values
Authors are associated with the intended customer
Public and restricted categories expose the right content
Migrate data beyond CSV fields
Use the Featurebase API when your migration needs a custom data flow. Compare the data you need to move with the supported API operations before building the import.
For Canny, Migrating from Canny covers how to plan the field mapping and switch collection to Featurebase. Keep separate source data for comments and customer relationships that are not included in the CSV importer.