Migrate from Wrike to monday Work Management

Wrike Spaces (top-level shared or personal organizational containers) map to monday.com Workspaces. Permission inheritance in Wrike is tied to Space membership; we export Space assignments and map them to monday.com Workspace member roles. Personal Spaces with private projects map to a dedicated monday.com Workspace designated for individual use.

Wrike Folders sit inside Spaces and contain Projects. We map Folders to monday.com Boards, preserving the Folder title as the Board name. Folder-level permissions in Wrike do not have a direct monday.com equivalent — we document the original permission matrix and recommend setting Board-level access controls post-migration.

Wrike Projects sit inside Folders and contain Tasks. We map Projects to Groups within the destination monday.com Board. If the customer's Wrike workspace uses Folders containing a single Project (a common pattern), we flatten this to a single Board with the Project as the primary Group to avoid unnecessary board proliferation in monday.com.

Wrike Tasks are the primary work unit and map directly to monday.com Items. We preserve assignees (mapped to monday.com Board members), due dates, start dates, priority, status, and all custom field values. The task title becomes the Item name. Created and modified timestamps migrate as-is to preserve the activity record.

Wrike Subtasks inherit parent context and can have independent assignees and dates. monday.com supports subitems on Pro+ plans. For Standard plan migrations, we map Subtasks to Items in a linked sub-board with a reference column pointing back to the parent Item, preserving the hierarchy structurally even without native subitem support. We flag which plan the destination uses during scoping.

Wrike's 14+ custom field types map to monday.com column types: DropDown maps to Labels, Numeric maps to Numbers, Date maps to Date, Currency maps to Numbers with formatting, Percentage maps to Numbers with % formatting, Contacts maps to Person or Connect boards, Checkbox maps to Checkbox, Calculated maps to Numbers (static value only — see Gotchas). We flag CalculatedNumeric and CalculatedDate fields explicitly and store the last computed value as a static number or date column since monday.com does not recompute formula results post-import.

Wrike Workflows define Status sets and custom transition rules per project or globally. We export every Workflow definition including all custom status values and transition logic. monday.com's status column does not natively support transition rule enforcement — the Workflow's conditional transition rules do not migrate as code. We deliver a written Workflow inventory with each rule mapped to a recommended monday.com automation trigger for the customer's admin to rebuild.

Wrike User accounts (name, email, role) export via API and map to monday.com Team Members by email match. We preserve the assignee-to-task mapping so the correct people are assigned post-migration. Deactivated Wrike users may need manual handling depending on whether their assignments should remain on records in monday.com.

Wrike Time Entries log hours, dates, and billing categories against tasks. We export time entries in full and map them to monday.com's Time Tracking column (Standard+). Duration-based entries convert to HH:MM format; billing category information stores in a separate Text column since monday.com's native time tracking does not include a billing category field.

Wrike file attachments are referenced by URL. We preserve download URLs and re-link them in monday.com file columns. Large attachment volumes may require a storage audit first — see the Gotchas section on the 2GB Free-tier cap. For accounts exceeding the cap, we prioritize task and custom field data migration and note which attachment sets will require a separate storage migration step.

Wrike supports Finish-to-Start, Start-to-Start, Finish-to-Finish, and Start-to-Finish dependency types between tasks. monday.com's Dependency column (Work Management Standard+ add-on) supports predecessor-successor linking. We map Wrike dependency chains to monday.com Dependency column entries and flag accounts without the Dependency add-on so the customer can add it before migration or accept a simplified flat structure.

Comments on Wrike tasks and projects include author, timestamp, and text content. We export comments in full and map them to monday.com Updates on Items. Thread structure (parent-child replies) preserves as nested Updates where monday.com's interface supports it. Author attribution migrates by email match to the monday.com Team Member.

Wrike Dashboards aggregate widgets showing project health, workload, and custom metrics. We export dashboard configurations and widget definitions where the API exposes them. monday.com Dashboards use a different widget model; direct widget-to-widget migration is not feasible. We deliver a written dashboard inventory describing each Wrike dashboard's purpose, widgets, and filters so the customer's admin can rebuild equivalents in monday.com's dashboard builder.

Wrike Tags are freeform labels applied to tasks and projects. We export tag values as-is. monday.com offers both Labels (multi-select color-coded tags) and Tags columns. We recommend Labels as the primary target since it matches Wrike's visual tagging behavior most closely. The customer chooses during scoping.