Migrating from Clockify

The Clockify migration works like the Toggl and Harvest migrations: connect with a key, import setup data, then backfill history. Both steps are safe to re-run. You need the owner or admin role.

Connect your Clockify account

1. In Clockify, open Profile Settings and find the API section (under Advanced). Generate or copy your API key.
2. In Time Trakkr, go to Integrations and find Migrate from Clockify.
3. Paste the key and select Connect. If your key reaches more than one workspace, pick the one to import.

The key is stored encrypted and only used for importing. Disconnect removes it.

Step 1 — setup data

Select 1 · Import clients, projects, tasks & people. Clients, projects (including archived ones, so history attributes), Clockify tasks, and people all come over. Projects without a client group under (No client); entries without a task land on a per-project Tracked time task. Active Clockify members arrive as invited members — they can't sign in until you invite them from Team — and deactivated members arrive as disabled with their history intact.

Rates are not imported

Clockify's API reports rate amounts ambiguously across plans and endpoints, and importing a wrong magnitude would corrupt billing math. Rather than guess, the import leaves all rates empty — set your billing rates after importing. Hours, billable flags, and everything else come over exactly.

Step 2 — backfill time entries

Select 2 · Backfill time entries. This runs in the background, walking your Clockify history a year at a time. The only before date defaults to your first natively tracked day so nothing double-counts; clear it to import everything. You'll get an email when it finishes.

What happens to edits you have made here

Re-running an import does not overwrite changes you made in Time Trakkr. The import compares three things: what it wrote last time, what the record says here now, and what Clockify says now. A field only changes if you have not touched it since the last import.

Where both have changed — you renamed a client here, and it was renamed in Clockify too — your version wins, and the disagreement is recorded rather than discarded.

Integrations → Kept your version lists those: which record, which field, your value and Clockify's, and when it was last seen. Nothing there is waiting on you; the decision has already been made the right way round. It is there so you can disagree — Keep mine records that you looked and agreed, and Use the source value takes Clockify's value and stops that field conflicting in future.

A field that keeps disagreeing stays a single entry with the date it was last seen, so a weekly import does not pile up copies.