Migrate from LiquidPlanner to monday Work Management

LiquidPlanner Workspaces map to monday.com Workspaces at the account level. Workspace-level custom field definitions must be recreated in monday.com as custom columns on the relevant boards; they do not carry over as schema. Member lists from the Workspace migrate to monday.com Users, with Virtual Members flagged for admin decision (import as user or contact). Workspace-level settings (notifications, billing rates) do not have a direct monday.com equivalent.

LiquidPlanner Projects map directly to monday.com Boards. We preserve the project name, baseline dates, status, and description. Project-level custom fields map as custom columns on the destination Board. The Project's priority ranking across the portfolio does not translate to a native monday.com field — we use the Priority column or a numeric ranking column as the equivalent. Multi-project dependency chains that span Boards require monday.com's Cross-Board Dependencies feature (Pro plan and above) or a workaround via the Lookup column.

LiquidPlanner Packages are phase-level grouping containers within a Project, similar to monday.com Groups within a Board. We map them 1:1 and preserve the Package name, description, and any custom field values. If a Package contains Sub-Packages, we flatten those into Groups within the same Board. Package-level ordering (phase sequence) migrates as Group position order.

LiquidPlanner Tasks map to monday.com Items. We migrate task name, description, assignee (single or split), start date (lower bound of range estimate), end date (upper bound of range estimate), priority, wait days, and custom field values. Tasks with range estimates are flagged in the pre-migration field-mapping document because monday.com uses fixed dates; the customer's PM verifies each flagged task's resulting timeline. Long-chain dependency tasks receive individual flags because LiquidPlanner's auto-rescheduling will not replicate in monday.com.

LiquidPlanner Sub-Tasks migrate as monday.com Sub-items on Boards with Sub-items enabled (Pro plan and above). On Standard plan, Sub-Tasks flatten into the parent Item as checklist items. The Sub-Task name, assignee, and dates migrate. Sub-Task custom fields map as Sub-item columns on Pro+ or are appended to the checklist item note on Standard.

LiquidPlanner finish-to-start, start-to-start, and wait-day dependencies map to monday.com's Dependency column (Pro+). Cross-Board dependencies require monday.com's Cross-Board Dependency feature or a Lookup column workaround. Multi-step chains are resolved iteratively; circular dependencies are flagged for the customer's PM to resolve before migration. Wait days from LiquidPlanner are converted to adjusted target dates in monday.com because wait days have no native equivalent.

LiquidPlanner Workspace and Project custom fields map to monday.com custom columns by type: text fields map to Text columns, numeric fields to Numbers columns, date fields to Date columns, dropdown fields to Dropdown columns, and checkbox fields to Checkbox columns. Custom field definitions (names, types, options) must be recreated in monday.com before migration; we provide the column configuration specification as part of the pre-migration field-mapping document.

LiquidPlanner time entries — hours logged, billable vs. non-billable flags, billing rates, and individual timer entries — migrate to monday.com's native Time Tracking column on Boards with the feature enabled (Pro plan and above). Timesheet summaries migrate as a note on the relevant Item or as a separate reporting board built in monday.com. Approval workflow status from LiquidPlanner does not carry over; the customer's admin sets up a new approval workflow if required. Monday.com Standard has no Time Tracking column, so teams on that plan need the Pro plan or a third-party time tracking integration.

LiquidPlanner Member records (email, name, role, billing rate) map to monday.com User accounts. We resolve by email match during import. Members without an email or that are inactive in LiquidPlanner are held in a reconciliation queue. Role and billing rate from LiquidPlanner migrate as custom columns on the User profile board or as a separate resource board for the customer's PM to reference.

LiquidPlanner Virtual Members are external stakeholders without full licenses. We flag all Virtual Members during scoping and give the customer's admin two options: import as a monday.com User (with an explicit display-name note indicating Virtual Member status) or import as a Contact in the customer's connected CRM integration. Virtual Members cannot hold tasks in monday.com without a User seat, so this decision affects the billable user count.

LiquidPlanner file attachments on Tasks and Projects migrate as references. If the customer has a Google Drive, Dropbox, or Box integration configured in monday.com, we import file URLs as Drive Link columns pointing to the existing document. Standalone file attachments without a cloud storage home are exported to a flat folder structure and linked as URL columns; the customer's admin relocates them to a supported storage system post-migration.

LiquidPlanner Milestones (zero-duration tasks with a target date) migrate to monday.com Items with a milestone flag or a dedicated Milestones column. Milestone name and target date transfer. Milestones that drive downstream dependencies via LiquidPlanner's scheduling engine are flagged individually because monday.com does not auto-propagate milestone changes through dependent chains.