Migrate from Flow to Microsoft Project

Flow Projects map directly to Microsoft Project Projects. We extract the project name, description, and creation date. Flow's project-level custom fields map to Text fields on the Microsoft Project Summary task or as custom columns in the project plan. The destination .mpp file or Project Online project is created before any Task import so that the project association is established for all child records.

Flow Tasks map to Microsoft Project Tasks. The Task Name, Description (as Notes field), Due Date, and Created Date migrate. Flow's Due Date maps to Microsoft Project's Finish field; Flow's task creation date maps to Start. We flag that Flow has no Start Date field, so migrated tasks default to the Due Date minus estimated duration or to today if no duration context exists. Task Status from Flow maps to Microsoft Project's % Complete or Status field.

Flow's Subtasks under a parent Task map to Microsoft Project's hierarchical subordinate tasks with outline levels and Summary task grouping. We preserve the parent-child relationship by setting the Outline Level and creating a Summary task in Microsoft Project for each Flow parent Task. The indent/outdent structure is reconstructed from Flow's subtask nesting depth.

Flow Members assigned to Tasks map to Microsoft Project Resources. We extract the Member name and email from Flow's workspace access, create a Resource record in Microsoft Project for each unique Assignee, and generate Assignment records linking the Resource to each migrated Task. If a Flow Assignee has no corresponding person in the destination, we flag them in the reconciliation report for the customer to map or provision manually.

Flow Due Dates on Tasks map to Microsoft Project Task Finish fields. We preserve the calendar date and any timezone context from Flow. We note that Flow does not store a Start Date, so we either set Start = Finish minus a default one-day duration or leave Start as Not Started, depending on the customer's preference documented during scoping.

Flow Comments on Tasks map to Microsoft Project Task Notes as text blocks prefixed with the author name and timestamp. We flag that Flow's UI may truncate timestamps to a date rather than an exact datetime, so chronological ordering of comments may be approximate. Attachments referenced in comments are not migrated by this step; see Attachment notes for the manual download process.

Flow Tags on Tasks map to a Microsoft Project Text field named Tags. We store tags as comma-separated values in the Text field or as individual flag columns if the customer requests a multi-column tag structure during scoping. Tags are not native Microsoft Project constructs; we recommend the customer rebuild tag-based filtering using Microsoft Project's native Group and Filter features in the destination.

Flow Lists group Tasks within a Project. We map Lists to Microsoft Project's Phase or Summary task grouping by creating a Summary task for each List and nesting the List's Tasks underneath. The Outline Level reflects the List hierarchy. If Flow Lists have no specific order, we use alphabetical or creation-date ordering in Microsoft Project.

Flow Custom Fields on Tasks map to Microsoft Project custom fields. We infer the field type from the value (text, number, date) and create matching Text1-30, Number1-30, or Date1-30 fields on the Task. We preserve the field label from Flow as a custom field name or as a note in the migration report if the destination does not support custom labels.

Flow Attachments cannot be extracted programmatically due to no API. We document every Task with an Attachment, including the file name, file type, and the URL path visible in Flow's UI. The customer downloads each file manually via browser and we map them to the migrated Task by name. We provide a checklist of all attachment-bearing tasks and a step-by-step guide for manual download before the migration window closes.

If Flow contains time tracking entries (hours logged against Tasks), we map them to Microsoft Project Assignment fields. We extract the hours value, the date, and the person who logged the time, and create a Task with Assignment records showing the Work hours. Microsoft Project's Assignment view displays total work per Resource per Task.