Wave just paywalled bank feeds — I wrote a migration guide for the refugees
Just published a guide on the Wave free-plan changes that landed June 1 — bank feeds, receipt scanning, and collaborator access all moved behind Pro ($16-19/mo), and the backlash is real: Trustpilot 1.2/5, 201 BBB complaints, Reddit full of "Wave used to be free" threads.
I wrote it for the Wave refugees who are now re-shopping accounting tools: https://tallyassistant.com/blog/wave-free-plan-changes-2026
It covers what actually changed, the real costs, and 3 options (pay / go manual / switch) — including a genuinely free plan that still imports bank CSVs without a bank-feed paywall.
Curious what others here think: for those who've been on Wave, was the bank feed the killer feature? And for anyone who switched away from a "free forever" tool after it started charging — what made you leave?
Bank feeds are almost always the killer feature in free bookkeeping tools, so this paywall change was going to sting no matter how it was rolled out. Good instinct writing the migration guide right when people are actively looking.
A dated pricing promise plus a written notice period answers the trust question directly instead of just saying trust us. The part I would still watch closely is whether the 60 days covers feature removal too, not just price. Bank feeds disappearing without warning is what actually pushed people out of Wave, the price was secondary. If your promise covers both, that is a real structural difference, not just a marketing page.
This tool is founded and operated solely by me. I have no office overhead or employee costs—only my own time, effort, and expenses for API calls and server maintenance. This gives me a significant cost advantage.
That's why I'm able to offer both a Free Tier and a Pro Plan, and I've already calculated that the pricing structure ensures a sustainable profit margin while keeping the tool affordable for users who need access to its core functionality.
Additionally, even if you cancel your subscription, all your data remains exportable for up to two months—so you never have to worry about being locked in or losing your work.
The cost structure explains why you can price it the way you do, but it does not actually answer what I asked. Does the 60 day notice cover removing a feature, not just raising the price? Wave users were not upset about margins, they were upset about losing something they relied on with no warning. If your promise is scoped to price changes only, that specific fear is still open.
The "free forever, then paywalled" pattern is becoming its own founder lesson, Mailchimp, Slack, now Wave, the list keeps growing. What I'd actually want to know as someone re-shopping tools right now: is the switching cost really about the money, or is it about not trusting the next tool's free tier will stay free either? If it's the latter, your migration guide is solving half the problem, the mechanics. The other half is convincing someone your pricing model won't do the same thing to them in 18 months. Have you thought about publishing something like a pricing-stability commitment, or pointing at your business model, to pre-empt that specific fear?
Good catch — you're right that the switching cost is trust, not money. We just published a dated [pricing promise] that locks your price, keeps the free plan free, and commits to 60 days' written notice. The launch-special expiry (Sept 30) was announced from day one — a planned deadline, not a goalpost move. Happy to be held to it.
What's really interesting is how a change in price can trigger a specific moment when people start to think about their options. ~
For instance, people who were happy with Wave might now feel like they need to look around and see what else is out there.
I believe that having the option to import data from a CSV file is crucial. Many small businesses are more concerned about being able to switch to a new system without losing their existing data or disrupting their entire workflow, rather than just looking for a free solution. The ability to easily import their data can be a major factor in their decision to choose one system over another, as it allows them to make a gradual transition without having to start from scratch.
The comparison between paying, going manual, and switching is a useful way to frame it too. Different users will have very different thresholds for each option.
It would be interesting to see whether people mostly switch because of the recurring cost itself, or because the change makes them feel they can’t rely on the product’s pricing model anymore.
The consideration moment point is spot-on — and it's the thing incumbents never see coming.
Wave users didn't switch because someone was cheaper. They started looking the day Wave's pricing moved under them. And here's the kicker: once someone's comparison-shopped, they've comparison-shopped forever. Even the ones who pay for Wave Pro today — the incumbent lost its default position. For a founder, that's the real damage a bad pricing move does.
You're also right that CSV import is the actual deal. Watching the complaints, the anxiety was never "is the next tool free" — it was "will my books survive the move." That's why we built universal CSV import (auto-detect any bank format, no column mapping): export from Wave → drag & drop → done. Portability is the trust signal. After the accounts-frozen stories, people want proof their data will still be theirs to take.
And on cost vs. trust — my honest take, as someone who's watched this play out: it's trust. Wave users were already paying 2.9% on Wave Payments without flinching. They're not price-averse. The anger is about features being removed — loss aversion stings way harder than a price tag. That's why instead of just launching a cheaper plan, we published a dated Pricing Promise (https://www.tallyassistant.com/pricing-promise): price locked, free plan stays free, 60 days' written notice. It directly answers the "will you do this to me in 18 months" question.
Question for the IH crowd: if Wave had shipped the same features at $12/mo before June — without removing anything — would their users have stayed? Cost or trust: which one actually moves a customer?
This is a real pain point — bank feed access is the backbone of so many financial tools, and losing it overnight forces a scramble. Curious what you’re recommending people migrate to for reliability, since that’s usually the harder question than just “which one is cheapest.” Clean, consistent bank data underneath everything else matters more than people realize until it’s gone.
The useful signal here might be less the anger itself and more the migration friction people mention: bank feeds, collaborators, receipt capture, and historical data. If your guide can tag which pain sent each visitor there, you'll learn pretty quickly whether this is search traffic or real switching intent.
Bank feeds are almost always the killer feature in free bookkeeping tools, so this paywall change was going to sting no matter how it was rolled out. Good instinct writing the migration guide right when people are actively looking.
The backlash is a strong signal of dissatisfaction, but switching accounting tools is a much bigger behavior than complaining about a price change.
Are you seeing evidence that these Wave users are actually migrating to alternatives, or is that the main assumption you're testing with this guide?