Migrate from Wrike to Microsoft Project

Wrike Projects map directly to Microsoft Project files or Project Online projects. Each Wrike Project becomes a separate MS Project file (.mpp) on desktop or a separate project in Project Online. Project metadata (name, description, start date, finish date, status) migrates 1:1. Wrike project-level custom fields map to MS Project Project Summary Task custom fields on Project Online. The project owner becomes the Project Summary Task assigned resource.

Wrike Tasks map to MS Project Tasks with Name, Start, Finish, Duration, and Work preserved. Wrike's status (Active, Completed, On Hold, Cancelled) maps to MS Project's percent complete and Task Summary Name. Wrike assignees become MS Project resource assignments on the Task row. Subtask nesting is preserved through MS Project's outline level and indent/outdent structure.

Wrike Subtasks are MS Project Tasks with an indent level one greater than their parent task, making the parent a Summary Task. Summary Tasks display the rolled-up duration and work of their subtasks automatically. We preserve the Wrike subtask's independent assignee and dates as a normal task row with the parent-summary relationship maintained via outline structure.

Wrike Folders above Projects have no direct MS Project equivalent because MS Project has no two-level container above Project. We resolve this by converting Folder-level groupings into a Summary Task at the top of each Project file, or by creating a master project in Project Online with subproject references. The customer's PMO chooses the grouping strategy during scoping based on whether they use Project Online (supports subprojects) or desktop MS Project (supports master projects).

Wrike's 14-plus Custom Field types (DropDown, Numeric, Date, Currency, Percentage, Contacts, Checkbox, Calculated) have no native equivalent in desktop MS Project. On Project Online we create custom columns via the enterprise custom fields feature. On desktop MS Project we map text-based custom fields to Text fields and numeric fields to Number fields. CalculatedNumeric fields export as static Number values with a note flagging they are not live formulas. DropDown fields map to Text values or Lookup Table fields on Project Online.

Wrike assignees on Tasks and Subtasks map to MS Project Resources. We extract unique user emails from Wrike task assignments, create Resource records in MS Project (or in the enterprise resource pool for Project Online), and resolve the assignment by matching the resource name to the Wrike assignee. Deactivated Wrike users without an MS Project resource equivalent go to a reconciliation queue for the customer's admin to resolve before the final import pass.

Wrike dependency chains (Finish-to-Start, Start-to-Start, Finish-to-Finish, Start-to-Finish) map directly to MS Project predecessor-successor links using the dependency type as the link type. We export the dependency graph as a list of predecessor-successor task name pairs and resolve the task IDs at import time. For destinations without native dependency support we note the dependency pairs in the migration log for manual recreation.

Wrike time entries (hours logged against a task on a specific date with optional billing category) map to MS Project Assignment Actual Work on the resource assignment. The date of the time entry becomes a timephased Actual Work value. Billing category maps to a text Notes field on the assignment or to a custom field if Project Online enterprise custom fields are available.

Wrike task comments migrate as appended entries in the MS Project Task Notes field, formatted with author name and timestamp. If the Wrike task has multiple comments, we concatenate them in reverse chronological order. MS Project's Notes field does not support threaded conversations, so we flatten the thread into a single text block. The original comment author and timestamp are preserved inline.

Wrike file attachments are referenced by URL in Wrike. We export the attachment URLs and filenames, and re-link them in MS Project either as file references (desktop) or as SharePoint document library links (Project Online). Large attachment volumes may require separate storage migration; we flag accounts whose total attachment size exceeds 500MB for a separate bulk-transfer discussion.

Wrike Workflows define custom status sets and transition rules per project or globally. MS Project has no workflow automation engine; status values are static text or number fields. We map Wrike custom statuses to MS Project Task Status fields (not the built-in percent-complete status) and deliver a written status-mapping table. Active workflow transition rules are documented for rebuild in Power Automate if the customer uses Project Online.