ClickUp's five-export limit, and the permissions behind it

1. What can you actually export from ClickUp?

ClickUp does not have one export. It has seven, each covering a different part of the product, each with its own format and its own conditions. There is no single button that produces your workspace.

The practical consequence is that "exporting ClickUp" is a checklist rather than an action. Tasks, Docs, Dashboards and Whiteboards each need a separate pass, and the Whiteboards come out as images either way.

2. Which plan and role do you need to export?

Two limits apply, and they are independent of each other: how many view exports your plan allows, and whether your role is permitted to run one at all. ClickUp's import and export availability page covers both.

Five is a total, not five per view, and it covers Docs, Dashboard cards, Whiteboards and Form responses as well as List and Table views. A free or Unlimited workspace with a dozen Lists therefore cannot be exported view by view, which makes those five worth spending deliberately rather than experimentally.

ClickUp's own pages disagree on this. Its views availability table shows Free Forever as having no view exports at all, while the import and export page quoted above gives Free Forever and Unlimited five each. Test one export on your own account before planning around either number.

Two permissions, not one

Exporting is governed by two separate Workspace permissions. Export Views covers List and Table views, Docs, Dashboard cards, Whiteboards and Form responses. Exporting covers task data through the Workspace export settings.

They are granted differently. ClickUp states that "to export views, users must have permissions at both the Workspace level and the location level" - a member needs at least Edit permission on the List as well as the Export Views permission, which is on by default. The Exporting permission for task data is the opposite: off by default for members, and on for admins and owners.

Guests cannot export at all, in any variant. That catches contractors and clients: someone working in your Workspace as a guest can build and use views and take none of it with them, so a member has to run the export for them.

3. How do you export your whole ClickUp workspace?

This is the broadest route and the one to start with:

1. In the upper-left corner, click your Workspace avatar and select Settings.
2. In the All settings sidebar, select Imports / Exports.
3. Click Export Items.
4. Click the Select locations dropdown and choose the Spaces, Folders, Subfolders or Lists to export.
5. Click Start Export, then Download Export when it finishes, and save the CSV.

You also receive an email containing a link to the file.

One line in ClickUp's instructions is worth reading as a warning rather than a tip: "exporting only the items you need increases the chances of your export succeeding." That is ClickUp telling you, in the middle of the happy path, that a whole-workspace export may not complete. On a large workspace, plan to export Space by Space rather than selecting everything and hoping.

4. How do you export a List or Table view?

This is the route that carries Custom Fields, which for most ClickUp workspaces is the difference between a useful file and a list of task names.

1. Open the List or Table view you want.
2. In the upper-right corner, click Customize, then Export.
3. Choose what to export: Visible columns, Task names only, or All columns.
4. Choose CSV or Excel, then click Download.

Pick All columns unless you have a reason not to. It exports every field for the tasks in the view regardless of what is currently on screen, which is what you want when the file is an archive rather than a report. Visible columns exports only what you can see, and has one useful side effect worth knowing: with it selected, closed tasks appear in the export too.

If you choose CSV you also get format controls that matter later. Dates can come out as Normal, ISO or POSIX, and times as either 10h 5m or 10:05. Choose ISO for dates if anything is going to read the file programmatically, because it sorts correctly as text and needs no conversion.

5. What is actually inside a ClickUp export?

More than most. The workspace CSV documents these fields, among others: task ID and link, task type, custom ID, name, description, status, created, due and start dates, parent ID and subtask IDs, assignees, tags, priority, List, Folder path and Space names, time estimated, checklists, comments, the count of assigned comments, time spent and rolled-up time.

Comments and time tracking in a plain CSV put ClickUp ahead of most of its competitors on paper. A Trello CSV export has no comments in it at all, and Asana's route to a full time-entry export is a Python script against its API.

Three things about the file are worth setting expectations on.

Custom Fields are not in the documented field list. Everything above comes from ClickUp's own inventory of what a workspace export includes, and Custom Fields do not appear in it. Since the view export explicitly does carry them, the practical rule is: if your work lives in Custom Fields, the workspace CSV is not your export, and the route that is depends on your plan.

Attachments arrive as links, not files. The column holds a small JSON structure of filenames and URLs. That is more useful than it sounds, because ClickUp's attachment links do not expire and do not require authentication, so they keep working. It is still not a copy of your files.

Dates come twice, once in Unix time. ClickUp includes date and time fields in both Unix format and plain text, and points you at an epoch converter. Nothing is lost, but a spreadsheet opened straight from the file will have columns of ten-digit numbers next to the readable ones.

6. Why did your export fail or arrive incomplete?

Four documented reasons, and the first two are the ones that produce a file which looks fine.

Collapsed groups are excluded. ClickUp states plainly that "collapsed groups are not included in the export". If your view is grouped by status or assignee and you have collapsed a few groups to make the screen readable, those tasks are simply absent from the download. Expand everything before exporting.

Subtasks are off unless you turn them on. Before exporting a view, set the Subtasks control in the upper-right corner: in List view choose As separate tasks, and in Table view toggle on Showing Subtasks. A workspace that puts real work in subtasks can otherwise export a fraction of itself.

The link expires in an hour. ClickUp's documentation is explicit: "download links sent via email expire after 1 hour". Start the export when you are able to deal with the file, not at the end of the day.

Large exports may not complete. Covered above, and the documented mitigation is to select fewer locations. If a workspace-wide export keeps failing, that is the fix rather than a support ticket.

7. How do you move ClickUp lists to Jira, Asana or a spreadsheet?

Which file you can produce decides most of this, so read section 2 first. A workspace that has spent its five view exports cannot produce another file containing Custom Fields, and no destination can receive what the file never held.

ClickUp to Jira

Jira ships a first-party ClickUp importer at Settings → System → External system import, and it reads your ClickUp account rather than a file, so none of the export gates apply. The constraint is volume instead: Atlassian documents a cap of 10 Lists per import. A workspace with fifty Lists is five runs, and you need admin rights on the Jira side for each.

ClickUp to Asana or Notion

Neither has a ClickUp importer, so both are the CSV route and both lose the things ClickUp is unusually good at exporting. Asana's CSV importer reads task name, description, section, assignee and collaborators, and has no column for comments or tracked time, so the two fields you were pleased to find in the ClickUp file have nowhere to go. Notion's CSV import cannot create relations, and Notion warns that imports add rows rather than updating them, so a retry after a failed run leaves two copies.

Both are worth a pilot with one List. The thing to check afterwards is not whether the tasks arrived but whether the Custom Fields did, because that is where ClickUp work usually lives.

ClickUp to Excel or Google Sheets

The most direct case. A List or Table view exports as Excel with no conversion step, so choose All columns and open the result. The workspace route gives CSV, which Google Sheets takes through File → Import → Upload. Remember the dates arrive twice, once as Unix timestamps, and that collapsed groups were never in the file.

Destination importers were checked against each vendor's documentation on August 13, 2026.

8. How do you move ClickUp lists into Breeze?

Breeze reads your ClickUp workspace through the API, so no export runs, no plan gate applies and no link expires. It connects with read access, shows what it is about to do, and changes nothing in ClickUp.

ClickUp is the source Breeze carries the most from. It is the only one of the eight supported tools where tags, custom fields, comments, subtasks, time tracking and attachments all come across. The attachments work because ClickUp's file links do not expire and need no authentication, which is not true of Notion, Airtable, monday.com or Asana, where Breeze has to skip them.

Running the import

In Breeze, open the menu in the top-right corner, select Settings, open the Import tab and select Import next to ClickUp. The wizard runs in four steps: connect, choose the lists, match people, and review before anything is written. There is no field-mapping step: if your list has a Board view, Breeze reads its columns, and otherwise it uses the list's statuses.

Only a Breeze account owner or admin can import a whole workspace as new projects. Importing a single list into a project you already have works from that project's settings instead.

What comes across from ClickUp

Two honest limits. Attachments are stored as links rather than copied into Breeze, so they still depend on the ClickUp workspace continuing to exist. And ClickUp's Docs, Dashboards and Whiteboards are not tasks, so they are outside what a task importer can carry: those need the separate exports in section 1 whatever you move to.

Large imports keep running in the background and Breeze emails you when they finish. Importing the same list again offers to update the project it created last time rather than making a second copy, and it never deletes what you have added in Breeze.

Common questions about exporting ClickUp data

Can you export ClickUp on the free plan?

Yes, with a ceiling. Task export from the workspace settings is available, and Free Forever also gets five List, Table or Form view exports in total, the same allowance as Unlimited. Business and above are unlimited.

Does a ClickUp export include comments and time tracking?

Yes. Both appear in ClickUp's documented list of fields in a workspace task export, along with checklists and rolled-up time. That is unusual: most project tools leave comments out of a CSV entirely.

Why are some tasks missing from your ClickUp export?

Most often because a group was collapsed in the view when you exported, since collapsed groups are excluded, or because subtasks were not switched on. Expand every group and set Subtasks to show before exporting.

Run the export before you need it

ClickUp gives you more in a file than most tools do, so the useful discipline is not choosing a format but confirming access. Check which plan and role you have, run one export now, and look at what came out: whether your Custom Fields are in it, whether the subtask rows arrived, whether any group was collapsed when you clicked.

And if you are moving the work rather than filing it, the export is the wrong starting point, because the gates apply on the way out and not on the way in. See exactly what Breeze imports from ClickUp, then try it with one list before you move the rest.