A board that has lived inside Featurebase for a year has more than requests in it. It has a helpdesk inbox, an AI agent that has answered some number of tickets, and admin seats billed every month whether or not anyone used them that week. None of that comes with you, and the place to start is naming what stays behind before what arrives.
Can I migrate from Featurebase to VoteFirst?
Posts, statuses and vote counts import with a button. Comments and voter identities do not.
Paste your board's featurebase.app address into Settings and Import Board, and the open, reviewing, in progress, completed and cancelled posts come across, each with its title, description, status and vote count, up to five hundred. Your customer list and what each one pays moves separately, as a CSV, in about ten minutes, on the nine dollar plan. Comments stay on Featurebase, and bringing them across is an API call in a loop.
Those two jobs come first, in the order you would do them, then the price at your own seat count, since that is where the two products diverge hardest. The side by side with Featurebase is on the alternative page.
Is there a Featurebase importer?
Yes. In Settings, under Import and export, paste your board's featurebase.app address into the Board address field and press Import Board.
It reads a public board, the kind anyone can open without signing in. It brings across the posts with the most upvotes, up to five hundred, each with its title, description, status and vote count. Reviewing maps to Suggested, unstarted maps to In Review, active maps to In Progress, completed maps to Completed and cancelled maps to Denied. HTML formatting in the post body is stripped on the way in, so a description written with bullet points or bold text arrives as plain paragraphs.
Votes arrive as anonymous voters, one synthetic voter per vote, so every post's count matches what Featurebase showed. They are counts, not people: an imported vote carries a weight of one and cannot be tied back to a customer. Revenue weighting applies from the next vote cast, which is what the customer import below is for.
Comments do not come across, and neither do voter names or emails. Bringing those over is the same API loop the Canny migration uses.
Every plan reads the importer, including the nine dollar one.
If you want to see the mechanism before you commit to it, read a board first, yours or anyone's, and a trial started from there arrives with the address already filled in.
What is actually in a Featurebase export?
Featurebase's own help centre documents a CSV importer for moving the other way, into Featurebase, with mapped fields for a post's title, description, status, upvotes and tags. The API read VoteFirst's importer actually makes is narrower than that file: GET /api/v1/submission returns a title, a content field, an upvote count, a creation date and a status type per post, and the importer reads exactly those five fields and nothing else.
Two things it does not read, because the endpoint used does not return them: who voted, and what any single voter pays. Featurebase's own revenue sync is a feature of their product, not a field in this export, so a weighted board on the other side has to be rebuilt the same way a Canny migration rebuilds it, from your own billing data rather than from theirs.
Comments live on a separate endpoint this importer never calls. If you want them, the next step is the same one the Canny migration describes: mint a voter identity, then post each comment, one call per comment, against the features already created here.
The comparison table
| Capability | VoteFirst | Featurebase |
|---|---|---|
| Entry paid price | $9/mo | $29/seat/mo, billed yearly (Growth) |
| Price at 1 seat | $9/mo | $29/mo |
| Price at 3 seats | $39/mo (PRO) | $87/mo |
| Price at 8 seats | $39/mo (PRO) | $232/mo |
| Billing unit | Per project | Per admin seat |
| Extra usage charges | None | $0.49 per AI resolution, every paid plan |
| Branding removal | Included on any paid plan | Not on Free or Growth; a separate monthly charge on Professional and Enterprise |
| Voting without an account | Yes, anonymous cookie, on the public board | Yes, on the public board |
| Revenue weighted voting | Every plan, integer multiplier per tier | From Growth, sorts by revenue impact |
| Single sign on | Signed JWT handoff, PRO only, no SAML | SSO and identity management, Enterprise only |
| Live chat, shared inbox, ticketing | Not offered | Included at every tier, including Free |
| AI agent | Not offered | Fibi AI agent, Growth and above, billed per resolution |
| Free plan | None; 14 day trial, card required | Yes, 1 seat, unlimited conversations |
Featurebase bills per admin seat, not per tracked user, so the rows above use seat counts. Read on Featurebase's own pricing page, 2 October 2026, with the yearly billing switch on, the position their cards open in.
VoteFirst's PRO plan does not move with seat count. Three admins and eight admins both land on the same thirty nine dollars, because the price is set by the project rather than by who has a login to it.
Customer CSV import
The board import above carries posts and plain vote counts. What it cannot carry is who voted, because Featurebase's public endpoint does not say, so revenue weighting on an imported board starts from your own customer list rather than from anything Featurebase holds.
A CSV of voters reads the following columns, matching any of the names on the right so renaming is rarely needed.
| What it is | Column names it accepts |
|---|---|
| The person | email or email_address |
| Their name | name, display_name, customer_name or full_name |
| What they pay | mrr, revenue, monthly_revenue or amount |
| Which tier they are on | tier, plan, tier_name or plan_name |
Up to ten thousand rows in one file. The parsed result shows on screen before anything saves, so a wrong column guess gets caught before it writes rather than after. It needs an active paid plan and an owner or editor role on the project, and the nine dollar plan qualifies the same as the thirty nine dollar one.
Once the list is in, each person lands on a voting tier, the tier carries a whole number multiplier, and every vote they cast from then on carries that multiplier. The plain headcount stays visible beside the weighted total, so the two numbers can be read side by side rather than one replacing the other.
Should you switch?
Three answers, and only one of them is yes.
No, if the helpdesk is the part you actually use. Featurebase bundles live chat, a shared inbox, ticketing and an AI agent with the feedback board, all behind one login. VoteFirst is a feedback board and nothing else, so moving means running a separate tool for support, and for a team that leans on that bundle daily, staying is the better answer.
No, if nobody on your board pays differently from anyone else. Weighting only changes the order when your customers pay different amounts. If the whole list is on one price, a plain vote count already sorts the board correctly and the switch buys nothing.
Yes, if the bill grows every time you add an admin. Featurebase charges per seat, so a team of eight pays $232 a month on its entry paid tier where a team of one pays $29. VoteFirst's PRO plan is $39 regardless of how many people on your side have a login, and that gap only widens as the team does.
What VoteFirst does not do
This is a feedback board, not a helpdesk, and it says so rather than quietly leaving the helpdesk out of the comparison.
- No live chat, shared inbox, ticketing or help centre. The board votes, comments and prioritizes; it does not route support conversations.
- No AI agent, AI Copilot or a per resolution charge of any kind, because there is no AI feature in the product at all.
- No SAML or OIDC. Single sign on for voters is a signed JWT handoff, available on PRO, not Featurebase's identity management tier.
- No Slack, Zapier or outgoing webhooks.
- No free plan. A fourteen day trial with a card required at signup, then $9 or $39 a month.
- A custom domain serves the public roadmap, the public voting board and one named board, not a changelog or a most wanted list on that same domain.
Frequently asked questions
Is VoteFirst cheaper than Featurebase?
At three seats or more, yes, because Featurebase bills per seat and VoteFirst does not. At one seat the gap is smaller, nine dollars against twenty nine, still cheaper, and it widens as soon as a second admin joins.
Can I migrate my Featurebase board to VoteFirst?
Posts, statuses and vote counts come across with a button. Comments and voter identities do not; bringing those over is the same API loop the Canny migration uses, against VoteFirst's own comment and identity endpoints.
Does VoteFirst have a helpdesk like Featurebase?
No. VoteFirst is a feedback board: voting, a public roadmap, a changelog and revenue weighted voting. There is no live chat, ticketing or AI support agent, and none is planned.
Does Featurebase's AI agent cost extra?
Yes, forty nine cents per resolution on every paid plan, on top of the seat price. VoteFirst carries no AI feature and no usage charge of any kind.
Should I stay on Featurebase?
If the helpdesk bundled with your feedback board matters more than the bill, or your company qualifies for Featurebase's eighty six percent startup discount, staying is the better answer.
What does it cost to try?
What this costs
Lite
$9 /mo
Pro
$39 /mo
Lifetime
$999 once
Fourteen day trial of Pro, card asked for at signup. Nothing here counts the people who vote, so the bill does not move when the board starts working. The long version, with what happens if you stop paying.
Nine dollars a month for one project, with weighted voting and the CSV import included. Thirty nine adds more projects, the API and a custom domain, and neither price moves with how many admins are on your side of the login.
A card is required to start the trial. Featurebase's free plan does not ask for one and is a real option for a single seat with no board import need; at that size it is worth weighing against the fourteen day trial here before deciding.
14 days, a card at signup, then $9 or $39 a month.