ClickUp

Sign in to ClickUp and tick the Workspaces to move (OAuth). Shuttio reads what that user may see in those Workspaces, never writes to ClickUp, and deletes its access 14 days after the migration finishes.

Object by object: What objects are supported for ClickUp migrations.

What Shuttio reads and moves

The list below describes the move into Odoo. Where Clarify or Odoo differ, the destination's own article says so.

• Lists: Every List the signed-in user sees in the Workspaces you ticked, archived ones too. A List in a Folder is named "Folder / List". The Workspace, Space and Folder names become tags, and an archived List is marked archived (its stage, or a tag where Odoo has no project stages).
• Statuses: Each List's statuses, in ClickUp's order, become the task stages of its project in Odoo. A closed or done status is the done stage. Odoo's own default stages are taken off a project Shuttio creates, so its board is exactly yours.
• Tasks: Each task goes to its List's project and its status's stage, with its description (Markdown where ClickUp returns it), due date and tags. Closed and archived tasks are carried; an archived task is marked done and tagged "Archived in ClickUp".
• Subtasks: A subtask becomes a subtask of its parent task in Odoo, in the same project.
• Priority: Urgent and high priority become Odoo's star on the task. Every priority is also named in the description.
• Start date and time estimate: Added to the top of the description as lines ("Start: 2026-05-01", "Time estimate: 1.5 h"): the Odoo writer has no field for them yet.
• Checklists: Added to the task description as a markdown task list, items checked or not as in ClickUp.
• Comments: Added to the end of the task description, oldest first, each with its author and date (up to 50 a task).
• Assignees: The first assignee becomes the task's assignee when the Odoo user with the same email exists. Further assignees are named in the description.
• Attachments: With the Attachments checkbox ticked, each file attached to a task is downloaded and attached to its Odoo task, on the full migration only (the sample moves none). A file over 50 MB is a failed row that names it.

Where each thing lands

Notes, tasks, meetings, calls, files, owners and lists depend on the destination. This is the row for ClickUp, generated from the same tables the runner uses:

Each destination's own article says how its data is written: Odoo, Asana, Trello.

Permissions and why

Sign in as a user who is a member of every Space you are moving, and tick every Workspace you are moving: Shuttio sees no other. ClickUp allows 100 requests a minute per token on the Free, Unlimited and Business plans; a large Workspace takes a while, and the run pauses when ClickUp asks it to slow down until you resume it. Shuttio's access is stored encrypted and deleted 14 days after the migration finishes. If ClickUp stops accepting it, the run pauses and asks you to reconnect ClickUp.

Known limits

• Custom fields, docs, goals, time entries, dependencies, views, automations: They have no place in the Project app, or the Odoo writer does not carry them yet.
• Activity history: Only comments are read; status changes and other task activity are not.
• Odoo without the Project app: The Objects step hides the objects and says so; install Project in Odoo and run again.
• Rate limits: ClickUp allows 100 requests a minute per token on Free, Unlimited and Business plans. Shuttio stays under that, so a large Workspace takes a while, and pauses the run if ClickUp asks it to slow down for longer than a minute; Resume carries on.
• Emails: Shuttio reads no emails from ClickUp.
• Large and linked files: a file over 50 MB, and an entry that is only a link, is listed as a failed row and not copied.