Migrate from LiquidPlanner to Asana

LiquidPlanner Workspaces contain all Projects, Members, and Settings for an organization. We map Workspace-level member lists and settings to the Asana Organization workspace. Workspace-level custom field definitions must be recreated as Asana custom fields within the organization's field library; the custom field values attached to Projects and Tasks migrate as typed field data. Workspace-level configurations (notification settings, billing rates) do not have a direct Asana equivalent and are documented in the migration inventory for the customer's admin.

LiquidPlanner Projects map directly to Asana Projects. We preserve the project name, description, status, baseline dates, and start date. Project-level custom field values migrate to Asana custom fields within the project. Project health indicators from LiquidPlanner do not have a native Asana equivalent and are flagged for manual review. LiquidPlanner's project hierarchy (parent-child project relationships) maps to Asana Portfolio structure.

LiquidPlanner Packages are grouping containers within a Project that function like high-level phases or initiative buckets. We map Packages to Asana Sections within a Project, preserving the grouping structure and any custom field values attached to the Package. If the customer prefers a hierarchical structure, we can create subprojects under the parent Project and map Packages to those subprojects instead. The customer selects the approach during scoping.

LiquidPlanner Tasks are the core work item type and map directly to Asana Tasks. We migrate task names, descriptions, start dates, end dates, assignees, and custom field values. Range estimates (e.g., 3-5 days) from LiquidPlanner's predictive scheduling engine are converted to fixed start and end dates using the lower bound as start and upper bound as end, then flagged for the customer's PM to verify. Tasks that are part of a dependency chain of more than three steps are flagged individually because LiquidPlanner's auto-propagation will not replicate in Asana's Timeline.

LiquidPlanner Sub-Tasks map to Asana Subtasks nested within the parent Task. We preserve the subtask name, description, dates, assignee, and custom field values. Subtasks in LiquidPlanner that have their own Sub-Tasks are flattened to two levels maximum in Asana (Task > Subtask), with any deeper nesting converted to checklist items on the second-level subtask. The nesting depth reduction is documented in the field mapping deliverable.

LiquidPlanner supports finish-to-start, start-to-start, and wait-day dependencies. Asana's Timeline view supports finish-to-start dependencies natively. Start-to-start dependencies are converted to finish-to-start by adjusting the predecessor task's end date to align with the successor's start. Wait days (gaps between dependency-trigger and successor start) are added as an offset to the successor's start date or as a separate placeholder task, depending on gap length. Complex multi-step dependency chains are flagged individually during migration.

LiquidPlanner Milestones are zero-duration tasks with a target date. We preserve milestone names and dates as Asana Milestones. Milestones that drive downstream dependencies via LiquidPlanner's scheduling engine are flagged because the propagation behavior will not replicate in Asana; the customer's PM reviews and manually sets successor dates after migration.

LiquidPlanner Members (email, name, role, billing rate) map to Asana Users. We resolve Members by email match. Members without a matching Asana User go to a reconciliation queue for the customer's admin to provision before record import resumes. Billing rates from LiquidPlanner do not have an Asana equivalent; we preserve them in a custom field for reference or export to a timesheet system.

LiquidPlanner Virtual Members are lightweight references for external clients or stakeholders without a full license. Asana has no concept of a partial user. We import Virtual Members as full Asana User accounts with an explicit [Virtual Member] prefix in the display name, or as Contacts in the customer's Asana organization if the customer prefers not to create user accounts for external parties. The customer selects the approach during scoping.

LiquidPlanner allows multiple Members assigned to a single Task with individual effort allocations. Asana supports only one assignee per task. We split each multi-owner task into individual task assignments in Asana, with the effort allocation ratio preserved as a note on each resulting task. The total estimated effort is distributed proportionally. This split is documented in the pre-migration field mapping document so the customer can decide whether to consolidate owners manually or accept the split structure.

Time tracking data (hours logged, billable vs. non-billable flags, billing rates, approval status) migrates to a structured CSV export linked to the corresponding Asana task by task name and assignee. Asana has no native billing-grade timesheet module, so time entries do not map to a native Asana object. We recommend exporting to a format compatible with Harvest, Toggl, or the customer's preferred timesheet system. Individual logged-time entries and timesheet summaries are preserved as separate export sections for maximum flexibility in downstream processing.

LiquidPlanner custom fields at the Workspace and Project level migrate to Asana custom fields within the project's field set or the organization's field library. Custom field definitions (names, types, option lists) must be recreated in Asana before migration because Asana manages custom field schemas differently. We provide a custom field definition mapping document listing each LiquidPlanner custom field's name, type, and option values alongside the recommended Asana custom field configuration. Custom field values on Tasks and Projects migrate as data once the field schema is in place.

File attachments on LiquidPlanner Tasks and Projects migrate as Asana Attachments. If the customer's organization uses Google Drive, Dropbox, or Box, we create linked references in Asana rather than duplicating files. Standalone file attachments are exported to a designated cloud storage location with a manifest linking each file to its source task. PDF and document attachments migrate as attachment references pointing to the exported location.

LiquidPlanner Portfolio-level aggregations (portfolio health, resource utilization, cost summaries) do not map directly to Asana Portfolios, which aggregate project progress and status but lack resource utilization heatmaps and cost rollup. We migrate the underlying Projects and their data. Portfolio-level health indicators and resource utilization charts are documented in the migration inventory as items requiring manual recreation in Asana Dashboards or a third-party BI tool.