How to migrate from Clockify to Nimbos without losing your time history
Updated October 18, 2026
You migrate through the Clockify API, one month at a time: a Nimbos admin pastes the API key, picks a month and syncs it. The hours come over — person, project, activity, description, start and end; rates, amounts and the billable flag stay behind, because each project's price is set in Nimbos. Syncing the same month again creates no duplicates: Nimbos mirrors Clockify, with the exceptions in the table below.
Before you start
- Who does it: someone with the Import hours (spreadsheet and Clockify) permission in Nimbos. The Admin role has it out of the box.
- Where the hours come from: the detailed report of the workspace that is active for the account that owns the key. Whatever that account cannot see in Clockify, Nimbos does not receive either — check the workspace before connecting.
- Stop running timers: an entry with no end time is skipped. The sync result names it so you can fix it in Clockify.
Step by step
- In Clockify, generate the API key under Profile settings → API.
- In Nimbos, open the admin area, Import section, and paste the key under Sync via the Clockify API. Nimbos checks the key before saving it, stores it encrypted and never shows it back.
- Pick the month to sync and click Sync month. The result tells you how many entries came in, how many already existed and what was left out, with the reason.
- Repeat for every month of history you want to bring over.
- Review the people and projects that were created. Anyone not yet in Nimbos is created from their email address, and each new person takes up a license.
What comes over from Clockify — and what doesn't
| In Clockify | In Nimbos |
|---|---|
| User | Person, matched by email — created if missing |
| Project and client | Project, created by name, with the client name |
| Task | Project activity |
| Description, start and end | The same, on the time entry |
| Tag or task named HORA EXTRA | Entry flagged as overtime |
Not imported: the billable flag and amounts — rates and prices are set in Nimbos, per project and per job title —, other tags, timers that are still running and zero-length entries.
Syncing again: what happens in each case
Nimbos recognizes an imported entry by three things: the person, the start and the end. Within the synced month it mirrors Clockify — and that rule decides every case:
| What happened in Clockify | What happens in Nimbos |
|---|---|
| New entry | It comes in |
| Entry already synced, unchanged | It stays as is — nothing duplicates |
| Time changed (start or end) | The old version goes and the new one comes in |
| Only the project, activity, description or tag changed, same time | Not updated: by person and time it is the same entry, so the earlier version stays. Fix it in Nimbos too |
| Entry deleted | It is removed from Nimbos |
| Entry already invoiced, in an approved month, in a closed hours review or of a deactivated team member | It stays in Nimbos even if deleted or changed there; the result shows the conflict and why. If it was changed, the new version may come in alongside it — resolve the conflict so the hour isn't counted twice |
| New entry in an already approved month, or of a deactivated team member | It doesn't come in; the result shows the conflict and why |
Heads-up: changing only the project, activity, description or tag of an entry in Clockify, without touching its time, does not reach Nimbos — the sync recognizes the entry by person and time. Make the same fix in Nimbos.
Entries typed directly into Nimbos are never touched by the sync, and every removal is written to the audit log. Two entries for the same person with exactly the same start and end count as one: the second doesn't come in.
That lets you run both tools side by side during the switch: the team keeps logging in Clockify, and you re-sync the month as often as you like until you cut over. If someone already logs directly in Nimbos, the result warns you — check it so the same hour isn't counted twice.
Limits worth knowing
- Up to 20,000 entries per sync, one month at a time.
- On Clockify's free plan, the API accepts 30 requests per hour per workspace, according to their documentation. If Clockify rejects a request for hitting the limit, wait and sync the month again — it won't duplicate.
- The sync relies on Clockify's detailed report. If it doesn't come back, Nimbos tells you instead of importing half a month.
No API access? Import a file instead
If you can't use an API key, bring the hours in as a file — CSV, TXT or XLSX —, mapping the columns once and saving the mapping as a layout. Nimbos provides a template with one column per field: person, email, date, start, end, hours, project, activity, description and overtime.
With a file, the projects must already exist in Nimbos, and importing the same period again replaces that person's hours on that project — it doesn't add them up.
After the migration, your exports keep working
Nimbos exports hours as a CSV with the same columns, in the same order, as Clockify's detailed report — without the Group column. The CSV column names are always in Portuguese, whatever language your team uses: it is a fixed format, kept unchanged for the scripts that already read it. If your scripts were written for an English-language Clockify export, map the column names once.
For Excel there is also a spreadsheet version (.xlsx): its headers follow your interface language, the Task column is called Activity, and dates, times and durations come out as numbers, ready to sum and sort.
With the hours in Nimbos, each project's margin comes from the same records — see how to calculate project margin.
Frequently asked questions
Do I have to stop using Clockify on migration day?
No. Syncing again mirrors Clockify, so both can run side by side while the team adapts. You decide when to cut over.
Do Clockify rates and amounts come over?
No. Nimbos does not read amounts from Clockify: prices are set per project and per job title inside Nimbos, and so is each person's cost.
What happens to people who don't have a Nimbos account yet?
They are created from their email address on the first sync and take up a license.
How Nimbos handles this
Keep reading
Sources
- Clockify API — official documentation (API key, detailed report and rate limits) — accessed October 18, 2026