\n| Portfolio<\/td>\n | Dashboard<\/td>\n | Different model; rebuild<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n The one to watch is subtasks<\/strong>. Asana allows deep nesting; monday.com’s subitems are one level. If you rely on three-deep subtasks, decide now whether those become subitems, separate items, or checklist entries in an item’s update.<\/p>\nStep 3: Run the Import<\/h2>\nmonday.com provides a documented Asana importer.<\/p>\n \n- In monday.com, open the account menu and find the import option.<\/li>\n
- Choose Asana and authorise the connection to your Asana account.<\/li>\n
- Select the projects you marked active. Do not select everything.<\/li>\n
- Run the import and wait.<\/li>\n<\/ol>\n
What generally comes across: task names, descriptions, assignees, due dates, sections as groups, subtasks as subitems, and many custom fields.<\/p>\n What generally does not: rules and automations, dependencies in some configurations, comment threads in full fidelity, attachments in some cases, and portfolio structures.<\/p>\n Step 4: Verify Before You Trust It<\/h2>\nCheck these five things on every imported board. This is the step people skip and regret.<\/p>\n \n- Assignees.<\/strong> If someone’s Asana email differs from their monday.com email, their tasks arrive unassigned. Filter for unassigned items and fix.<\/li>\n
- Due dates.<\/strong> Spot-check ten items against Asana, particularly anything with a date range rather than a single due date.<\/li>\n
- Custom fields.<\/strong> Dropdowns and number fields usually map; formula and lookup fields usually do not.<\/li>\n
- Subtasks.<\/strong> Confirm nothing deeper than one level was silently flattened or dropped.<\/li>\n
- Attachments.<\/strong> Open three items that had files. If files are missing, download them from Asana before you cancel anything.<\/li>\n<\/ol>\n
Step 5: Rebuild Automations<\/h2>\nNone of your Asana rules transfer. Rather than recreating all of them, use this as a cull \u2014 most teams find half their rules were never useful.<\/p>\n List the Asana rules that actually fired regularly, then rebuild those in monday.com’s automation centre. The common ones map cleanly:<\/p>\n \n- When status changes to Done, move item to a Done group<\/li>\n
- When a due date arrives, notify the assignee<\/li>\n
- When an item is created in a form, assign to a person and set a status<\/li>\n
- When status changes to Blocked, notify the board owner<\/li>\n<\/ul>\n
Build them one at a time and test each with a dummy item before moving on. Automations that misfire silently are worse than none.<\/p>\n Step 6: Rebuild Views and Dashboards<\/h2>\nAsana’s List, Board, Timeline and Calendar views have monday.com equivalents, but they are configured per board and do not import.<\/p>\n Build one default view per board first \u2014 the one your team looks at daily. Add dashboards afterwards, once people are working in the tool and can tell you what they actually want to see.<\/p>\n Step 7: Run Both in Parallel for Two Weeks<\/h2>\nKeep the Asana subscription active. Make monday.com the system of record from an announced date, but leave Asana readable.<\/p>\n Two weeks is usually enough for someone to discover a missing attachment or a project nobody flagged. After that, export a final backup and cancel.<\/p>\n Step 8: Onboard the Team<\/h2>\nFifteen minutes, live, everyone. Cover the vocabulary change (project becomes board, task becomes item), where their daily view is, and who to ask when something is missing.<\/p>\n Name one person as the owner for the first month. They approve new boards and column changes so the account does not sprawl in week two.<\/p>\n |