Migrate from Flow to monday Work Management

Flow Tasks map directly to monday.com Items. The Task title maps to Item name, description becomes the Item description or a text column, due date maps to a Date column, and assignee resolves to the monday.com User reference. Subtasks under a Flow Task map to monday.com Subitems if the destination plan supports them, or to child Items linked via a parent Item column if Subitems are unavailable.

Flow Projects have no direct monday.com equivalent because monday.com organizes work as Boards containing Items rather than standalone Project records. We map each Flow Project to a monday.com Board, or to a Group within an existing Board if the customer prefers consolidated Boards. Lists within a Flow Project become Groups within the mapped Board. Custom project-level properties become columns on each migrated Item.

Flow Comments migrate to monday.com Updates attached to the corresponding Item. We preserve the comment body text, author name, and the timestamp returned by Flow (which may be date-only rather than full datetime). Updates are sequenced by timestamp. We flag in the validation report that chronological ordering of comments may be approximate due to Flow's date-only timestamp truncation.

Flow Members map to monday.com Users. We resolve by email address match. Any Flow Member without a matching monday.com User is placed in a reconciliation queue for the customer to provision before record import resumes. Member name and email are preserved; Flow profile metadata beyond these fields is not available for transfer.

Flow Due Dates on Tasks map to a monday.com Date column on the Board. The date value and any time-of-day context from Flow transfer as-is. We create the column with the name matching the Flow field label. If a Flow Task has no due date, the column is left blank on the corresponding Item.

Flow Custom Fields are key-value pairs with no documented type metadata. We infer the monday.com column type from the value content: text strings map to Text columns, numeric values to Number columns, ISO date strings to Date columns, and delimited lists to Tags or Dropdown columns. Field types are inferred at migration time; we flag uncertain mappings in the validation report for the customer to verify post-migration. If a field contains heterogeneous values, we map it to a Text column as the conservative fallback.

Flow Tags on Tasks map to the monday.com Tags column on the Board. Each tag name transfers as-is and attaches to the corresponding Item. Tags used for categorization in Flow become monday.com Tags; Tags used for cross-project classification map to a separate Tags column that the customer may rename during the post-migration review.

Flow Lists are groupings within a Project at the same hierarchy level as Tasks, with no parent-child relationship in Flow's flat model. We map each List to a monday.com Group within the Project's mapped Board, preserving the List name as the Group name and attaching all Tasks in that List to the Group. Alternatively, if the customer prefers a flat structure, Lists can map to a Tags column instead. The customer selects the strategy during scoping.

Flow Subtasks nest under parent Tasks. We map this hierarchy to monday.com Subitems if the destination account has Subitems enabled (Standard and above). Each Subitem inherits the parent Item's Board and Group. Subitem title, assignee, and due date transfer. If Subitems are not available on the destination plan, Subtasks become child Items linked via a parent Item column with a lookup relationship.

Flow provides no programmatic path for bulk attachment export. We produce a full manifest of Items that have attachments, with the file name and download URL for each. The customer downloads files individually via browser and re-uploads them to the corresponding monday.com Item post-migration. We do not automate the download step. This manual effort is documented in the migration plan with a step-by-step checklist.

If Flow contains time entry records associated with Tasks, we map them to monday.com's Time Tracking column on the Board. The time entry value and associated Task relationship transfer to the corresponding Item. This column is available on Pro and above. We confirm the destination plan includes Time Tracking before mapping and flag any plan tier gap in the scoping report.

Flow Saved Views represent saved filtering and sorting states in the UI with no persistent data that can be extracted. We document the Saved View names, column filters, and sort order from the Flow workspace as a written reference. The customer's admin recreates these as column filters, grouping, and view presets in monday.com using the Board's built-in filtering. We do not migrate Saved Views as a data object.