Skip to content
Get a quote

How do I migrate from Monday.com to Asana?

Short answer

Export each monday board to Excel, save it as CSV and import it with Asana's CSV importer. That supports assignees, due and start dates, dependencies, followers and custom fields. Subtasks can be set with a "Subtask of" column. Asana doesn't document importing attachments or comments by CSV, so move files and updates separately, then rebuild monday automations as Asana rules.

By

What moves natively

monday.comNative exportAsana CSV importResult
ItemsExcel per board (up to 100,000 items)TasksWorks
People columnNames or emailsAssignee (one per task, by email)Works if users are in Asana
Date and timeline columnsExportedDue and start datesWorks
Status and dropdown columnsExportedCustom fields, or sectionsSections only appear when you move tasks into them
SubitemsCan be added to the export”Subtask of” columnTest it first
DependenciesExported as a columnDependenciesMap by task name
Updates (comments)Separate tab; subitem updates not exportedNot documentedAdd as description text or through the API
FilesAccount export zip with all boards and filesNot documentedAttach through the API
Automations, integrationsNot exported—Rebuild as Asana rules

Steps

  1. Invite users to Asana with the same emails they use in monday.
  2. Plan the structure: a monday workspace usually becomes an Asana team, a board a project, and a group a section.
  3. Create shared custom fields in Asana’s library for columns used across boards.
  4. Export each board to Excel with subitems, convert it to CSV, and clean up the people and date columns.
  5. Import one board, check it, then import the rest.
  6. Move updates and files through the Asana API, matching tasks by name or a kept monday item ID.
  7. Rebuild automations as Asana rules and recreate dashboards.

What the native tools do / where they stop

Both platforms handle the basic task list. Neither moves the history of the work: comments, files and status changes. Asana’s CSV importer is documented for fields, not for attachments or comments. monday’s Excel export keeps updates but drops subitem updates. If the reason for the move includes “keep the context”, plan an API step for comments and files.

Where FlitStack AI fits

FlitStack AI migrates tasks with comments, attachments, subtasks and dependencies between PM tools, with users matched by email. See PM migrations or talk to us.

Questions, answered

A few useful answers.

Does Asana have a direct monday.com importer?

Not one that Asana documents. The documented path is CSV. monday's own importer works in the other direction (Asana into monday) and supports only a short list of fields.

Do monday subitems become Asana subtasks?

They can, through a 'Subtask of' column naming the parent task. That comes from Asana staff replies on the forum rather than the help docs, so test it on one board.

Do custom fields stay?

Custom fields created during a CSV import are local to that project. If several projects need the same field, create it in the organization's library first and map to it.

A closer look

Tell us what you’re moving.

Share your source, destination and rough record counts. We scope the migration and the process work with you and send you a quote.

Get a quote