How to get there: Go to Settings → Import tab.
Productboard is a product management platform, not a voting tool, so this migration is fundamentally a model translation, not a CSV copy. Read this article in full before starting, the structural mismatch matters.
Productboard has no upvoting. Customer demand is represented as insights linked to features, weighted by segments and companies. ProductLift, like most feedback tools, runs on upvotes from individual customers.
You have to decide what becomes what:
This means a Productboard migration is the only migration where our concierge service is strongly recommended over self-serve. The decisions above benefit from a guided conversation. Email support@productlift.dev if you want help.
You'll need:
| Productboard | ProductLift |
|---|---|
| Product | (parent context, becomes board or portal-wide) |
| Component | Board, or Category within a single board |
| Feature | Post (or parent category if you import Subfeatures) |
| Subfeature | Post |
| Note | Comment (or vote source) |
| Insight (highlighted snippet from a Note) | Vote / comment |
| Status | Status (Features/Subfeatures only) |
| Custom Field | Custom Field (post type custom field in ProductLift) |
The simplest path is the URL export:
https://[your_workspace].productboard.com/api/features/export into the browser. Replace [your_workspace] with your actual workspace name.The Features CSV includes UUIDs, parent UUIDs, hierarchy path, status, team assignment, timeframe, and all custom fields. Tick Include item description to add plain-text description in the grid export.
Alternatively, open a grid board, configure the columns you want, and use the grid's export button.
https://[your_workspace].productboard.com/api/notes/export?export_type=with_features into the browser.?export_type=with_features parameter links each note to its feature.Be aware: notes sourced from Slack, Zendesk, or Intercom often don't include the original body text, only metadata. This is a documented Productboard limitation.
A separate Export insights to CSV path exists under the insights view. Use this if you want to translate insight-counts into vote-weights per feature.
Productboard has a REST API at developer.productboard.com. Important: API v1 is deprecated and stops working July 8, 2026. Use v2.
The shape depends on your chosen mapping. The simplest pattern: Subfeatures → Posts, with parent Features used as Categories.
| Productboard field | ProductLift field |
|---|---|
| Subfeature name (or Feature name) | Title |
| Description | Description |
| Status | Status |
| Parent Feature name | Category |
| Component name | (use as second-level tag, or as board name if splitting) |
| Timeframe | Estimated Date |
| Owner email | Assigned To |
| Custom field values | Custom field columns |
There are no votes in Productboard, so you have to invent them. Two reasonable approaches:
title,description,status,number_votes,voter_emails
"Add dark mode","Users want a dark theme.","Planned",12,"a@ex.com;b@ex.com;c@ex.com"The voter-email path is preferable because each customer keeps their voting history in ProductLift.
If you want note text attached to posts, import the posts first, then add the note body as internal comments via the ProductLift API. Internal comments stay private to admins, matching how Productboard treats notes.
Productboard statuses only apply to Features and Subfeatures. On the preview step, the importer detects any status that doesn't exist on the target board and lets you, per status:
When it finishes, click View Imported Posts to see the batch.
Productboard migrations involve real decisions: which hierarchy level becomes posts, how to translate insights into votes, what to do with note bodies that didn't survive the source-tool export. Send us your workspace details and we'll work through it with you. Email support@productlift.dev to start a migration concierge request.
See Importing feedback posts for the full importer reference.