Migrate from monday Work Management to Microsoft Project

Each monday Board maps to a Microsoft Project file (.mpp or cloud Project plan). Board name becomes the Project Name; board-level settings like default view do not transfer. We create the Project in the destination account and set the Project Start Date from the earliest non-null Timeline or Date column value on any Item in the board.

monday Items map to Microsoft Project Tasks. The Item name becomes the Task Name. Start Date reconstructs from the monday Timeline column Start or the Date column value; Finish Date from the Timeline End or a separate Date column. We handle the common case where teams use a single Date column instead of a Timeline range by treating that date as both Start and Finish. Items without date data become Tasks with a start date set to the Project Start Date.

monday Groups are horizontal row containers within a Board representing status or phase buckets. We create Project-level Summary Tasks for each Group name and nest Items within the corresponding Summary Task to preserve the grouping structure. If the destination uses a flat task list, we add a custom Text1 field carrying the Group name.

monday Status columns carry named labels (To Do, In Progress, Done) with optional color. We map Status labels to Project Task Status values (Not Started, In Progress, Completed). If the customer uses %-complete tracking, we compute percent complete from the Status-to-percent mapping defined during scoping (e.g., Done = 100, In Progress = 50) and write it to the Task's PercentComplete field.

The monday Timeline column provides a start and end date range per Item. We extract start_date and end_date from the Timeline column response and write them to the corresponding Task's Start and Finish fields in Project. If the board uses separate Start Date and End Date columns instead, we apply the same mapping. Items with no date column value default to the Project Start Date.

monday Assignees are User records on an Item. We resolve each assignee's email against the monday User list and map to a corresponding Microsoft Project Resource (created in the Resource Sheet before task import). We create Resource Assignments on the Task using the resolved Resource ID. If a monday User has no matching Project Resource, they are added to a reconciliation queue.

monday Subitems nested under a parent Item map to Project Subtasks under the parent Task. This is the highest-effort object in the migration because monday provides no bulk Subitem endpoint. We first query all Item IDs on the board, then make a secondary API call per Item to fetch its Subitems, and finally create the parent-child relationship in Project using the Outline Level and Summary task flag. Subitems under archived Items are optionally included based on the customer's scope decision.

monday Dependency column links Items as predecessor-successor pairs. We extract the linked Item IDs from the dependency column and resolve them to the corresponding Task UIDs in the destination Project. Cross-board dependencies are flattened: if Item A on Board 1 depends on Item B on Board 2, we bring both Items into the same Project during migration and create a Finish-to-Start dependency link. The monday dependency link type (Finish-to-Start, Start-to-Start) is inspected; unknown link types default to Finish-to-Start.

monday Time Tracking column entries carry duration (in minutes), description, and assignee. We map the total logged time per Item to the Task's Actual Duration and individual entries to Task Logged Hours rows per resource. Start and Finish dates of the time entry do not map to Project scheduling dates; they only populate the logged hours data.

monday Updates are threaded comments on Items. Each Update carries body text, author, and timestamp. We append Update text to the Task's Notes field in chronological order, prefixed with the author name and timestamp. Long comment threads are summarized if the Notes field length exceeds Project's practical limit. This preserves the commentary history in a read-only Notes attachment.

monday file attachments store name, URL, and uploader metadata. We preserve the file URLs as plain-text references in the Task's Notes field. Actual binary file migration (download from monday CDN and re-upload to SharePoint or OneDrive) is outside standard scope; we flag each file reference for the customer's admin to relocate manually or via a separate file migration step.

monday Tags are free-text labels applied to Items with optional color. We map Tags to a custom Text field in Project (Task Text1) holding a semicolon-delimited list of Tag names. If the destination Microsoft Project plan is connected to Microsoft Planner or a SharePoint task list, Tags may alternatively map to Planner's Tags or a SharePoint choice column.