Portmux is a Asana to monday.com migration service that moves your workspaces, projects, tasks, subtasks, custom fields, and dependencies into monday.com boards with the team structure and automations your operations team designed.
Asana and monday.com solve similar problems with different opinions. Asana organizes around Projects with Sections; monday uses Boards with Groups. Asana custom fields are project-scoped; monday columns are board-scoped with type-specific behavior (status, dropdown, mirror, formula). The migration's job is to translate between these models without losing structure or context.
Asana Teams mapped to monday Folders within an Account-level Workspace; Workspace-level membership preserved as Workspace Members in monday.
Each Asana Project becomes a monday Board with the same name, owner, and member access; Project description carried into Board description.
Asana Sections within a Project mapped to monday Groups within a Board with the same order and color/styling preserved where possible.
Asana Tasks migrated to monday Items with task name, assignee, due date, completed status, and tags carried forward.
Asana Subtasks migrated to monday Subitems with parent linkage, assignee, due date, and completed status preserved.
Asana custom fields (text, number, single-select, multi-select, date, people) mapped to monday columns of equivalent type (Text, Numbers, Status, Dropdown, Date, People).
Task and subtask comments migrated to monday Item Updates with original commenter (matched by email), timestamp, and @-mentions translated.
All task attachments downloaded from Asana and re-uploaded to monday Item File columns with original filenames preserved.
Asana task dependencies (block/blocked-by) re-created as monday Dependency column relationships between corresponding items.
Active Asana project templates migrated to monday Board templates with the same group structure, default columns, and pre-populated tasks.
Asana Rules (project-scoped automations) re-implemented as monday Automations on the destination Board with the same triggers and actions.
Asana Goals and milestones migrated to monday as a Goals Board with linked OKRs, progress tracking, and update history preserved.
We connect to Asana via Personal Access Token with admin scope and to monday via API token with admin scope. Asana's REST API enumerates every Workspace, Team, Project, Task, Custom Field, and Rule. Within 48 hours you see a complete project inventory, a custom field translation table, and a Rules-to-Automations mapping draft.
Mapping covers Project-to-Board correspondence, custom field type translation (Asana single-select → monday Status; Asana multi-select → monday Dropdown; etc.), Section-to-Group structure, and Rules-to-Automations re-implementation. We also decide on Folder structure in monday since Asana doesn't have a perfect Folder equivalent.
Monday account loaded with all projects in dependency order (Goals → Boards → Items → Subitems → Comments). Your team validates 5 boards for fidelity. On cutover day, Asana is set to read-only via plan downgrade or member removal, monday becomes authoritative, and we run a final delta of post-cutover Asana activity.
Every migration has its own gotchas. Here's what we plan for on this specific path.
Asana custom field types don't all have direct monday equivalents. Asana's "People" field maps cleanly; "Single-select" maps to monday Status with the same options; "Multi-select" maps to monday Dropdown. Asana's "Formula" field (calculated values) maps to monday Formula columns but the syntax differs, formulas are recreated, not auto-translated.
Asana tasks can live in multiple Projects (a single task appearing in both Engineering and Product Roadmap, for example). Monday Items belong to one Board. We pick the primary Board and add a Connect Boards column to link the Item from secondary contexts, preserving the cross-project visibility Asana provided.
Asana Rules are project-scoped triggers with limited action types. Monday Automations are board-scoped with a richer action set. Most Rules translate cleanly; Asana's "If-Then-Else" rule chains often consolidate into fewer, simpler monday Automations. Each Rule is reviewed in mapping and we document any logic that gets simplified.
Asana Portfolios (which group projects with rollup status) map to monday Workspaces with custom Dashboards. Asana Goals migrate to monday's Goals app or to a dedicated Goals Board with Connect Boards links to project boards. The exact mapping depends on whether your team uses Asana Portfolios for reporting (monday Dashboards) or for permission scoping (monday Workspaces).
Single-system migrations like Asana to Monday run as Track A engagements: one source, one destination, up to 1M records, 4–6 weeks. Final price depends on object volume, custom field count, and integrations, scoped on a 20-minute call before any commitment. See full pricing →
Tell us what's in the source, where it's going, SaaS or custom, and when you need to be live. You'll walk away with a scoped quote, a named engineer, and a go-live date.