Move from Asana to Atlas.
To move from Asana to Atlas, export each project as CSV or JSON from the project menu, then import the file into Atlas. Task titles, descriptions, statuses, priorities, and dates come into Atlas as tasks. Assignees, sections, and custom fields are in the export, but you set them in Atlas after the import. Asana rules, portfolios, and the exact board layout do not transfer, and this guide is specific about what you will rebuild.
Export your data from Asana.
Asana exports one project at a time to CSV or JSON from the project header menu. For a whole organization, an admin can request a full JSON export from the admin console. You do this in Asana before opening Atlas.
- Open the project you want to move. Go to the project in Asana. Click the project name dropdown at the top, or the
•••more menu next to it. This is where per project export lives. - Choose Export, then CSV or JSON. In the menu select
Export/Print, then pick CSV for a spreadsheet of tasks, or JSON for a fuller structured file. Use CSV for Atlas. JSON preserves more nesting, but the Atlas importer reads flat rows. - Repeat for each project. Asana exports per project, so run the export once per project you plan to move. Keep the files named by project so the import stays organized. Teams with many projects usually move the active ones first.
- For a full org export, use the admin console. If you are a workspace admin on a plan that allows it, open the admin console and request a full data export. Asana prepares a JSON archive of the organization and emails a link when it is ready.
- Download and verify. Save each file and open it once. Confirm task names, assignees, due dates, sections, and custom fields are present. Fix anything missing by adjusting the columns shown in the project before re exporting.
Note: a CSV export follows the columns visible in the project's list view, so add the custom fields you want before exporting. Attachments are referenced by link rather than bundled into the file.
What carries over, and what does not.
Asana holds a lot of structure that a per project export cannot fully represent. Here is the real split.
Carries over cleanly
- Tasks and core fields. Task name, description, assignee, due date, start date, and completion status all export as columns or JSON fields.
- Sections and columns. The section a task sits in exports as a value, so you can rebuild the same grouping in Atlas.
- Custom fields. Text, number, dropdown, and date custom fields export as columns, so the values are in your file. The Atlas task import does not read them, so recreate the fields you need in Atlas.
- Subtasks. Subtasks export as rows. The Atlas importer creates flat tasks, so reconnect the parent and child links that matter after the import.
Does not carry over, and must be rebuilt
- Rules and automations. Asana rules are project logic, not data. They do not export. You rebuild the ones you use with Atlas automations.
- Portfolios and goals. Portfolios roll up projects, and goals sit above them. Neither is part of a project export. You recreate the roll ups you need in Atlas Projects and Goals.
- Dependencies across projects. A dependency inside one project can survive in JSON, but a dependency that crosses projects exports as a reference, and you reconnect it in Atlas after the import.
- Board layout and saved views. Board, timeline, and calendar arrangements are not in the file. The tasks are; the views are not, and they are quick to rebuild in Atlas.
- Comment threads. Task comments do not travel in a CSV. If a decision lives in a comment, move it into the task description before you export.
Import into Atlas.
Importing tasks is quick. The payoff is that in Atlas those tasks live with docs, CRM, contracts, and an assistant that can act on the whole graph.
In Atlas, open Settings, then Data, and use Import to load a CSV file, or a JSON list of tasks, into the project you choose. The importer reads columns named title, description, status, priority, dueOn, and startsOn, so rename the matching Asana columns before you upload. Rows without a title are skipped, and Atlas tells you how many tasks it created. For example, Name becomes title and Due Date becomes dueOn. Import each Asana project into its own Atlas project.
Once imported, the same work feeds Tasks and Projects, and Ask Atlas reads all of it. Ask it to rebuild your board by section, assign the unassigned, and list everything overdue, and it does the work. An assistant that acts on your project, rather than one that only summarizes it, is the reason to move.
Try the import free to start, then invite the team. The full product is described on the Atlas overview.
Asana and Atlas, compared.
Asana is a mature, well designed project and work management tool with strong portfolios and reporting. Atlas is a wider surface with an assistant that acts. Both are accurate. Choose by what you actually need.
| Capability | Asana | Atlas |
|---|---|---|
| Work and project management | Mature and polished | Strong, on a shared graph |
| Portfolios and roll ups | Well built portfolios and goals | Projects and Goals with live roll ups |
| Native CRM | Not built in | 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 | 39 PDF tools inside the tenant |
| Assistant that takes action | AI summarizes and drafts | Reads your data, then creates and moves records |
| Number of tools replaced | Project management | 16 modules in one workspace |
| Security certifications | Holds independent audits | None held today, stated on the trust page |
| Entry price | Free basic, paid per member | Free to start |
Pricing and features change. Check the current Atlas numbers on the pricing page, and Asana's on their own site.
Migration questions.
The things people ask before they move a team off Asana.
Should I export Asana as CSV or JSON?
Use CSV for the Atlas import. Asana's JSON export is a nested file rather than a flat list of tasks, so it does not load directly, and the Atlas importer does not keep subtask links either way.
Do Asana rules and automations transfer?
No. Rules are project logic and are not part of an export. You rebuild the automations you depend on in Atlas, which uses the same trigger and action pattern, so many rules translate directly.
Can I move projects one at a time?
Yes, and Asana exports per project anyway, so a phased move is natural. Export and import your active projects first, verify them in a free Atlas workspace, then bring across the rest.
What happens to portfolios and goals?
Portfolios and goals are not part of a project export. You recreate the roll ups that matter in Atlas Projects and Goals, which read from the same tasks you imported, so the numbers stay grounded in real work.
Is Atlas as compliant as Asana for enterprise review?
No. Atlas holds no security certifications today, and the trust page says so directly. If your migration must clear a procurement requirement for an audited vendor, Asana or another certified tool is the right answer.
Who should not migrate.
Some Asana teams should stay put. Here is who.
Do not migrate if
- Your procurement requires an audited vendor. Atlas holds no certifications yet. If a SOC 2 report is a gate, this is not your move.
- Portfolios and goals reporting are central to how you run. Asana's roll up reporting is mature. If executives live in those views, weigh the rebuild carefully.
- You have hundreds of active projects with heavy rules. A per project export plus rule rebuilding at that scale is a project of its own.
- You only need project management. Atlas earns its place by replacing several tools. If tasks and projects are all you want, Asana already does that well.
Migrating from a different tool? Read the guides for Notion, ClickUp, and HubSpot.
Put Asana work on one graph.
Export from Asana, import into Atlas, and give your tasks, docs, and pipeline a single work graph with an assistant that acts. It is free to start, so you can test the import before you commit the team.