Migrate from Asana to monday Work Management

Asana Projects map directly to monday.com Boards. We preserve the project name, description, color, archived status, and default view orientation. Project-level custom fields migrate as Board-level columns; task-level custom fields migrate as Item-level columns. The board's structure (Groups, Items, Subitems) is populated in subsequent phases after the Board container exists. Asana projects with subprojects are handled by creating a monday.com Board per subproject and optionally linking them via a Link to Item column.

Asana Tasks map directly to monday.com Items within a Board. We preserve name, notes/description, start date, due date, assignee, liked (hearts), completion status, and created_at timestamp. Completed tasks retain their completed_at timestamp. Assignee mapping resolves by email to monday.com Board members during import. The Item's status column is mapped to Asana's task completion state.

Asana Subtasks map to monday.com Subitems attached to the parent Item. We recursively export the subtask hierarchy and reconstruct parent-child relationships. Asana allows unlimited subtask nesting depth; monday.com imposes a three-level maximum (Item > Subitem > Subitem). We flag subtask hierarchies exceeding three levels during discovery and present two options: flatten to three levels and note the flattening in the migration manifest, or retain the deeper hierarchy as linked Items with a 'Parent Task Reference' column for manual reorganization post-migration.

Asana Sections (row-level groupings within a project) map to monday.com Groups. We preserve section names and the task ordering within each section. Groups in monday.com are collapsible and display item counts, matching Asana's section behavior. When the Asana project has no sections, we create a default Group named 'Inbox' or map to the Board's main view with no grouping.

Asana custom fields map to monday.com columns with type-aware conversion. Text fields map to Text columns, Number to Numbers, Date to Date, Enum dropdowns to Dropdown columns preserving option labels and colors, and Formula fields to Formula columns using monday.com's formula syntax. Rollup fields do not have a direct equivalent; we flag them for review and either convert to a linked Item formula or exclude with documentation. Custom field colors from Asana are preserved where monday.com column color options exist.

Asana task dependencies use GID references and a dependency_type field (predecessor/successor). We preserve the dependency graph and reconstruct it at monday.com using the native Dependency column. Dependencies must be resolved after all Items are created so that target Item IDs exist. We handle circular dependency detection and flag unresolved references if the target Item was excluded from migration scope.

Asana attachments include both files uploaded directly to Asana and links to external tools (Google Drive, Dropbox, Box). We resolve direct uploads by downloading from Asana's storage and re-uploading to monday.com's file layer, preserving the original filename and upload date. External links are converted to Link to Item columns pointing at the original URL. Attachments exceeding monday.com's 250 MB per file limit are flagged for the customer to upload manually post-migration.

Asana Comments are stored as a Stories resource linked to tasks. We export comment text, author, and created_at timestamp. Updates in monday.com are authored by Board members and display on the Item's timeline. HTML formatting in comments is sanitized to plain text or markdown depending on destination column type. Author resolution matches by email to monday.com Board members; unresolved authors appear as 'Asana User' attribution.

Asana Tags are flat labels applied to tasks across a workspace. We export tag names and colors and map them to monday.com Labels attached to Items. Tags applied to multiple tasks are handled as a bulk label assignment during Item import. monday.com Labels are board-specific, so tags scoped to an Asana workspace-wide taxonomy are applied to each relevant Board independently.

Asana Teams are organizational units grouping members and projects. We export team membership and the list of projects per team. monday.com Workspaces serve a similar organizational function. We match teams to workspaces by name or create new workspaces per the customer's workspace naming convention. Individual users are mapped to Workspace members by email match; users without a matching monday.com account go to a reconciliation queue for the customer to provision before record import resumes.

Asana Portfolios aggregate multiple projects for executive dashboards but store no independent data. We export portfolio metadata (name, owner, description) and the full list of contained project GIDs. monday.com's Dashboard serves a similar cross-board visibility function. We document the portfolio membership list and recommend rebuilding as a monday.com Dashboard with linked Board widgets post-migration. The customer chooses which Boards to pin to the new Dashboard during the rebuild phase.

Asana Goals (OKRs, Advanced tier only) link to Projects, Portfolios, or standalone objectives with timeframes, owners, and progress metrics. monday.com has no native Goals/OKR object. We map goal titles and progress percentages to a dedicated Board (or a designated section within a relevant Board) using Custom Fields for timeframe, owner, and progress. Goals without a clear home Board are migrated to a dedicated 'OKRs' Board. The customer decides on the Goals rebuild strategy during scoping.

Asana Automation rules execute within Asana's native rule engine and have no export representation via API or any known export mechanism. Third-party tools like Flowsana that extend Asana automation are similarly non-portable. We run a pre-migration rule audit to document every active automation (trigger, conditions, actions), then deliver a written rebuild inventory with recommended monday.com Automation equivalents. The customer's admin rebuilds automations post-migration using monday.com's Automation builder or an integration platform like Zapier or Make.

Asana offers List, Board, Calendar, Timeline (Gantt), and Workload views per project. We export view configuration including column order, grouping fields, and sort order. monday.com's view types (Board, Chart, Timeline/Gantt, Calendar, Map, Doc) are Board-level settings. We map Asana view types to monday.com equivalents where they exist and document any view type that has no direct equivalent (e.g., Workload view) for manual reconstruction or third-party tooling.