Migrate Trello boards to Plane

Convert Trello boards into Plane projects with explicit card, checklist, comment and attachment mapping, source export limits and reversible cutover checks.

Last updated

In short

  • Trello board JSON and workspace exports have different history coverage.
  • Map lists by meaning rather than assuming every list is a workflow state.
  • Treat Plane import/API support as version-specific and reconcile every source card.
On this page (7)

Migration plans · Part of Plane

Decide how the board should behave in Plane

A Trello board can be a workflow, a collection of ideas, a calendar or a set of unrelated lists. Plane’s projects and work items need an explicit target model. The goal is to preserve useful planning behavior, not to force every list into a status simply because it appears as a column.

This is a reference migration design and acceptance exercise, not an executed converter. Record the Trello plan and export method, Plane release, API version and edition. The Plane edition guide distinguishes Community, Commercial and Airgapped offerings; verify the features and licensing required for the chosen target.

Select an export that covers the required history

The Trello export documentation distinguishes board JSON, Premium CSV and workspace exports. Board JSON includes only a limited recent action history, while CSV does not include comments. Workspace export options can include raw attachments. These distinctions matter before promising complete migration fidelity.

Preserve the source export in controlled storage and record when it was generated, by whom and which boards it covers. A link to an attachment is not the attachment itself. If the export contains links only, download the required files while access remains available and verify their content.

Build the card-to-work-item mapping

Trello object Plane treatment Decision to record
Board Project or agreed project grouping Visibility and membership
List State, module or retained category Meaning of each list
Card Work item Stable source card ID and URL
Description Supported rich-text/Markdown representation Formatting and embedded links
Members Mapped assignees Missing or inactive users
Labels Project labels Color and semantic differences
Checklist Sub-items or structured description Individual completion state
Due date Target date field Timezone and reminder behavior
Comments Supported API reconstruction or archive Original author/time provenance
Attachments Supported upload or retained archive Content and permission checks
Butler/Power-Ups Separate workflow redesign No assumed automatic transfer

A synthetic board might contain Ideas, Ready, Doing and Reference. The first three can describe planning states, while Reference may be better represented as documentation or a separate collection. Have the team owner approve that interpretation before creating hundreds of work items.

Verify the actual target API surface

Plane’s API reference documents projects, work items, states, labels, comments and attachments, with versioned API navigation. Use the endpoints and fields supported by the deployed version. Do not assume a native Trello importer exists or that a custom script can set historical authorship and timestamps without restriction.

Create a migration ledger containing source card ID, target work-item ID, content digest or revision marker and processing status. Create shared states, labels and user mappings first. Then create work items and apply comments, relationships and attachments through supported operations. Respect rate limits and retry only operations whose outcome can be reconciled.

Preserve provenance without manufacturing history

If comments are recreated under a migration service account, label the original author and time as source metadata. Keep an archive of the original export for details the target cannot represent. Do not imply that every reconstructed activity is a native historical event.

Archived cards need a deliberate scope decision. They may contain completed work required for reference, but moving all of them into active planning can overwhelm the target project. Record which are imported, archived separately or excluded with owner approval. A count mismatch is acceptable only when it matches that explicit decision.

Run a varied acceptance board

Build a synthetic board containing an archived card, a card with several members, a completed checklist item, a due date, an attachment and a comment thread. Include a private board and a guest participant.

Check Required result
Card reconciliation Every in-scope source ID maps once or has an accepted exception
State meaning Target state matches the team’s intended workflow
Checklist Completion information remains usable
Dates Same intended deadline in the user’s timezone
Comments Available history and known export limits documented
Files Downloaded content matches and access is restricted
Permissions Guest cannot see unrelated projects or attachments
Automation No unexpected notification or duplicate task creation

Ask users to perform the actual planning actions: create work, assign it, move it, find completed work and open a referenced file. A migration that preserves text but breaks the daily workflow needs redesign before cutover.

Cut over and keep a reversible source

Freeze the board or define a final edit window. Export the final changes and reconcile cards modified after rehearsal. Disable source automations before enabling equivalent target workflows, then update team links and communicate the authoritative location.

Keep Trello accessible for the agreed rollback window. Trello’s documentation notes that its JSON/CSV exports are not a direct board-recreation import path, so an export alone should not be treated as a ready rollback mechanism. Preserve the actual source board and its access while validating the move.

If target work begins and rollback is required, record new cards, comments and state changes and reconcile them into the source deliberately. Back up Plane’s database, files, configuration and required secrets. Retire the source only after the owner accepts workflow behavior, permissions and the explicit history limitations.

Sources and further reading

Use the linked documentation to confirm the version, edition and contract that apply to your project.

Scope our planning migration

Bring sample boards, list meanings, required comment history and any Butler or Power-Up workflows.