Migrate from Fluid to monday Work Management

Fluid Programs are top-level containers holding related Projects. monday.com has no native Program object; we map Programs to monday.com Groups (inside a Workspace) and preserve the program-to-project parent relationship as a naming convention or Group description field. For organisations with more than 10 programs, we recommend using separate monday.com Workspaces per program to avoid Group clutter. The program name migrates as the Group name; the program description migrates as the Group description.

Fluid Projects map directly to monday.com Boards. The project name becomes the Board name, and the project status (active, on hold, completed) maps to a monday.com Status column on the Board. Project owner assignments become Board members in monday.com. Project-level custom fields from Fluid migrate as Board-level columns that apply to all Items. Start and end dates at the project level migrate as Board-level Date columns if the customer uses a portfolio-level view.

Fluid Tasks map to monday.com Items on the relevant Board. The task name becomes the Item title, status maps to the Status column, priority maps to a Priority or Labels column, and assignee maps to the Person column. Start date and end date migrate as the monday.com Timeline column (requires Pro tier) or as separate Start Date and Due Date columns (Standard tier). We flag the tier requirement during scoping if Timeline view is essential.

Fluid Subtasks map to monday.com Sub-items, which are a native feature from the Basic tier onward. We preserve the subtask name as the sub-item title, and all standard sub-item fields (assignee, due date, status) map directly. Parent-child relationships between Tasks and Subtasks are maintained in monday.com through the sub-item hierarchy, which is visible in the Board's structure view. Sub-items are included in Item count totals for licensing purposes.

Fluid Custom Fields map to monday.com Columns with type-aware conversion: text properties become Text columns, numeric values become Number columns, date values become Date columns, and picklist values become Dropdown columns. We read the Fluid field type during scoping and generate the corresponding monday.com column type before migration. Strict column validation (enforced as of monday.com API version 2025-04) means column types must be set correctly on creation; changing a column type post-migration requires column deletion and re-creation.

Fluid's hours-consumed and planned-effort data per task migrates as numeric columns on the monday.com Item. We map hours-consumed to a Number column named 'Hours Consumed' and planned effort to 'Planned Hours' (or equivalent customer-named columns). These are flat numeric fields; complex effort tracking that requires rollup formulas across sub-items maps to monday.com's Formula column type available on Pro+ tiers, and we flag this requirement during scoping.

Fluid stores task start and end dates that drive its Gantt visualisation. We extract these as date fields and map them to the monday.com Timeline column, which requires the Pro tier ($19/seat/month). The Timeline column presents the start and end date as a visual bar across a timeline view. We flag the Pro tier requirement explicitly during scoping and advise if the customer is on Standard tier that Timeline view is not available.

Fluid assigns tasks to named users. We extract the user identity and map it to monday.com's Person column, which links to monday.com workspace members. We resolve assignees by email match against the destination monday.com workspace members list. Assignees without a matching workspace member are held in a reconciliation queue for the customer's admin to provision before Item import resumes.

Fluid computes workload distribution charts at runtime by aggregating task assignments and effort metrics. These visualisations are not stored as discrete records with a documented export path. We do not migrate Workload Distribution data and document this gap explicitly in the migration scope before work begins. The underlying task assignments (assignee and hours per task) do migrate, and customers can rebuild workload views in monday.com's Workload view (Pro+ tier) from the migrated Item data.

Fluid's Flex Statistics mode stores scenario-modelling and what-if planning data in a proprietary analytical format with no documented export endpoint. This is a known limitation documented in the Fluid platform context. We do not migrate Flex Statistics data and include an explicit exclusion in the migration scope. Customers relying on scenario models should export the underlying input data (project timelines, effort estimates, resource assignments) manually before migration begins, as these inputs are preserved in the task and effort metric migration.

Fluid file attachments associated with tasks migrate as File column values in monday.com (available from Basic tier). Large attachment volumes or attachments stored in external file systems (Google Drive, SharePoint, Dropbox) may require a monday.com integration instead of direct file migration, and we advise on the appropriate approach during scoping based on attachment count and storage source.

Fluid does not include native meeting management features. The absence of meeting data means there is nothing to migrate on this object. Teams that relied on a separate meeting tool linked to Fluid tasks will need to re-establish that link in monday.com using its own integrations or the monday.com Meetings add-on. We note this gap during scoping so customers can plan the post-migration process adjustment.