Migrate from ProjectFlow to monday Work Management

ProjectFlow Projects map to monday.com Boards. Each Project becomes a separate Board with the Project name as the Board name, start date and target date mapped to Board settings, and project status preserved as a Board-level Status column or mirror column. We extract the full project list during CSV parsing and create Boards in dependency order so that linked subprojects and milestone references resolve correctly.

ProjectFlow Tasks map directly to monday.com Items within a Board Group. Assignee, due date, priority, and status migrate to the corresponding monday.com column types (People, Date, Status). Task description migrates to the Item's Description column (rich text). We preserve the original Task ID in a custom column for audit trails and cross-reference during reconciliation.

ProjectFlow Subtasks map to monday.com Subitems nested one level below the parent Item. Subtask nesting depth in ProjectFlow varies by tier; we flag and flatten hierarchies that exceed monday.com's single subitem level by re-parenting records to the closest allowed parent. Each Subitem inherits the parent Item's Group and Board context.

ProjectFlow Milestones map either to a dedicated Milestones board or to Items with a Date column set to the milestone date and a Status column set to a milestone-specific label (such as Milestone Reached). We preserve the milestone name, target date, and any linked task references as an Items column or related Items links depending on the customer's preference.

ProjectFlow GanttChart structure including task bars, start and end dates, and dependency links maps to monday.com Timeline columns and Dependency columns. Dependencies that cannot be represented natively in monday.com (such as cross-board dependencies) are stored in a custom Dependency Notes column. We extract the dependency graph from ProjectFlow's CSV export and reconstruct it as linked Items or dependency references post-import.

ProjectFlow Documents map to monday.com file attachments. We extract document metadata (name, type, size, created date, author) from the Document object and store it as an Item column. If the documents are stored in a cloud path accessible via URL, we attach them as file links to the corresponding Item. monday.com does not have a native document management object; file attachments are the closest equivalent.

ProjectFlow DocumentFolders preserve a nested folder hierarchy that monday.com Groups do not natively replicate. We extract the full parent-child folder relationship and recreate it as monday.com Groups with naming conventions that reflect the hierarchy (for example, FolderName/SubfolderName as a Group name). Customers who require a true folder hierarchy use monday.com's Google Drive or SharePoint integration to link external document repositories.

ProjectFlow DailyReports (construction-industry daily site reports) have no direct monday.com equivalent. We map DailyReport date, author, and narrative content to an Item Comment with a formatted block containing the report date, site reference, and narrative. We flag any loss of structured site-specific fields such as weather conditions, labour counts, or equipment usage as a documented gap in the migration report.

ProjectFlow Alert thresholds and notification rules are platform-native and cannot be exported in structured format. We extract alert configuration details (alert name, trigger condition, notification recipients) as a written inventory and map each to a corresponding monday.com Automation rule using the Automate centre's When-Then builder. Customers rebuild these manually post-migration using the inventory as a configuration guide.

ProjectFlow ProjectShares control which users have access to a project. We extract the sharing configuration and map it to monday.com Board sharing settings (Workspace visibility, Team-based access, or individual email invites). ProjectShares that reference external parties without monday.com accounts are flagged for manual handling.

ProjectFlow Assignees map to monday.com People column values on Items. For Enterprise-tier multicompany ProjectFlow instances, we deduplicate cross-company user records by email address before mapping, ensuring a single monday.com user account is referenced per unique person. Owners map to Board admins; assignees map to People column entries.

ProjectFlow Custom Fields on Projects and Tasks vary by tier and configuration. We enumerate all custom fields during discovery, classify them by type (text, number, date, dropdown, checkbox), and map them to monday.com custom column types. monday.com's supported column types include Text, Numbers, Date, Status, Dropdown, Checkbox, Timeline, Dependency, Location, and Formula; any ProjectFlow custom field type without a direct monday.com equivalent is mapped to a Text column with a note in the migration report.