Migrate from Planio to Trello

Planio Projects are the top-level container in Planio's hierarchy. In Trello, we create one Workspace per Planio Project and one Board per Planio Issue tracker within that Project. If the Planio Project has multiple sub-projects, we nest Boards using Trello Workspace features. Project metadata (description, custom fields) migrates to the Board description or as Board-level Custom Fields via Power-Up.

Planio Issues map to Trello Cards on the corresponding Board. The Planio Issue subject becomes the Card name, the description becomes the Card description, and the Planio Issue status maps to a Trello List name. Priority, assignee, due date, and watchers map to Card labels (priority), Card members, Card due date, and Card subscriptions respectively. Custom field values on Issues require a Trello Power-Up with custom field support (Premium tier) or map to Card labels as tag-style values.

Planio sub-issues map to Trello child cards linked to the parent card via Trello's Board-level card relations feature. Cross-issue relations (blocks, duplicated by, related to) have no native Trello equivalent; we store them as structured text in the parent Card description and flag them for manual re-documentation. If the customer prefers, sub-issues can alternatively be stored as checklist items within the parent Card, but this flattens the relationship hierarchy.

Each distinct Planio Issue status value (e.g., New, In Progress, Feedback, Resolved, Closed) becomes a Trello List on the target Board. We create Lists in the same order as the Planio workflow sequence. If Planio uses multiple trackers with different workflows, we either create separate Lists per tracker or configure separate Boards per tracker depending on the customer's preference during scoping.

Trello does not have a native time-tracking object. We migrate Planio time entries as Card-level custom fields: a numeric Custom Field (via a Power-Up) storing total hours logged, and a text Custom Field storing the activity comment. If Trello Premium is available, we use the built-in Custom Fields Power-Up; if not, we store time data as Card labels with a structured naming convention (e.g., 'Hours: 4.5h'). Historical time entries are aggregated per Issue and stored as a single value on the corresponding Card.

Planio custom field definitions (text, integer, float, date, boolean, list, user, version) require pre-creation at the destination. Trello Premium supports custom fields natively; Trello Standard requires a Power-Up. We export Planio's custom field definitions during discovery, map each to the nearest Trello custom field type, create them on the target Board before card migration, and flag any Planio field types with no Trello equivalent for customer decision during scoping.

Planio Wiki pages have no direct Trello equivalent. We export wiki content as structured Markdown or HTML files and attach them to the corresponding Board Card (or Board description) as a file attachment. Internal Planio cross-references (links to other wiki pages or Issues) are rewritten as plain-text reference notes and flagged for manual update at the destination. Wiki pages are a secondary-priority migration object.

Planio Documents and Issue attachments migrate as Card attachments in Trello. We export file metadata and binary content, preserving the original filename. If multiple files share the same name (a common scenario in Planio), we apply a numbered suffix convention (file.pdf, file-1.pdf, file-2.pdf) to avoid Trello's duplicate-file overwrite behavior. Large attachment sets require chunked transfer with retry logic against Trello's API rate limits.

Planio Git and SVN repositories with commit-to-Issue linkages have no Trello equivalent. We extract commit hashes and Issue references from Planio's repository log, store them as Card labels or structured Card description notes, and flag the linkage for the customer's team to re-establish via Trello's GitHub or Bitbucket Power-Up post-migration. Full git history transfer is out of scope; we document the repository URL and commit reference structure for manual reconnection.

Planio Users map to Trello Board Members. We resolve users by email match against the Trello destination Workspace. If a Planio user has no matching Trello account, we hold them in a reconciliation queue for the customer's admin to provision before card import. Project-level role assignments in Planio map to Board membership and permission levels in Trello (Admin, Normal, Observer).

Planio News posts and Forum threads contain team communications and discussions with limited migration value in Trello's card-based model. We export these as structured text records with author and timestamp, attach them as Card descriptions on a dedicated Board or an 'Archive' Board Card, and note that they are low-priority migration objects requiring manual review post-migration.

Planio Help Desk Customers are a distinct role from Planio Users; they can submit tickets via email without a full account. In Trello, all Board participants are full members. We map Help Desk Customers to Trello Board Members (invited as guests with limited access if available) or tag their Card activity with a Customer label. Help Desk ticket history migrates as Card activity, but the customer-facing email threading is lost.