Migrate from Flowzone to Microsoft Project

Flowzone Jobs map to Microsoft Project Projects, with the Job title becoming the Project name, description becoming the Project summary, and the Job's current status preserved as a Project-level custom field. Tasks within the Project correspond to sub-items or checklist items on the Job, or to workflow steps if the migration scope includes step-state encoding. Parent-project and sub-project structures in Flowzone List hierarchies map to summary tasks and indent hierarchy in Project.

Flowzone Lists group related Jobs and serve as the top-level organisational view. We map each List to a Project in Microsoft Project, or to a summary-task grouping if the destination is a single Project file. List-level custom columns become Project-level custom fields. If the customer maintains a flat Job list with no List grouping, we create a single Project with all Jobs as tasks.

Flowzone custom columns (text, numeric, date, dropdown, checkbox) map to Microsoft Project custom fields. We use the Text1-Text30 fields for string data, Number1-Number20 for numeric data, Date1-Date10 for date data, and Flag1-Flag20 for boolean data per the standard Project field schema. Custom field names and data types are aligned during the field-mapping phase before import. Lookup columns require mapping to a picklist or enterprise custom field with lookup table.

Flowzone documents attached to Jobs export as binary files with filename, version, and approval status. We restore them to the destination Project's associated SharePoint document library or attach them directly to the Project file. Approval status maps to a document-level custom field or a SharePoint list column in the destination. Annotation threads are UI-stored data that do not export in portable format; we flag annotated documents during the export audit and restore the approval status as a document property, with a note that annotation history requires manual reference.

Flowzone workflows are step-based with branching, looping, and step-jumping logic. Microsoft Project does not have a native workflow engine in the standalone desktop product. We export the workflow definition and the current step of each Job, then encode the current step as a custom Project or Task field (dropdown or text) and deliver a written workflow inventory documenting each step, its branching conditions, and its recommended Stage or custom field encoding in the destination. The customer's admin implements the workflow representation post-migration.

Flowzone Activities (available on Pro plan) are time-planned events linked to Jobs, with date, assignee, and description. We export activity details and map them to Microsoft Project Tasks with scheduled start and finish dates. If the destination is Project Online, Activities may also map to calendar entries in the associated SharePoint calendar or Outlook calendar linked to the Project site.

Flowzone time records capture hours logged against a Job with date, assignee, and notes. We export the amount, date, and assignee and map to Microsoft Project Assignment resources with the Hours field populated from the time-record value. Budget-to-actual comparison from Flowzone Pro maps to Earned Value custom fields in Project. We flag any time records that span multiple Jobs for disaggregation into task-level assignments. Time records without a corresponding Task require a placeholder task to be created in the destination.

Flowzone user accounts map to Microsoft Project Resources. We export the user list and map email addresses to Resource names. Material resources and cost resources from Flowzone map to Microsoft Project material and cost resource types respectively. Resource Calendar defaults to the destination Project calendar unless the Flowzone user has a defined working pattern we can encode.

Flowzone role-based permissions and group-based access control map to Microsoft 365 Groups and SharePoint permission levels on the Project site. External client portal sharing in Flowzone maps to SharePoint external sharing settings and Azure AD B2B guest access. We deliver a written permission matrix documenting the original Flowzone group hierarchy and its recommended Microsoft 365 equivalent, including any role-based Project Online security group mappings. The customer's tenant admin implements the permission configuration post-migration.

Flowzone Forms capture structured input against Jobs. We export the form schema (field names, types, options) and any submitted responses linked to Jobs. Form field mappings to Job columns require manual routing in the destination: form fields may become SharePoint List columns on the Project site or custom Task fields depending on the destination architecture. We document the form-to-field mapping as part of the migration inventory for the customer's admin to implement.

Flowzone custom dashboard panels (bar charts, pie charts) are UI-level visualisations tied to the platform's visualisation engine. They do not carry underlying data separately from the Jobs, Columns, and Forms they summarise. We do not migrate dashboard panel definitions. The underlying data migrates through the Job, Column, and Time Record mappings above, so the customer's admin can rebuild the visualisations in Microsoft Project Online views, Power BI, or the Project Dashboard. We flag this in the migration inventory.