Export Featurebase Requests, then prepare one row per request for ProductLift. Help articles and changelog announcements have separate import routes.
The export covers the workspace, not the filters currently open in Requests. Featurebase calls some CSV columns by their older names: Board Name is the category, Tags are labels, and Upvote Count is the Requester count. See Featurebase's export guide.
| Source data | ProductLift field |
|---|---|
| Post Title | Title |
| Post Content | Description |
| Status | Status |
| Creation Date | Created Date |
| Author's Email | Author Email |
| Tags | Tags |
| Board Name | Category, or use it to split destination boards |
| ETA | Estimated Date |
If you carry Upvote Count into Number of Votes, it becomes a total only. It does not identify requesters. To preserve people, use Featurebase's Requester CSV, match records to requests and put unique email addresses in Voter Emails, separated by semicolons. Review what each requester record represents before recording a vote on their behalf.
The Request CSV does not contain discussion or activity history. Merged requests are not separate rows. Keep any extra exported comments or source feedback separately; use the API for supported follow-up imports.
Import help content and changelog history into their own boards. Reconnect customer revenue rather than treating a request's exported revenue total as customer records.
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.