2026-09-07

The Harvest switchover month: run both, reconcile at the end

A hard cutover on a Monday is how migrations produce a month of missing time. The alternative is to run both tools for one billing period and let a report tell you when it is safe to cancel.

Week one: import

Create the workspace, run the Harvest import with a personal access token from id.getharvest.com/developers, and read the reconciliation report. Every client, project, member and year is compared against Harvest’s totals to the cent. Variances are itemized to the entry. If the report matches, the history is in.

Weeks two and three: both

The team keeps logging in Harvest, because that is what they know and what the current invoice will be built from. Some people try the week grid here. Nothing is at stake yet.

Week four: re-run, reconcile, decide

Run the import again. It syncs what changed: new entries land, edited entries land as edited, nothing duplicates. Re-run the reconciliation and read it as the last word. If it matches, cancel Harvest on your own schedule; you have 90 days of export access here regardless, and Harvest’s own exports are still yours to take.

What the trial does meanwhile

If the import puts the workspace over the free plan (more than two active people or one active project), a 14-day trial of the full plan starts with the import. At the end you subscribe at $9 per active member per month, or archive down. The report and the exports never lock either way.