Migrate from LiquidPlanner to Microsoft Project

LiquidPlanner Workspaces contain all Projects, Members, and Settings for an organization. Microsoft Project has no Workspace equivalent; projects are individual .mpp files or Project Online entries. We map Workspace-level custom field definitions and member lists to the destination environment and note that Workspace-level settings (billing rates, default views) do not migrate. If the customer uses Microsoft 365, we recommend a SharePoint document library or Teams channel as the organizational container for migrated .mpp files.

LiquidPlanner Projects map directly to Microsoft Project plans. Project name, description, baseline dates, priority, and status migrate 1:1. Project-level custom field values transfer to Microsoft Project custom fields (if the plan supports them; Project Plan 1 has limited custom field support). Project status indicators are noted in the migration map for the customer's PM to set appropriately in the destination.

LiquidPlanner Packages are grouping containers within a Project, similar to a high-level phase or initiative. Microsoft Project has no native Package object, so we transform Packages into summary tasks with the same name, and the Package's custom field values become custom fields on the summary task. The customer's PM should verify the grouping hierarchy after migration because some Package structures may benefit from being collapsed into the project level rather than preserved as nested containers.

LiquidPlanner Tasks map to Microsoft Project tasks with the following transformations: range estimates (lower bound as Start, upper bound as End), single assignee from the primary owner (additional owners become notes or separate assignment rows), wait days converted to predecessor lag time, and custom field values mapped to typed Microsoft Project custom fields. Tasks with multiple assignees are split into individual task rows in Microsoft Project with effort ratio preserved as a note.

LiquidPlanner Sub-Tasks map to Microsoft Project subtasks by outline level. If the destination plan has a limit on outline nesting, we flatten deeper Sub-Task hierarchies into linked tasks and flag them for the customer's PM to reorganize. Sub-Task custom field values migrate as custom fields on the child task.

LiquidPlanner finish-to-start dependencies map to Microsoft Project finish-to-start predecessors directly. Start-to-start dependencies map to start-to-start predecessors. Wait days in LiquidPlanner (a delay after a predecessor completes) map to Microsoft Project lag time on the predecessor link. Complex multi-step dependency chains are mapped as-is but flagged individually because LiquidPlanner's auto-rescheduling behavior across long chains will not replicate in Microsoft Project.

LiquidPlanner Milestones map directly to Microsoft Project milestones. We preserve milestone name and target date. Milestones that drive downstream dependencies in LiquidPlanner's scheduling engine are flagged for the customer's PM to verify the resulting milestone date in the fixed-date model because the downstream rescheduling behavior will not occur automatically.

LiquidPlanner Workspace-level and Project-level custom fields migrate as values attached to the corresponding Project or Task in Microsoft Project. Custom field definitions (names, types, options) must be recreated in Microsoft Project's custom field editor before migration. We provide a custom field mapping table during discovery. Note that Project Plan 1 has limited custom field support; Plan 3 or Plan 5 is required for extensive custom field usage.

LiquidPlanner time tracking data (hours logged, billable vs non-billable, billing rates) maps to Microsoft Project task assignment actual work. We extract the effort logged per Member per Task and create assignment rows with the logged hours as Actual Work. Billable/non-billable flags become assignment-level notes because Microsoft Project does not have a native billable flag on assignment rows. Approval status is noted but not enforced in the destination because Microsoft Project lacks a built-in timesheet approval workflow.

LiquidPlanner Members map to Microsoft Project resources. We preserve name, email, and billing rate as the resource Standard Rate. Members are created in the destination Resource Sheet before any task assignments are loaded so that the resource reference is satisfied at import time. Virtual Members (external stakeholders without full licenses) are imported as resources with a display name prefix indicating they are external.

File attachments on LiquidPlanner Tasks and Projects do not migrate as embedded files in Microsoft Project. We export attachments to a shared cloud location (OneDrive, SharePoint, or a designated network path) and create hyperlinks on the corresponding tasks pointing to the attachment location. This preserves access to the files without embedding them in the .mpp file or Project Online environment.

LiquidPlanner Portfolio Manager dashboards aggregate multiple projects with cross-project resource utilization, portfolio health, and cost summaries. Microsoft Project has no native multi-project portfolio view in the desktop product. We migrate the underlying Projects individually and deliver a written inventory of every Portfolio View configuration for the customer's PM to rebuild using Microsoft Power BI or Project Online's portfolio dashboards if they upgrade. Portfolio-level aggregations cannot be migrated as data because they are computed views, not records.