Migrate your Trello data

Boards are the top-level container in Trello. We extract all boards from a workspace, including board visibility (public/private), description, and organization membership. Each board migrates as an independent project or workspace unit in the destination tool.

Lists represent workflow stages within a board. We preserve list order and name, mapping them to columns, swimlanes, or pipeline stages depending on the destination's data model. Archived lists are flagged for optional restoration.

Cards are the primary task unit. We migrate title, description (with Markdown rendering), due dates, start dates, cover colors, and sticker data. Card position within its list is preserved via ordering. Archived cards are migrated only when explicitly scoped.

Custom Fields graduated from Power-Up to core API in 2023. We map all supported field types (text, number, date, checkbox, dropdown) to their destination equivalents. Legacy Power-Up Custom Field data embedded in pluginData is extracted where accessible via API, but may require manual verification for older boards.

Labels are taggable color-coded categories per board. We preserve label names, colors, and the full set of labels applied to each card. Some destinations map labels to tags or category fields.

Checklists live on cards and can have multiple named items with completion states. When migrating to platforms that lack checklist semantics, we convert each checklist to a sub-task or comment block. Item order is preserved. Nested checklists are flattened to a single level.

Trello stores file attachments on Amazon S3 with per-plan size limits (10MB Free, 250MB Enterprise). We download all raw attachments at migration time and upload to the destination. Board-level attachments and cover images are included. Links to external URLs are preserved as-is and converted to link fields where supported.

Members are workspace users assigned to cards. We preserve assignee records as owner or assignee fields. Guest users with single-board access may not consume a Trello seat but still have attachment and comment data that requires mapping to a destination user identity.

Action history (card moves, edits, comments) is stored as a chronological log in Trello. Migrating full action history is not standard practice — we migrate current state data. Comment threads are preserved as discussion entries, but activity feeds are not transferred.

A Workspace is the organizational layer above boards. We map workspace membership and board groupings to organizational units, teams, or workspaces in the destination. Multi-workspace configurations require separate workspace creation or a unified workspace with board-level segmentation.

Power-Ups are third-party or Atlassian add-ons that extend Trello functionality. Each Power-Up stores data in its own schema that is not universally accessible via API. We do not migrate Power-Up state; customers should identify equivalent functionality in the destination platform before migration.

Calendar View is a Premium feature that renders cards with due dates on a calendar grid. This is a display layer — the underlying data (card + due date) is migrated normally. We flag Calendar-specific filtering or custom date ranges for manual reconfiguration post-migration.

Timeline View is a Premium feature using card start and due dates to render a Gantt-style display. Start dates are a Trello Power-Up field that may not exist on all cards. We migrate available date data and flag cards missing start dates for manual enrichment in the destination.

Dashboard View aggregates workspace-level metrics across boards. This is a reporting aggregation tool — the underlying card and list data is migrated. The dashboard configuration itself (charts, filters, scope) must be rebuilt in the destination platform.