Migrate your Wrike data

Wrike Projects sit at the top of the folder hierarchy and contain Tasks, Subtasks, and metadata. We map Projects 1:1 using their title, dates, status, and custom field values. Folder parentage is preserved so nesting relationships are intact in the destination.

Tasks are the primary work unit in Wrike with assignees, dates, durations, and dependencies. We export tasks with their full attribute set including custom fields, responsible users, and linked dependencies. Subtask relationships are preserved via parent task IDs.

Subtasks in Wrike inherit the parent's context and can have independent assignees and dates. We preserve the parent-child hierarchy explicitly in the destination schema so nesting depth is maintained.

Wrike supports 14+ Custom Field types including DropDown, Numeric, Date, Currency, Percentage, Contacts, Checkbox, and Calculated fields. We map these field types to equivalent destination fields but flag Calculated fields which cannot be migrated as editable values—only their last computed value transfers.

Wrike Workflows define Status sets and transitions per project or globally. We export Workflow definitions including all custom statuses and transition rules. The destination must support custom status sets, or we map each Wrike status to the closest available destination status.

User accounts with name, email, and role are exported via the API. We preserve the assignee-to-task mapping so the right people are assigned post-migration. Note: deactivated users may need manual cleanup in the destination.

Spaces are top-level organizational containers (shared or personal). Wrike's permission model is tied to Space membership. We map Space assignments but recommend reviewing access controls in the destination, as permission inheritance may differ.

Dashboards aggregate widgets showing project health, workload, and custom metrics. We export dashboard configurations and widget definitions where the API exposes them. Not all widget types map directly; we flag those requiring manual rebuild.

Wrike logs time against tasks with hours, dates, and billing categories. We export time entries in full and map them to equivalent billing or timesheet objects in the destination. Duration-based entries are converted to explicit start/end timestamps.

File attachments are referenced by URL in Wrike. We preserve download URLs and re-link them in the destination. Large attachment volumes may require separate storage migration; we flag accounts exceeding 5GB of attachment data for pre-migration storage planning.

Wrike supports Finish-to-Start, Start-to-Start, and other dependency types between tasks. We map these 1:1 where the destination supports dependency tracking. For destinations without native dependency support, we add dependency as a custom linked-field.

Comments on tasks and projects include author, timestamp, and text content. We export comments in full. Thread structure is preserved as parent-child relationships where supported by the destination schema.

Views are Wrike display configurations. We export the view layouts and filter settings. Since most destinations use their own native views, we note the original view configuration in the migration log for manual recreation.

Tags in Wrike are freeform labels applied to tasks and projects. We export tag values as-is. The destination must support tag-based filtering, or we convert tags to a custom multi-select field.