Migrate from Planview ProjectPlace to Trello

ProjectPlace Workspaces are the top-level container, analogous to Trello Boards at the project level or Trello Enterprise Organizations for portfolio grouping. For single-Workspace migrations, we map Workspace directly to a Trello Board. For multi-Workspace organizations, we map each Workspace to a Trello Organization with Boards beneath it, preserving workspace descriptions, member lists, and visibility settings at the time of export. Trello free tier supports one Workspace; Enterprise or Standard tier is required for multi-board Organization structures.

ProjectPlace Tasks and Activities map to Trello Cards within a List. Assignee, due date, start date, description, and checklist items migrate directly. The task hierarchy (parent-child subtasks) maps to Trello Cards with parent-card Checklist items or Card Relations Power-Up for flat structures. Status from ProjectPlace maps to the Trello List position; we enumerate every distinct status value per Workspace during scoping and map each to a List name. Watch for the date recalculation behavior: we freeze task dates by snapshotting the live calculated schedule before export, then replay the date tree at the destination preserving the upstream dependency structure.

ProjectPlace Kanban boards within Workspaces map directly to Trello Boards. Column names, card assignments, and card-level metadata migrate as-is. We preserve the board's card ordering within each column. If the ProjectPlace board has more than one swimlane view (e.g., by assignee or status), we flag this as a List-splitting decision for the customer's admin during scoping since Trello does not support swimlanes natively.

ProjectPlace Gantt charts are derived from task start/end dates and dependency links. Trello has no native Gantt view. We preserve the schedule hierarchy and dependency links by mapping tasks to Cards with due dates representing the Work Plan end date, then reconstructing the dependency graph using Trello's Card Relations Power-Up (Successor/Predecessor links). Milestone markers from the Gantt become Cards with a Milestone label and a fixed due date. The customer should enable the Card Relations Power-Up before migration begins; we document the dependency chain in a CSV alongside the migrated Cards for manual verification.

ProjectPlace Milestones are standalone schedule markers that can be linked to multiple tasks. We map milestone names and dates to Trello Cards with a Milestone label, a pinned due date, and a Card Description noting the linked tasks. We flag any milestones that were unanchored by downstream date changes in ProjectPlace before export so the customer's PM can validate the corrected date in Trello.

ProjectPlace stores documents within Workspaces. We export document metadata (name, uploader, upload date, URL) and catalog the attachment references. Binary file blobs require a separate file transfer step; we orchestrate parallel file migration alongside the data migration and link each file to the corresponding Card as an attachment or as a labeled external link if the file is hosted in a connected cloud storage service.

ProjectPlace user accounts map to Trello Members by email address match. We preserve user names, email addresses, and Workspace membership. Trello's admin roles (Workspace Admin, Board Member, Observer) do not have a direct ProjectPlace equivalent; we map ProjectPlace Workspace Admins to Trello Workspace Admins and standard members to Board Members by default, flagging any exceptions for the customer's admin to confirm. Role-based permissions and custom ProjectPlace role configurations do not migrate cleanly and require manual reconfiguration in Trello Workspace settings.

ProjectPlace per-Workspace custom fields have no native Trello equivalent at the free tier. Trello's Custom Fields Power-Up (available on Standard and above) supports text, number, date, dropdown, checkbox, and label types. We enumerate the full custom field taxonomy during scoping, map each to the closest Trello Custom Field type, and pre-configure the Custom Fields Power-Up on each destination Board before Card import. Dropdown-type custom fields in ProjectPlace become Trello dropdown Custom Fields with the same options list preserved. Custom fields that have no Trello type equivalent (e.g., formula fields) are flagged for manual re-creation as Calculated Fields or as Description text.

ProjectPlace includes built-in task-level time tracking. Trello has no native time tracking feature. We export time entries (hours logged, date, user attribution) and map them to Trello Cards as a dedicated Time Log checklist item within each Card, or as a numeric Custom Field if the Custom Fields Power-Up is active. Reporting aggregations (e.g., total hours per project, per user) are not carried forward; the customer's admin rebuilds time reports in Trello using a connected time-tracking Power-Up or an external tool like Everhour.

ProjectPlace task and board discussions migrate as Trello Card Comments with the original text, author, and timestamp preserved. Nested reply threads and @mention formatting flatten into a flat comment stream because Trello does not support threaded comments natively. We flag any @mentions that reference inactive or non-provisioned users so they can be resolved post-migration.

File attachments on ProjectPlace tasks and documents require a separate blob transfer step. We catalog attachment references and filenames during the schema scan, orchestrate parallel file migration alongside data migration, and link each file to the corresponding Trello Card as an attachment. If the file source URL is no longer accessible, we flag the attachment as pending and note it in the migration report for the customer's admin to resolve.

ProjectPlace Agile boards with sprints map to Trello Boards with Lists representing sprint stages (e.g., Sprint Backlog, In Progress, Done). Sprint names, start/end dates, and board assignments migrate as Card labels and due dates. We create a dedicated Sprint Start and Sprint End checklist item on each Card to carry forward the sprint timing metadata. Burndown data does not carry forward; the customer rebuilds velocity calculations in Trello using a reporting Power-Up like Corwise or a connected analytics tool.

ProjectPlace custom status values and color-coded labels vary by Workspace. We enumerate the full status taxonomy during scoping and map each to either a Trello List (for workflow-stage statuses) or a Trello Label (for categorical tags). The customer chooses the mapping strategy during scoping. Any ProjectPlace status values that have no Trello equivalent are flagged in the migration scope document for manual resolution.

ProjectPlace's workload visualization aggregates task assignments per user across all Workspaces. We export the underlying task-assignee data as a CSV during migration so that workload balance can be reconstructed in Trello by filtering Cards by Member. Trello has no native cross-board workload view; the customer uses a reporting Power-Up or exports the member-assignment CSV for offline analysis.