Migrate your LiquidPlanner data
Predictive-scheduling project management platform with automatic resource leveling. Teams that align with its methodology get strong portfolio visibility; teams that resist it face a steep, frustrating climb.
In its favor
Why people choose LiquidPlanner
The signal that keeps LiquidPlanner on the shortlist. Sourced from G2, Capterra, and customer scoping calls.
Predictive scheduling engine automatically adjusts task dates when scope or availability changes, reducing manual re-planning overhead on complex, multi-resource projects.
Automatic resource leveling surfaces over-allocated team members before deadlines are missed, giving project managers a proactive workload-balancing view.
Integrated time tracking with timesheet approval workflows consolidates billing and project tracking into one tool rather than switching between systems.
Priority-based planning lets teams rank work across the entire portfolio so that when resources shift, the most important tasks are the first to reassign.
Consolidated project management under one SaaS roof replaces spreadsheets, Microsoft Project, and email threads, reducing training overhead across the organization.
Steep learning curve and opinionated methodology: teams that do not follow LiquidPlanner's scheduling logic spend months fighting the tool instead of using it.
Limited third-party integrations compared to modern PM platforms — many teams outgrow what is available and migrate to Jira, Asana, or Monday.com.
Customer service quality has declined since the Tempo acquisition, with multiple reviewers reporting slow or nonexistent support responses.
Predictive scheduling can produce confusing or unexpected date shifts when dependencies chain across many tasks, making it hard to communicate committed deadlines to clients.
LiquidPlanner Classic sunset on December 31, 2026 forces teams off a familiar platform, and Portfolio Manager itself sunsets December 31, 2027, creating uncertainty about long-term platform viability.
Reasons to switch
Why people leave LiquidPlanner
The recurring reasons buyers give for replacing LiquidPlanner. Presented as facts, not knocks.
Platform scorecard
Strengths, weaknesses, and where LiquidPlanner fits
Grades across six dimensions, plus a SWOT-style view of where the platform shines and where it falls short.
SWOT — strengths, weaknesses, and use-case fit
Strengths
Weaknesses
Where it works
Where it struggles
Pricing tiers
LiquidPlanner pricing overview
LiquidPlanner uses per-user, annual billing with three published tiers ranging from $15 to $42/user/month. A 14-day free trial is available. Enterprise pricing requires a sales conversation. The key migration-relevant constraint: Open API access is gated to the Ultimate plan, so organizations on Essentials or Professional must export data manually or upgrade before a programmatic migration can proceed.
Essentials
Tier 1 of 4
$15/user/month (billed annually)
What's included
Need help selecting your Project Management?
Book a free 30 minute consultationPricing is informational. FlitStack AI does not bill on LiquidPlanner's schedule — see our quote-based pricing →
What gets migrated
LiquidPlanner object support
Object-by-object support for LiquidPlanner migrations. Per-pair details surface during scoping.
Workspaces
Mapping requiredLiquidPlanner organizes data into Workspaces that contain all Projects, Members, and Settings for an organization. We map Workspace-level configurations and member lists, but Workspace-level custom fields and permission templates require manual re-application in the destination.
Projects
Fully supportedProjects are the top-level container in LiquidPlanner and translate 1:1 to most destination PM tools. We preserve the project hierarchy, baseline dates, and status. Project-level custom fields map as long as the destination supports custom fields on Projects.
Packages
Fully supportedPackages are grouping containers within a Project, similar to a high-level phase or initiative. We preserve the Package structure and any custom field values attached to them.
Tasks
Fully supportedTasks are the core work items in LiquidPlanner. We migrate task names, descriptions, dates, assignees, dependencies, wait days, and custom field values. Tasks with multiple assignees are exploded into individual assignments in platforms that do not support multi-owner tasks.
Sub-Tasks
Mapping requiredSome destination PM tools support only one level of nesting. We flatten Sub-Tasks into the parent task as checklist items or as linked child tasks, depending on the destination's capabilities, and flag which approach was taken.
Dependencies
Mapping requiredLiquidPlanner supports finish-to-start, start-to-start, and custom wait-day dependencies. We translate these into the destination's dependency model where supported. Complex multi-step dependency chains are verified manually post-migration because fixed-date systems do not auto-propagate schedule changes the way LiquidPlanner does.
Custom Fields
Mapping requiredLiquidPlanner supports custom fields at the Workspace and Project level. We migrate all custom field values attached to Projects and Tasks. Custom field definitions (names, types, options) must be re-created in the destination before migration; we generate a field-mapping spec during scoping.
Time Entries
Fully supportedTime tracking data — hours logged, billable vs. non-billable flags, billing rates, and approval status — migrates fully. Timesheet summaries and individual logged-time entries are treated as separate records where the destination distinguishes them.
Members and Virtual Members
Mapping requiredMember records include email, name, role, and billing rate. Virtual Members are placeholders for external clients or stakeholders without a full license. We import all Members as users; Virtual Members are imported as contacts or linked records depending on the destination's user model.
Documents and Attachments
Mapping requiredFile attachments on Tasks and Projects are migrated as linked references if the destination supports cloud storage integration (Google Drive, Dropbox, Box). Standalone file attachments are exported to a staging folder and re-uploaded manually or via integration post-migration.
Milestones
Fully supportedMilestones are special zero-duration tasks with a target date. We preserve milestone names and dates. Milestones that drive downstream dependencies via LiquidPlanner's scheduling engine are flagged for manual review in fixed-date systems.
Portfolios and Portfolio Views
Mapping requiredPortfolio-level aggregations of multiple projects — including portfolio health, resource utilization, and cost summaries — do not map directly to most destination tools. We migrate the underlying project data; portfolio rollup views must be rebuilt in the destination reporting layer.
| Object | Support | Notes |
|---|---|---|
| Workspaces | Mapping required | LiquidPlanner organizes data into Workspaces that contain all Projects, Members, and Settings for an organization. We map Workspace-level configurations and member lists, but Workspace-level custom fields and permission templates require manual re-application in the destination. |
| Projects | Fully supported | Projects are the top-level container in LiquidPlanner and translate 1:1 to most destination PM tools. We preserve the project hierarchy, baseline dates, and status. Project-level custom fields map as long as the destination supports custom fields on Projects. |
| Packages | Fully supported | Packages are grouping containers within a Project, similar to a high-level phase or initiative. We preserve the Package structure and any custom field values attached to them. |
| Tasks | Fully supported | Tasks are the core work items in LiquidPlanner. We migrate task names, descriptions, dates, assignees, dependencies, wait days, and custom field values. Tasks with multiple assignees are exploded into individual assignments in platforms that do not support multi-owner tasks. |
| Sub-Tasks | Mapping required | Some destination PM tools support only one level of nesting. We flatten Sub-Tasks into the parent task as checklist items or as linked child tasks, depending on the destination's capabilities, and flag which approach was taken. |
| Dependencies | Mapping required | LiquidPlanner supports finish-to-start, start-to-start, and custom wait-day dependencies. We translate these into the destination's dependency model where supported. Complex multi-step dependency chains are verified manually post-migration because fixed-date systems do not auto-propagate schedule changes the way LiquidPlanner does. |
| Custom Fields | Mapping required | LiquidPlanner supports custom fields at the Workspace and Project level. We migrate all custom field values attached to Projects and Tasks. Custom field definitions (names, types, options) must be re-created in the destination before migration; we generate a field-mapping spec during scoping. |
| Time Entries | Fully supported | Time tracking data — hours logged, billable vs. non-billable flags, billing rates, and approval status — migrates fully. Timesheet summaries and individual logged-time entries are treated as separate records where the destination distinguishes them. |
| Members and Virtual Members | Mapping required | Member records include email, name, role, and billing rate. Virtual Members are placeholders for external clients or stakeholders without a full license. We import all Members as users; Virtual Members are imported as contacts or linked records depending on the destination's user model. |
| Documents and Attachments | Mapping required | File attachments on Tasks and Projects are migrated as linked references if the destination supports cloud storage integration (Google Drive, Dropbox, Box). Standalone file attachments are exported to a staging folder and re-uploaded manually or via integration post-migration. |
| Milestones | Fully supported | Milestones are special zero-duration tasks with a target date. We preserve milestone names and dates. Milestones that drive downstream dependencies via LiquidPlanner's scheduling engine are flagged for manual review in fixed-date systems. |
| Portfolios and Portfolio Views | Mapping required | Portfolio-level aggregations of multiple projects — including portfolio health, resource utilization, and cost summaries — do not map directly to most destination tools. We migrate the underlying project data; portfolio rollup views must be rebuilt in the destination reporting layer. |
Gotchas
What to watch for in LiquidPlanner migrations
Issues we've hit on past LiquidPlanner migrations, tagged by severity. FlitStack AI handles every one — surfacing them up front because buyer engineering teams want to know.
API access requires Ultimate plan — migrations from Essentials or Professional need an alternative extraction path
LiquidPlanner Classic and Portfolio Manager both have announced sunset dates
Predictive scheduling range estimates do not map to fixed-date destination systems
Multi-owner task assignments require flattening in single-assignee platforms
Virtual Members import as full users in most destination platforms
| Severity | Issue |
|---|---|
| High | API access requires Ultimate plan — migrations from Essentials or Professional need an alternative extraction path |
| High | LiquidPlanner Classic and Portfolio Manager both have announced sunset dates |
| Medium | Predictive scheduling range estimates do not map to fixed-date destination systems |
| Medium | Multi-owner task assignments require flattening in single-assignee platforms |
| Low | Virtual Members import as full users in most destination platforms |
Leaving LiquidPlanner?
Where LiquidPlanner customers move next
5 destinations LiquidPlanner can migrate to.
How a LiquidPlanner migration works
Four steps, LiquidPlanner-specific
Connect
OAuth 2.0 (Bearer token) into LiquidPlanner. Scopes limited to read-only on the data we move.
Map
We translate LiquidPlanner-specific structures (custom fields, objects, value lists) to the destination's model.
Sample
Test with a 50–200 record subset to validate LiquidPlanner quirks before production.
Migrate
Full migration with LiquidPlanner rate-limit handling. Rollback available throughout.
FAQ
LiquidPlanner migration FAQ
Answers to the questions buyers ask most during LiquidPlanner migration scoping. Not seeing yours? Book a call.
Can't find your answer?
Walk through your LiquidPlanner migration with a real engineer — 30 minutes, free, written quote within 24 hours.
Book a free 30 minute consultationOther project management tools we support
Ready when you are
Migrate LiquidPlanner.
Without the rebuild.
Free scoping call with a migration engineer. Tell us about your LiquidPlanner setup and destination — written quote back within a business day.