What objects are supported for Clockify migrations
What Shuttio moves out of Clockify: client, workspace, project, task, time entry, user and more. The table shows what each Clockify object becomes.
Last updated: 20 November 2026
Shuttio moves data out of Clockify. It does not write into Clockify. Out of Clockify, data goes into Odoo.
What Clockify calls each object
| In Clockify | What Shuttio moves | Note |
|---|---|---|
| Client | Companies | A client already in Odoo is matched by name and linked. The client's note and an Archived line go in the internal note. |
| Workspace | A tag on its projects | Shuttio reads every workspace the key's user belongs to, from the region you chose. |
| Project | Projects | Client as customer and the name. Its note starts the description; billable, hourly rate and estimated hours are one line after it. |
| Task | Project tasks | A task with the status Done lands in the Done stage. |
| Time entry | Timesheet lines | Date, hours, project, task and description. Billable and tags go in brackets after the description. A running timer is left out. |
| User | Matched to an Odoo employee by email | No employee or user is created. |
| Entries with no project | A project called No project | Added for each workspace and rolled back with the migration unless a timesheet line of yours is on it. |
| Invoices and expenses | Not moved | They have no place in Odoo's Project and Timesheets apps. |
For the permissions Shuttio needs and what does not move, see reading from Clockify.
← What objects are supported for Toggl Track migrationsWhat objects are supported for Greenhouse migrations →
Not answered here? Email help@shuttio.com.