Help / Guides /

Import requests from Canny, UserVoice or a spreadsheet

Updated 15 Nov 2026

Switching to List79 doesn't mean starting from an empty board. Export your requests from the tool you use now as a CSV file, and import them with their status, date, author and voters. You check how List79 reads the file before anything is imported, and you can undo an import afterwards.

1. Export your requests

  • Canny: Settings, then Data export. Export posts, and include votes if you want to bring voters along.
  • UserVoice: the Admin console, Suggestions, then Export to CSV.
  • A spreadsheet: File, then Download or Save as, and choose CSV.

The first row should hold the column names, then one request per row. Commas, semicolons and tabs all work, and so do quoted fields with line breaks in them. A file can be up to 5 MB and 5,000 rows; split bigger files into parts. To start from scratch, download the template on the import page.

2. Upload the file

Open the product's Settings and choose Import from CSV. Owners and admins can do this. Choose your file and Upload and check columns.

Not sure how it'll come out? Switch to Test at the top right first and import there: the same import in test mode touches only test data. See Test mode.

3. Check the columns

List79 shows the first rows of your file and guesses which column holds what, from the column names Canny, UserVoice and most spreadsheets use. Correct anything that's off:

FieldWhat it does
TitleRequired. Rows without a title are skipped.
DescriptionThe details of the request.
StatusTranslated with the status table below.
CreatedWhen it was asked, so your board keeps its history. Without it, the import date is used.
Author's user ID, email and nameWho asked. The author also counts as a voter.
Voters' emails or user IDsA list in one cell, separated by commas, semicolons or spaces. Each person becomes a vote.
Vote countJust a number. In List79 every vote belongs to a person, so a count can't become votes; it's kept as an internal note on the request ("it had 12 votes in the old tool…").

Below that, a table lists each status found in your file and the List79 status it becomes: for example complete becomes Shipped, closed becomes Declined, and open becomes New. Change any of them before importing.

4. Choose the options and import

  • Skip rows whose title matches a request you already have (on by default), so importing twice doesn't make duplicates.
  • Send imported people update emails (off by default). New people from the file didn't sign up for List79's emails, so they get none when their requests change unless you tick this. Nothing is emailed during the import either way, and no webhooks are sent.

Choose Import. The result shows how many requests, votes and new people were added, and how many rows were skipped. Imported requests show via Import on their page.

People and votes

People are matched by user ID, or by email when the file has no ID. If someone is already known to List79 (because they've used your widget, say), their imported votes join their existing record, and their next vote from your app counts as the same person. To match people your app identifies by its own user ID, include a user ID column with the same IDs you send to the widget or API.

Imported requests and votes don't count toward your plan's active users.

Undo an import

Past imports are listed on the import page. Choose Undo to delete the requests that import added, with every vote, comment and note on them. People the import added are removed too, unless they've done something else since, such as voting from your app. Requests your team merged into an imported request stand alone again.

Your uploaded file holds people's emails, so List79 deletes it as soon as it's imported or cancelled, and deletes uploads that were never imported after a day.