Importing is available to workspace owners and admins. See Import data into your workspace for how imports run and what to check before you start.
Prepare your CSV
Your file should have one row per item and a header row naming the columns. The exact columns depend on what you’re importing.Column names don’t have to match Sleekplan’s field names. You map each field to a column yourself in the next step, and matching names are lined up for you automatically. Matching names just saves you a click.
- Feedback posts
- Changelog updates
- User accounts
| Column | Required | Format |
|---|---|---|
| Title | Required | The post title. |
| Description | Required | The body of the post. |
| Category | Required | The category name. Created if it doesn’t exist yet. |
| Required | The email of the user the post is from. The user is created if new. | |
| Votes | Optional | A number. Sets the post’s vote count. |
| Created | Optional | The original date, as YYYY-MM-DD. |
| Status | Optional | The status name. Created if it doesn’t exist yet. |
| Username | Optional | A display name for the post’s author. |
| Tags | Optional | One or more tags, comma-separated (for example ui, mobile). |
Feedback posts example
Run the import
Open the importer
Choose what to import and pick CSV
Set What to import to Feedback posts, Changelog updates, or User accounts, then set Source to CSV file.

Upload your file
Click the upload area and choose your
.csv, or drag the file onto it. Keep First row contains headers on if your file has a header row (it’s on by default).Map the columns
For each Sleekplan field, pick the column from your file that feeds it. Required fields are marked with a red asterisk. Columns whose names match are mapped for you, so most files need only a quick check. The Preview below shows the first few rows exactly as they’ll be imported, so you can confirm everything lines up.

Start the import
Once every required field is mapped, click Start import. Sleekplan schedules the job and emails the workspace owner a log when it finishes. See How an import runs.
Tips and things to watch
- Rows missing a required field are skipped. For feedback, a row with no title, category, or email won’t be imported. The email log lists what was skipped.
- Dates use
YYYY-MM-DD. For example,2026-03-01. Rows without a date use the import time instead. - Wrap values that contain commas in quotes. This matters most for the feedback Tags column, for example
"ui, mobile", so the comma isn’t read as a column break. - Categories and statuses are created on the fly. Double-check the spelling in your file, since a typo like
Planedcreates a new status rather than matching your existing Planned. - Running the same file twice creates duplicate posts. Import each file once. Users are matched by email, so they aren’t duplicated.
Related
Import from another tool
Move posts, comments, and votes from Canny, Upvoty, or UserVoice with an API key.
Organize your feedback
Set up the categories, statuses, and tags your imported posts land in.
