What objects are supported for Toggl Track migrations
What Shuttio moves out of Toggl Track: client, workspace, project, task, time entry, user. The table shows what each Toggl Track object becomes.
Last updated: 20 November 2026
Shuttio moves data out of Toggl Track. It does not write into Toggl Track. Out of Toggl Track, data goes into Odoo.
What Toggl Track calls each object
| In Toggl Track | What Shuttio moves | Note |
|---|---|---|
| Client | Companies | A client already in Odoo is matched by name and linked. An archived client says so in the internal note. |
| Workspace | A tag on its projects | Shuttio reads every workspace the token's user belongs to. |
| Project | Projects | Client as customer, name, start and end dates. Billable, rate, fixed fee and estimated hours are one line of the description. |
| Task (paid plans) | Project tasks | A task that is no longer active 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. |
| 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 Toggl Track.
← What objects are supported for Klaviyo migrationsWhat objects are supported for Clockify migrations →
Not answered here? Email help@shuttio.com.