How to get there: Go to Settings → Import tab.
Move your feedback, votes, and statuses from Featurebase to ProductLift in three steps: export your posts CSV from Featurebase, upload to ProductLift, let AI map the columns.
You'll need:
Plan to migrate one board at a time. The Featurebase export respects your active filters, so you can scope each export to a single board cleanly.
Featurebase and ProductLift both use "boards" but the shape differs slightly:
Two reasonable migration shapes:
The Featurebase posts CSV contains:
| Featurebase column | What it contains |
|---|---|
| Post Title | Post title |
| Post Content | Post body (markdown) |
| Upvote Count | Total vote count |
| Creation Date | Created timestamp |
| Author Name / Author's Email | Submitter |
| Tags | Comma-separated tags |
| Post URL | Original Featurebase URL |
| Board Name | Source board |
| Status | Post status |
| ETA | Estimated delivery date |
| Associated MRR | Revenue (if a billing integration is connected) |
| Custom Field Values | Any custom fields you defined |
Repeat for each board (using filters), or export everything at once.
The simplest migration just brings vote totals across, not individual voters. Featurebase's Upvote Count column maps directly to ProductLift's Number of Votes, your post leaderboards stay in the same order.
You only need per-voter attribution if you want each customer's voting history preserved in ProductLift. Featurebase has two paths for that:
GET /v2/posts/upvoters?submissionId={postId} to script a per-post voter pull. Best for large workspaces.The posts CSV does not include comment text. If you need comment threads, pull them via Featurebase's /v2/comments API.
You don't need to rename Featurebase's columns. ProductLift's importer uses AI to map them automatically.
| Featurebase column | ProductLift field |
|---|---|
| Post Title | Title |
| Post Content | Description |
| Status | Status |
| Upvote Count | Number of Votes |
| Author's Email | Author Email |
| Tags | Tags |
| Creation Date | Created Date |
| ETA | Estimated Date |
| Board Name | (use as Category if collapsing boards) |
| Post URL | (ignore, or paste into Description) |
| Author's Picture URL | (ignore) |
| Associated MRR | MRR per Post (preserved on the post, surfaces on prioritization views) |
Skip this section if you're happy preserving vote totals only. If you exported per-post voter lists, add a Voter Emails column with semicolon-separated emails per row:
title,description,status,number_votes,author_email,tags,created,voter_emails
"Add dark mode","Users want a dark theme.","Planned",47,"customer@example.com","ui,design","2025-10-12","a@ex.com;b@ex.com;c@ex.com"ProductLift will auto-create users for any voter email it hasn't seen, cast real votes from them, and reconcile against your Number of Votes total so the count matches Featurebase.
You don't need to rename Featurebase's statuses in your CSV. On the preview step, the importer detects any status that doesn't exist on the target board and lets you, per status:
Same flow for categories that don't yet exist.
When it finishes, click View Imported Posts to see the batch.
ProductLiftIdentify({ email, uid, name, ... }). See Single sign-on (SSO).If you'd rather not run the migration yourself, our team can do it for you. Send us your Featurebase export (or API credentials) and we'll handle the mapping, voter attribution, and cleanup. Email support@productlift.dev to start a migration concierge request.
For large Featurebase workspaces or where the CSV path drops too much (per-voter attribution, full comment threads), use the API instead of the wizard:
GET /v2/posts, voters via GET /v2/posts/upvoters, comments via GET /v2/comments.See Importing feedback posts for the full importer reference.