Migration guide

Leaving Harvest after the 2026 price change

If a renewal email moved you to a plan you did not choose, at a number you did not expect, you are not an outlier. Here is exactly what changed, what it costs, and how to get your data out before your renewal date.

What actually changed

Harvest retired its legacy plans (Pro, Premium, Simple, Solo, Basic, Business) and replaced them with two tiers, Teams and Enterprise. The important part is not the tiers. It is that billing became two layers instead of one: a per-seat fee, plus usage-based charges for invoices, projects, clients and tasks.

Accounts choose between Unlimited usage (a fixed add-on) and Flex usage (recalculated each period from the previous period's activity). The per-unit rates for Flex are not published on the pricing page, so you cannot compute your own bill in advance. Renewals default to Enterprise with Unlimited usage unless you intervene before the renewal date.

If you are wondering why a fifteen-year-old product changed shape this suddenly, the short version is that it was acquired in July 2025. We wrote that up separately: why Harvest got expensive, including how to check whether the tool you move to can do the same thing to you.

Your options, honestly

Not everyone should switch to us. Pick by what you actually need:

Prices are each vendor's published list price, checked 27 July 2026. Follow the links, they change.

How to move your data

The reason most people stay is that years of history live in the old tool. That objection is the one we spent the most effort removing.

1. 1

   Create a FlatHours account

   Free plan, no card. Takes under a minute.

2. 2

   Make a Harvest personal access token

   In Harvest, go to id.getharvest.com/developers and create a token. Copy the token and the Account ID beside it.

3. 3

   Paste both into Settings → Import

   You will see a count of your clients, projects, tasks, people and time entries before anything is imported, so you know the size of the job.

4. 4

   Run the import

   Clients, projects, tasks, per-project rates, budgets and full time history come across. Time already invoiced in Harvest arrives locked so it cannot be billed a second time.

5. 5

   Check it, and re-run if you like

   The import is idempotent: running it again updates what it already brought across instead of duplicating it. Safe to repeat after a partial run.

What you give up by moving here

Worth being straight about it. FlatHours has no resource planning, no capacity forecasting, no utilisation dashboards, no timesheet approval chains, no SSO, and no expense tracking. If your team depends on any of those, one of the PSA platforms above is a better fit and we would rather you went there than churned in a month.

What you get instead is a timer, a timesheet, projects with real rate rules, invoices built from tracked hours, a client payment portal, and a bill you can predict without a spreadsheet.

Nothing watches you

FlatHours will not watch your screen, take screenshots, run in the background, read what you type, record which applications you used, guess what you were doing, or categorise your day for you. There is no monitoring feature on any plan, there is nothing an employer can switch on to observe their staff, and that is not going to change.

There is now one thing that notices you, and only if you switch it on yourself: an optional idle prompt. If your timer runs with no keypress, click or scroll on the FlatHours page for a number of minutes you choose, it asks whether to keep that time or drop it. It cannot see anything except whether an input event happened, it is set per person so nobody can turn it on for you, and it exists to stop a client being billed for time you were not working.

We also do not use your data to train models, and no AI feature is ever switched on without you switching it on. Both are written into the Privacy Policy, not just said here.