Move from ClickUp to Atlas.
To move from ClickUp to Atlas, export your tasks to CSV or Excel from the ClickUp export tools, then import the file into Atlas. Tasks, statuses, assignees, due dates, and custom fields come across as structured records. ClickUp automations, dashboard widgets, and nested subtask relationships need to be rebuilt, and this guide tells you exactly which ones.
Export your data from ClickUp.
ClickUp has a data export in its settings, and a per view export on any List. The account level export is an owner or admin action and is available on the paid plans. You do all of this inside ClickUp before you open Atlas.
- Open the workspace export. Click your workspace avatar, then
Settings. In the sidebar chooseImport/Export, then theExporttab. This is the account wide export and it belongs to the workspace owner or an admin. - Or export a single List. If you only need part of the account, open any List, click the
•••menu at the top right, and chooseExport. You can export that view to CSV, Excel, PDF, or Markdown without touching workspace settings. - Choose CSV or Excel. Pick CSV for the cleanest import, or Excel if you want to review the data in a spreadsheet first. CSV keeps task name, status, assignees, priority, due dates, time estimates, and every custom field as columns Atlas can map.
- Include the fields you care about. Before you export, make sure the view shows the columns you want, because a List export follows the visible columns. Add custom fields, tags, and dates to the view so they land in the file. Hidden columns do not export.
- Run the export and download the file. Start the export. ClickUp prepares the file and either downloads it or emails a link for larger accounts. Save the
.csvor.xlsx, then open it once to confirm your tasks and fields are all present before importing.
Note: ClickUp Docs export separately as Markdown or PDF from within each Doc, and attachments are referenced by link in the task export rather than bundled. Pull any Docs you need down alongside the task CSV.
What carries over, and what does not.
ClickUp is deeply configurable, and configuration is exactly what a CSV cannot hold. Here is the real split.
Carries over cleanly
- Tasks and their core fields. Task name, description, status, assignees, priority, due dates, start dates, and time estimates all export as columns.
- Custom fields. Text, number, dropdown, date, and label custom fields export as their own columns and map straight onto Atlas fields.
- Tags and lists. Tags come across as values, and the List a task belongs to becomes a grouping you can turn into an Atlas project.
- Comments as text. A List export can include the latest comments as a column, so key context travels even though threading is lost.
Does not carry over, and must be rebuilt
- Automations. ClickUp automations are workspace logic, not data. They do not export. You rebuild the ones you rely on with Atlas automations, which use the same when this then that shape.
- Dashboards and widgets. Dashboard cards are views over live data. The data exports, the dashboards do not. You recreate the reports you need in Atlas Analytics.
- Subtask nesting depth. A CSV is flat. Deeply nested subtask trees export as rows with a parent reference, and you reconnect the hierarchy that matters during import.
- Dependencies and relationships. Task dependencies and linked tasks export as references, not live links. Reconnect the critical path in Atlas.
- View settings. Board, Gantt, calendar, and workload views are not in the file. The tasks are; the saved views are not. You rebuild views in Atlas in minutes.
Import into Atlas.
A CSV of tasks is the easy part. The reason to move is that in Atlas those tasks share a graph with docs, CRM, contracts, and an assistant that can act on them.
Sign in to Atlas and open Import from the workspace menu. Upload the ClickUp CSV and map each column to an Atlas field: name, status, assignee, priority, due date, and every custom field. Choose which List becomes which Atlas project. Atlas previews the mapping so you can fix anything the importer guessed before it writes a single record.
After the import, the same tasks power Tasks and Projects, and Ask Atlas can read the whole set. Ask it to rebuild your board, assign unowned work, and surface everything past due, and it performs the actions rather than listing them. That is the difference between an AI that describes your backlog and one that clears it.
Test the import on the free Starter plan for up to 5 seats, then scale to the rest of the team. The full product is on the Atlas overview.
ClickUp and Atlas, compared.
ClickUp has deeper project management configurability than Atlas, with more granular settings and view types. Atlas trades some of that depth for one graph across 16 modules and an assistant that acts. Both are fair descriptions.
| Capability | ClickUp | Atlas |
|---|---|---|
| Project management depth | Very deep, highly configurable | Strong, deliberately simpler to run |
| View types | Many, including workload and mind maps | List, Board, Calendar, Timeline |
| Native CRM | Built from custom lists | Purpose-built CRM on the same graph |
| Contracts and e-signature | Not built in | Draft, redline, and sign in the workspace |
| PDF editing tools | Not built in | 32 PDF tools inside the tenant |
| Assistant that takes action | ClickUp Brain writes and answers | Reads your data, then creates and moves records |
| Reported pain | Often described as complex and slow to load | Fewer surfaces, one place for the work |
| Security certifications | Holds independent audits | None held today, stated on the trust page |
| Entry price | Free personal, paid per member | Free up to 5 seats, then $24 per seat |
Pricing and features change. Confirm the current Atlas numbers on the pricing page, and ClickUp's on their own site.
Migration questions.
The things people ask before they move a team off ClickUp.
Do my ClickUp custom fields come across?
Yes, as long as they are visible in the view you export. Text, number, dropdown, date, and label fields each export as a column, and Atlas maps them onto its own fields during import. Add any hidden custom fields to the view before exporting so they are included in the file.
Will my automations transfer?
No. ClickUp automations are workspace logic and are not part of a data export. You rebuild the ones you depend on using Atlas automations, which follow the same when this then that pattern, so the translation is usually quick.
Can I move one Space or List at a time?
Yes. Export a single List from its menu, import it into a free Atlas Starter workspace, and verify it before moving more. A phased move by team or by Space is the safer path and Atlas does not require a single cutover.
What about deeply nested subtasks?
A CSV is flat, so nested subtasks export as rows carrying a parent reference. Atlas can reconstruct one level of parent and child cleanly, and for very deep trees you reconnect the branches that matter during import rather than every leaf.
Does Atlas meet the same compliance bar as ClickUp?
No. Atlas holds no security certifications today, and the trust page states that plainly. If your move is gated by a procurement requirement for an audited vendor, ClickUp or another certified tool is the right choice, and we will tell you so.
Who should not migrate.
Some ClickUp teams should stay. Be honest with yourself about which one you are.
Do not migrate if
- Your procurement requires an audited vendor. Atlas holds no certifications yet. If you must show a SOC 2 report to pass review, this is not your move.
- You rely on ClickUp's most granular configurability. If custom statuses per space, workload views, and heavy automations are load bearing for you, ClickUp is deeper than Atlas at that specific job.
- You run everything through ClickUp dashboards. Those do not transfer, and rebuilding a large dashboard library is real effort.
- You only need a project tracker. Atlas pays off when it consolidates several tools. If tasks and projects are your whole world, the wider surface is more than you need today.
Migrating from a different tool? Read the guides for Notion, Asana, and HubSpot.
Trade complexity for one graph.
Export from ClickUp, import into Atlas, and put your tasks, docs, and pipeline on a single work graph with an assistant that acts. Starter is free for up to 5 seats, so you can test the whole import before you commit.