Migrate from Productboard

Decide which features become ProductLift posts and how to preserve the customer feedback behind them. A note, a feature and a customer vote are different records.

Choose what to move

Productboard content ProductLift destination
Features or subfeatures Feedback posts or roadmap items
Product or component grouping Boards, categories or tags
Notes and linked customer feedback Internal comments or references where appropriate
Customers and companies Customer records, imported separately

Keep source feature IDs and parent IDs in your working files. They help match notes and rebuild useful post relationships after import.

Export features and notes separately

Use Productboard's export options for the feature view you want to move. Include names, full descriptions, status, owners, dates and parent information. Download notes separately and check that the note text and linked feature IDs are present.

If your export is incomplete, a developer can use the Productboard API. Check access to email fields: the notes API can return redacted owner or creator emails without the required permission. A redacted value cannot identify a customer in ProductLift.

Prepare the feature file

Source data ProductLift field
Feature or subfeature name Title
Description Description
Status Status
Owner email Assigned To
Chosen product or component grouping Category or Tags
Specific delivery date, when known Estimated Date

Choose one row per piece of work. Keep broad timeframes such as “next quarter” in the description if there is no exact date. Do not silently turn a whole feature hierarchy into unrelated duplicate posts.

Preserve customer evidence accurately

Do not turn every insight or note into a vote. Several notes can come from the same person, and a note can describe a problem without supporting a specific solution. Keep private research as internal comments. Only add voters when the source records establish that those customers requested or supported that feature.

Import the posts first, then attach notes or relationships through a separate API step. Check missing note bodies in the original source instead of replacing their meaning with a count.

Import and check a sample

  1. Create a feedback board if you do not have one yet.
  2. Open Settings → Import & export, upload 5 to 10 prepared rows and select the destination board.
  3. Review the suggested column mappings. In the preview, create or map missing statuses and categories.
  4. Click Execute Import. Open View Imported Posts and compare the imported posts with Productboard.
  5. Check titles, dates, authors and votes before importing the rest. Exclude your sample rows from the remaining file.

The post import guide covers supported fields and finding an import batch. For changing your domain, widgets and customer login after the move, follow the migration checklist.