Migrate from ProjectFlow to Microsoft Project

ProjectFlow Projects map 1:1 to Microsoft Project files or Project Online project plans. The project name, description, start date, target finish date, status, and priority migrate directly. We preserve the project-level metadata (customer, project manager, contract type) as task notes or custom fields in Microsoft Project because Project Online has no native project-level custom field object at the file level. Project-level Documents and DocumentFolders are linked via URL fields or recreated in SharePoint Online per the customer's document management preference.

ProjectFlow Tasks map 1:1 to Microsoft Project Tasks with Name, Start, Finish, Duration, Priority, and Status preserved. The Task's start_date and due_date map to Microsoft Project Start and Finish fields; estimated hours map to the Duration field (converted to duration units). Custom task fields from ProjectFlow are enumerated during discovery and mapped to Microsoft Project custom fields (Text1-30, Number1-10, Cost1-10, Flag1-20) via the Field List customisation dialog.

ProjectFlow subtasks map to Microsoft Project's summary-task and sub-task hierarchy. Microsoft Project supports hierarchical task structures with summary tasks (parent rows) and sub-tasks (child rows) up to a practical WBS depth of 8-10 levels. We flag during scoping if the subtask hierarchy exceeds this depth and either flatten the excess levels or re-parent the deepest records under a newly created summary task. The indentation structure is preserved as Outline Level in Microsoft Project.

ProjectFlow Milestones map to Microsoft Project Milestone tasks — tasks with Duration = 0 and Milestone = Yes. The milestone name, target date, and any linked tasks migrate directly. We verify that milestone dates are correctly set as Finish dates on zero-duration tasks because Microsoft Project derives milestone status from the Finish date and duration value, not from a separate milestone flag field.

ProjectFlow Gantt structure — task bars, start/end dates, and dependencies — is extracted and reconstructed in Microsoft Project using the FS (Finish-to-Start) dependency type as the default. Cross-dependency links from ProjectFlow that do not map to a standard Microsoft Project predecessor type (SS, FS, FF, SF) are stored as task Notes with the original dependency type noted, or linked via a custom Flag field. Lag time and lead time from ProjectFlow migrate as Successor fields with positive or negative day offsets.

ProjectFlow Documents are linked to projects and optionally nested inside DocumentFolders. We export document metadata (file name, URL path, linked project, linked task, author, created date) and recreate document references in Microsoft Project using a URL custom field on the relevant task or as a SharePoint document library linked to the Project Online site. Actual file transfer uses the customer's preferred storage path (SharePoint Online, OneDrive for Business, or local file share). Document versioning is not preserved; we transfer the current version only.

ProjectFlow DocumentFolders with their parent-child hierarchy are preserved as a flat list of folder paths and recreated as a SharePoint Online document library structure within the associated Project Online site. If the destination is Microsoft Project Desktop without SharePoint, the folder hierarchy is documented as a path list in the project Notes and provided as a CSV for manual folder creation.

ProjectFlow DailyReports (construction-industry-specific with site-level progress, weather conditions, and labour counts) have no direct Microsoft Project equivalent. We map DailyReports to a combination of task Notes on the relevant project or summary task and a CSV export of the original DailyReport data for the customer's records. We flag any loss of structured site-specific fields (weather, labour counts, equipment on site) during scoping and allow the customer to choose whether to include these as formatted note text or exclude them entirely.

ProjectFlow alert thresholds and notification rules are platform-specific and do not have a native Microsoft Project equivalent. We extract alert configurations as a structured CSV during discovery and provide a written alert inventory that maps each ProjectFlow alert to a corresponding Microsoft Project Reminder (flag icon, reminder time) or to a SharePoint workflow for email notification. The customer configures these manually in the destination.

ProjectFlow assignees on Tasks and Projects map to Microsoft Project resource assignments on tasks. We resolve ProjectFlow users by email match to Microsoft Project resources. Enterprise multicompany structures in ProjectFlow may result in the same person appearing as separate assignees under different company contexts; we deduplicate these to a single resource record in Microsoft Project during the mapping phase and flag any history attribution ambiguity. If a ProjectFlow assignee has no corresponding resource in Microsoft Project, they are held in a reconciliation queue for the customer's admin to provision before record import.

ProjectFlow ProjectShares control which users or external parties have access to a project. We map these to Microsoft Project Online's sharing model (Project Online site permissions via SharePoint Online groups) or to Microsoft Project Desktop file-level sharing if the destination is the desktop application. Role definitions differ between platforms; we document the original ProjectShares as a permissions matrix CSV and note where the destination's permission model diverges from the source.

ProjectFlow custom fields on Projects and Tasks vary by tier. We enumerate all active custom fields during discovery (field name, data type, values, linked object) and map them to equivalent Microsoft Project custom fields via the Task Information or Project Information Field List dialog. Field types map as follows: text to Text custom fields, numbers to Number fields, dates to Date fields, currency to Cost fields, and multi-select options to Outline Code or Flag fields. Fields that have no Microsoft Project equivalent are flagged and either dropped or converted to Notes text.