Trello → Linear
Move active work from Trello boards to Linear teams without flattening list semantics, losing attachment or comment context, duplicating notifications, or importing a backlog nobody intends to own.
Should you make this move?
Both platforms have a case. Compare what you gain with what you give up before scheduling the cutover.
Trello
- Visual boards are immediately understandable and require almost no training
- Structured ownership, status, and workflow views improve operational visibility
- Dependencies, planning depth, reporting, and scale expose its simplicity
- Custom fields, automations, history, and reporting are difficult to reproduce exactly
Linear
- Fast, opinionated product-development workflows keep software teams focused
- Structured ownership, status, and workflow views improve operational visibility
- Non-software work and highly customized enterprise processes fit poorly
- Custom fields, automations, history, and reporting are difficult to reproduce exactly
Linear: Fast, opinionated product-development workflows keep software teams focused. This removes a major source-side concern: Dependencies, planning depth, reporting, and scale expose its simplicity.
What you lose: Visual boards are immediately understandable and require almost no training. What you inherit: Non-software work and highly customized enterprise processes fit poorly.
Jump to a section
Know the shape of the move.
This timeline assumes
- Editorial planning scale, not a Trello or Linear product limit: up to 20 active boards, 10,000 cards, 100 users, 200 labels, and 50 active Butler automations.
- A Linear workspace administrator runs the import; Linear teams, members, statuses, labels, cycles, and project conventions are created first.
- Individual Trello board exports are used because Linear documents that its Trello path does not accept a Workspace-level export.
- Native Trello CSV export is a Premium Workspace feature; otherwise transform each documented board JSON export into Linear's documented CSV shape.
- The migration moves active operational work; stale and completed boards are archived unless an owner approves import.
- The source remains read-only for at least one full delivery cycle after cutover.
What survives the move.
“Partial” and “manual” are not footnotes. They are work that must be scheduled and verified.
| Item | Outcome | Impact | What happens | Mitigation |
|---|---|---|---|---|
| Card title and description | partial | critical | Linear directs Trello migrations to its CLI using individual board exports, but the reviewed documentation does not provide a Trello-specific field guarantee for title and description fidelity. | Map these fields explicitly and test Markdown, links, Unicode, long descriptions, and template cards before bulk import. |
| Board and list structure | partial | critical | Trello boards/lists can express teams, projects, workflow states, queues, or categories; Linear requires one deliberate model. | Map every board and list by meaning, not name, before import. |
| Card members | manual | high | The reviewed Linear documentation does not specify how Trello card members map through the CLI path. Linear issues have a single assignee, so multi-member cards need an editorially approved representation. | Choose and verify a primary assignee mapping; preserve additional collaborators manually as text, labels, or subscribers where appropriate. |
| Labels | partial | high | Tags can become labels, but duplicate names, colors, board-local scope, and inconsistent taxonomy can create noise. | Create a workspace label dictionary and merge synonyms before import. |
| Checklists | manual | high | Trello JSON can contain nested checklist data, but the reviewed Linear documentation does not specify a Trello checklist mapping for the CLI path. | Choose description checklist, manually created sub-issues, or archive per checklist type and validate completion state. |
| Comments | lost | critical | Linear's Trello migration uses its open-source CLI/CSV path, which Linear warns does not import data such as comments that richer assistants may support. An individual-board JSON export contains only the 1,000 most recent board actions, including comments. | When complete comment history is required, preserve it through a Premium Workspace export or another verified complete API/archive method. Otherwise document older comments as unavailable and obtain an explicit accepted-loss decision. Copy decision-critical comments into descriptions and retain an archive link. |
| Attachments and cover images | partial | high | CSV and links do not guarantee binary attachment import; source URLs can expire after access changes. | Download raw attachments, hash them, upload critical files, and retain a card-to-file manifest. |
| Custom fields | partial | high | Trello exports custom-field data, but Linear issue properties do not provide a universal direct mapping. | Map each field to label, priority, estimate, cycle, project, description, or archive. |
| Dates and reminders | partial | high | Due dates can map, but start dates, completion timestamps, reminders, recurrence, and calendar behavior differ. | Define date semantics and rebuild recurrence or reminders deliberately. |
| Butler automation | lost | critical | Rules, buttons, scheduled commands, email reports, and integrations do not execute in Linear. | Inventory triggers and outcomes, delete obsolete automation, and rebuild essential behavior with Linear workflows or integrations. |
| Power-Ups and integrations | lost | high | Power-Up state, votes, aging, forms, calendars, dashboards, and linked services are platform-specific. | Export required data and approve an explicit replacement or retirement. |
| Card activity and audit history | lost | medium | Move history, edits, notifications, watches, and archival events do not become Linear activity history. | Keep board JSON and compliance evidence through the retention window. |
| Archived cards and boards | manual | medium | Bulk-importing history can bury current work and distort metrics. | Create a signed active/archive decision and keep historical boards in the read-only source or a static archive. |
Where each thing goes.
| Source | Destination | Method | Notes |
|---|---|---|---|
| Board | Linear team and/or project | manual | Choose based on ownership and delivery horizon, not visual similarity. |
| List | Issue status, project, label, or import disposition | transform | Every list needs one documented semantic mapping. |
| Card name | Issue title | transform | Map in the CLI input and verify empty, duplicate, Unicode, and long titles. |
| Card description | Issue description | transform | Map in the CLI input; verify formatting and repair Trello links and embedded references. |
| Selected primary card member | Assignee | manual | The Trello-specific mapping is undocumented; choose and verify one assignee, and give unmatched or additional members explicit treatment. |
| Labels | Issue labels | transform | Normalize board-local duplicates into a controlled taxonomy. |
| Due date | Due date | manual | The reviewed Trello-specific importer documentation does not guarantee this mapping; configure it and verify timezone and completed-due behavior. |
| Checklist | Description checklist, manually created sub-issues, or archive | manual | No Trello-specific checklist mapping is documented for the Linear CLI path. |
| Custom field | Priority, estimate, label, project, cycle, or description | manual | Map per business meaning and destination constraints. |
| Comment/activity | No destination | unsupported | Preserve in the source JSON/archive or curate critical context manually. |
| Attachment | Linear attachment or durable external URL | manual | Download and re-upload critical binaries. |
| Butler rule | Linear workflow/integration | manual | Recreate from desired outcome after cutover. |
Make the move recoverable.
Create the source-of-truth backup
Preserve every board, card, required comment, attachment, custom field, automation, membership, and active-work decision before transformation, with an explicit accepted-loss decision for any unavailable older comment history.
- Inventory boards, lists, cards by state, archived items, members, guests, labels, custom fields, attachments, Power-Ups, calendars, email-to-board addresses, and Butler automation.
- Export each in-scope board in JSON; use native board CSV only with Premium eligibility, otherwise transform documented JSON fields into Linear's documented CSV shape. Do not substitute a Workspace-level export for Linear's individual-board import requirement.
- If complete comment history is required, create a Premium Workspace export or use another verified complete API/archive method; individual-board JSON contains only the 1,000 most recent board actions. If no complete method is available, record older comments as unavailable and obtain an explicit accepted-loss approval.
- When Premium is available, include raw attachments in the Workspace archive; otherwise download and hash critical attachments, then map them to board, card ID, and URL.
- Record card, comment, attachment, checklist, label, custom-field, and member totals per board, including any accepted comment-history gap.
Proof to capture: A board manifest reconciles counts and hashes and includes an approved import/archive decision for every list and card class.
Workflow semantics map
Translate board/list conventions into one coherent Linear operating model.
- Interview board owners about what each list means.
- Map active flow to Linear statuses and delivery containers.
- Archive queues with no current owner or action.
Proof to capture: Save the input, output, command or tool settings, warnings, and final item counts.
CSV normalization
Produce deterministic imports for Linear's CLI.
- Normalize users, state, tags, dates, descriptions, and tasks.
- Add stable Trello board/card IDs to descriptions or a manifest.
- Fail on unmapped required owners or states.
Proof to capture: Save the input, output, command or tool settings, warnings, and final item counts.
Context preservation
Retain decision-critical comments and files that the CSV path omits.
- Use a complete comment-history method when comments are required; otherwise approve and record the gap beyond the 1,000 most recent board actions.
- Identify available comments containing decisions, approvals, or requirements and copy critical context into the issue description with provenance.
- Upload critical files and keep the raw archive read-only.
Proof to capture: Save the input, output, command or tool settings, warnings, and final item counts.
The things most likely to hurt.
These are operating limits. Treat every “Stop if” condition as a blocked migration, not a suggestion.
List names are mistaken for statuses
Lists such as Q3, Bugs, Person A, or Reference are mapped to workflow states.
- Consequence
- The Linear workflow becomes unusable and metrics are meaningless.
- Mitigation
- Map list intent with owners before importing.
Stop if: Any active list lacks one unambiguous destination meaning.
Comments disappear unnoticed
Issue count matches but decision context is absent.
- Consequence
- Teams repeat decisions or ship against incomplete requirements.
- Mitigation
- Curate critical comments and retain the JSON/source archive.
Stop if: A critical card's acceptance or decision trail exists only in comments.
Automations act in both systems
Butler and Linear integrations both create or move work.
- Consequence
- Duplicate issues, status changes, and notifications.
- Mitigation
- Disable source automation before enabling destination automation.
Stop if: A test action changes both systems.
Inactive backlog overwhelms current work
Imported issue count greatly exceeds owned active cards.
- Consequence
- Search, triage, and metrics become noisy from day one.
- Mitigation
- Import only owned, actionable work and preserve history separately.
Stop if: Any imported backlog class has no owner or review date.
Members are assigned incorrectly
Email mismatches leave issues unassigned or assign the first wrong member.
- Consequence
- Work and notifications go to the wrong person.
- Mitigation
- Pre-create an identity map and reconcile assignee counts.
Stop if: Any critical issue has an unexplained assignee.
Do the work in this order.
- Days 1–2 · scope
Triage and destination design
8–12 hours active2 days elapsedBoard-owner review waiting- Classify boards and cards as import, archive, or discard.
- Define Linear teams, statuses, projects, labels, identities, and permissions.
Depends on: Trello admins, board owners, Linear admin
Stop / go checkpointApprove the operating model?
Go when: Every board/list and active-work class has an owner and destination.
Stop when: The model copies visual layout without agreeing workflow meaning.
- Day 3 · backup
Export and manifest
4–7 hours active1 day elapsedWorkspace or API archive generation when complete comments are required waiting- Export individual-board JSON and CSV for import preparation.
- Use a Premium Workspace export or another verified complete method for required comment history; otherwise approve and record the older-comment loss.
- Download critical attachments and reconcile counts.
Depends on: Approved scope
Stop / go checkpointIs context recoverable?
Go when: Cards, required comments, attachments, fields, members, and automation are represented or have an explicit accepted-loss decision.
Stop when: Any critical board or decision trail lacks a complete archive or approved loss.
- Days 4–6 · pilot
Transform and pilot
9–14 hours active3 days elapsedCLI import and owner review waiting- Normalize a simple and a complex board.
- Import to a test team and validate workflow, users, fields, context, and files.
Depends on: Linear workspace admin, Backup
Stop / go checkpointApprove bulk import?
Go when: Representative owner scenarios and counts pass.
Stop when: Comments, assignments, workflow semantics, or critical files have no safe disposition.
- Days 7–9 · waves
Import in board waves
7–13 hours active2–3 days elapsedImport processing waiting- Import boards by team dependency.
- Reconcile issue, assignee, label, status, date, checklist, and context counts after each wave.
Depends on: Approved pilot
Stop / go checkpointFreeze Trello?
Go when: Every wave has no unexplained blocking variance.
Stop when: A wave creates duplicates, wrong assignments, or invalid workflow states.
- Days 10–11 · cutover
Freeze, delta, and integrations
3–5 hours active1–2 days elapsedFinal change application and integration delivery waiting- Freeze Trello changes and disable Butler.
- Apply reviewed final changes manually by stable card ID; never reimport CSV to update Linear issues because it can create duplicates.
- Switch forms, Slack, email, Git, calendars, and other intake paths.
Depends on: Reconciled waves
Stop / go checkpointMake Linear authoritative?
Go when: One intake system owns work and all critical integrations pass.
Stop when: A production path still creates or updates Trello cards.
- Days 12–15 · observe
Run one delivery cycle
1–4 hours active3–4 days elapsedNormal team workflow waiting- Keep Trello read-only and observe triage, assignment, planning, delivery, and reporting.
- Complete verification and owner sign-off.
Depends on: Successful cutover
Stop / go checkpointClose rollback window?
Go when: Teams complete normal workflow with no missing critical context or source write.
Stop when: Critical work, context, access, or automation remains broken.
Cut over with a way back.
Cutover
Make Linear the only editable work tracker after capturing the final Trello changes and disabling source automation.
- Announce and enforce the Trello edit freeze.
- Disable Butler, email-to-board, forms, and integrations that write to Trello.
- Record changes since the last import and apply them manually by stable Trello card ID; do not reimport CSV as an update mechanism.
- Reconcile active issue, assignee, status, due-date, label, and context counts.
- Enable Linear intake and integrations one at a time.
- Make Trello boards read-only and pin a notice with the Linear destination.
Proof to capture: Active-work counts reconcile, all tested intake paths create one correct Linear issue, and Trello receives no production write.
Rollback
Resume Trello as the work system while preserving actions performed in Linear after cutover.
- Freeze Linear issue changes and capture only scoped post-cutover fields through a verified Linear export or API, using a manual ledger where coverage is incomplete.
- Re-enable Trello editing only for approved owners.
- Apply reviewed new issues, status, assignee, date, and comment changes back to Trello.
- Restore Butler and integrations from the versioned inventory.
- Disable Linear production intake and announce the source-of-truth change.
Proof to capture: Trello contains all approved post-cutover work and one test intake follows the restored workflow while Linear is read-only.
- Critical active work is missing
- Workflow mapping blocks normal delivery
- Wrong assignees or access affect critical work
- A required integration has no functioning Linear path
- Decision-critical context is unavailable
Prove the migration worked.
Every blocking check must pass. Capture the evidence before cleanup begins.
| Pass | ID | Check | Method | Expected result | Evidence |
|---|---|---|---|---|---|
V-01Blocking | Card disposition | Reconcile every source card to imported issue, archive, or approved discard. | 100% accounted for by stable card ID. | Card reconciliation CSV. | |
V-02Blocking | Board/list semantics | Run representative triage, planning, in-progress, blocked, done, and cancelled scenarios. | Statuses and containers match the approved operating model. | Workflow scenario log. | |
V-03Blocking | Assignees and access | Compare assignee totals and test member, guest, and unauthorized accounts. | Every critical issue has the correct owner and least-privilege access. | Identity and access matrix. | |
V-04Blocking | Descriptions, dates, labels, and checklists | Compare stratified cards including long, Unicode, overdue, complete, multi-label, and checklist-heavy examples. | All approved fields preserve meaning. | Record comparison sheet. | |
V-05Blocking | Critical comments and files | Review every card flagged as decision- or attachment-critical. | Required context is in Linear or a durable approved archive link. | Context manifest. | |
V-06Blocking | No duplicate behavior | Trigger each form, integration, rule replacement, and notification scenario. | One correct Linear action and no Trello write. | Integration delivery log. | |
V-07Blocking | Cycles, projects, estimates, and priority | Have each team run one planning and reporting session. | Owned work appears in the expected views and metrics. | Team-owner sign-off. | |
V-08Blocking | Archive usability | Recover one board, comment trail, and attachment solely from the preserved export. | Historical context can be retrieved without editing Trello. | Restore drill log. |
Remove the scaffolding safely.
Safe after: One complete delivery cycle, all blocking checks pass, and every team owner signs off.
- Preserve Trello JSON/CSV, attachments, mappings, importer versions, exception logs, and verification evidence.
- Revoke temporary API keys, tokens, and importer credentials.
- Remove obsolete Butler rules, email-to-board addresses, forms, Power-Ups, and webhooks after the read-only window.
- Keep Trello read-only under the agreed retention policy before cancelling licenses or deleting boards.
- Update team workflow, onboarding, intake, planning, and incident documentation.
- Schedule quarterly access, stale-work, label-taxonomy, integration, and archive-restore reviews.
Verify against the primary material.
Platform behavior changes. Check these sources and the review dates above before executing a production migration.
- Atlassian Support: export data from TrelloAccessed 2026-07-27
- Atlassian Support: understand Trello JSON exportsAccessed 2026-07-27
- Atlassian Support: Trello custom fieldsAccessed 2026-07-27
- Atlassian Support: Trello automationsAccessed 2026-07-27
- Linear Docs: import issuesAccessed 2026-07-27