Migrate from LiquidPlanner to Trello

LiquidPlanner Workspaces map to Trello Organizations (Business Class) or Workspace Free (Standard Free). We extract the Workspace member list and role assignments. Workspace-level custom field definitions must be recreated in Trello as Custom Fields Power-Up configurations. Workspace-level settings (notifications, default views) do not transfer; these require manual configuration post-migration.

Each LiquidPlanner Project maps to a Trello Board. We preserve the Project name, status (active, on-hold, completed), baseline dates, and description as the Board description. Project-level custom field values map to Trello Custom Fields on the Board level. We create the Board structure (Lists) during migration based on the customer's preferred Kanban layout, as LiquidPlanner has no native List equivalent.

LiquidPlanner Packages are grouping containers within a Project, typically representing phases or workstreams. We map each Package to a Trello List within the destination Board. Because Trello Lists are ordered horizontally and Packages are hierarchical within a Project, we flatten the Package hierarchy into a flat List structure and flag any Packages with sub-Packages for the customer to resolve as separate Boards or Lists. Package-level custom field values migrate as Card-level Custom Fields.

Tasks are the core work item and map 1:1 to Trello Cards. We preserve task name, description (as Card description), start date, due date, priority rank, and all custom field values. Tasks with multiple assignees are split into individual Card assignments; the effort allocation ratio is preserved as a Card comment. Wait days and dependency references are flagged as Card comments with a manual cross-reference note since Trello has no native dependency tracking.

LiquidPlanner Sub-Tasks migrate to Trello Checklist items on the parent Card. Because Trello supports multiple Checklists per Card, each LiquidPlanner Sub-Task becomes a separate Checklist. If the customer requires Sub-Tasks as standalone Cards, we create child Cards and link them via a Card link Power-Up, flagging this decision during scoping.

Milestones in LiquidPlanner (zero-duration tasks with a target date) map to Trello Cards with a dedicated Milestone label. We preserve the milestone name and target date in the Card description. Any milestone that drove downstream dependencies in LiquidPlanner is flagged for manual re-establishment in Trello via a Power-Up or the customer's preferred dependency tool.

LiquidPlanner supports finish-to-start, start-to-start, and wait-day dependency types with full chain visibility. Trello has no native dependency tracking. We capture all dependency references during extraction and write them as Card comments in the format 'Depends on: [Task Name]' for manual re-establishment. If the customer licenses a Trello dependency Power-Up (such as Dependencies or Card Relationships), we map the dependency references to those tools during migration and flag any dependency chains longer than three steps for manual review.

LiquidPlanner Members (users with full licenses) map to Trello Members by email match. We extract name, email, role, and billing rate from LiquidPlanner and create corresponding Trello accounts. Billing rate is preserved as a Card custom field or as a note on the Member's profile for later reference in Trello integrations.

LiquidPlanner Virtual Members are external clients or stakeholders without a full license. We flag Virtual Members during scoping and import them as Trello Members (they become full user accounts) or as Board Guests, depending on the customer's preference. We document which approach was chosen for each Virtual Member in the pre-migration handoff.

Time entries in LiquidPlanner (hours logged, billable vs. non-billable flags, billing rates, approval status) require creative mapping in Trello. We add total logged hours to the Card description and create a custom time-tracking Power-Up field on each Card, or preserve the raw time entry data as a structured Card comment if the customer has no Power-Up preference. Approval status and billing rate flags are preserved as Card labels or custom fields. Trello's native time tracking is not available without a Power-Up.

LiquidPlanner custom fields at the Project and Task level (Pick List, Text, Date, Numeric, Currency) map to Trello Custom Fields Power-Up fields. We create the destination Custom Field definitions before migration and map values accordingly. Only Trello Standard and Premium include the Custom Fields Power-Up; we flag this during scoping if the customer is on Trello Free. Custom field options from LiquidPlanner Pick Lists migrate as Custom Field option values in Trello.

File attachments on LiquidPlanner Tasks and Projects migrate as Trello Card attachments. We extract the file content and re-upload as a Trello attachment if the file is under Trello's 10MB per-attachment limit. Files exceeding the limit are exported to the customer's Google Drive, Dropbox, or SharePoint and linked as a URL reference on the Card. We confirm the preferred external storage destination during discovery.