Trello → Jira
Move Trello boards, cards, members, and comments into Jira without treating one importer as a complete copy of checklists, custom fields, archived lists, or Butler rules.
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
Jira
- Deep workflow, issue, permission, and reporting controls support complex organizations
- Structured ownership, status, and workflow views improve operational visibility
- Administration and process complexity can slow teams that need a lighter workflow
- Custom fields, automations, history, and reporting are difficult to reproduce exactly
Jira: Deep workflow, issue, permission, and reporting controls support complex organizations. 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: Administration and process complexity can slow teams that need a lighter workflow.
Jump to a section
Know the shape of the move.
This timeline assumes
- Up to 80 Trello boards, 25,000 cards, and 200 members
- The team chooses the current Trello importer or the older Import Wizard before any destination write.
- Every imported member has a valid email that already exists on the Jira site, or an org admin will add that person first.
- A representative board is imported and signed off before the remaining workspace.
- The migration team records evidence for every blocking verification check.
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 |
|---|---|---|---|---|
| Boards become Jira spaces | partial | critical | Each imported Trello board becomes a new Jira space with a Kanban board. The current importer pulls one workspace and one board at a time. Atlassian also says a board is the unit you map to a space in the older wizard. | Name the space and key before import. Pilot one busy board, then import related boards as separate spaces. |
| Lists, cards, and board columns | partial | critical | The current importer creates work items on a Kanban board. Atlassian documents a failure mode where Trello column names become issue statuses, but the Jira board still parks those statuses under To do until you rebuild columns. | After import, open Board settings and drag each status into a matching column. Compare card counts by list. |
| Members without a usable email | partial | critical | The current importer asks for a valid email per user. People without an email appear as Anonymous or @trellousername. Product admins can only attach existing site users. New people need an org admin invite first. Users who can create team-managed business spaces cannot move users, so fields stay unassigned and comment mentions become plain text. | Build an email sheet before import. Have an org admin invite missing people. Do not let a product-admin-only run own the production load. |
| Archived cards and archived lists | partial | high | On a software-space import, Atlassian says archived cards and archived lists do not come across. On a business-space import, archived cards arrive as Done and archived lists do import. | Confirm software versus business before you design history. Export archived cards from Trello if you still need them. |
| Checklists | partial | critical | The older software-space path does not import checklists. The business-space path imports them as sub-tasks. Atlassian Community later described checklists as in scope for the newer importer, so the outcome depends on which importer you run. | Count checklists on the pilot board. If they are missing, export them from Trello JSON or a checklist tool and recreate them. |
| Custom fields | partial | high | The older software-space path does not import Trello custom fields. Community copy for the newer importer lists custom fields as in scope. CSV export is a poor home for them. | Inventory custom fields. Verify each one on the pilot. Archive values that did not land. |
| Comments and activity | partial | high | Trello CSV exports omit comments. A single-board JSON export only keeps the 1,000 most recent actions, including comments. A Premium Workspace export is the path Trello documents for all comments. | Take a Workspace JSON export before import if comment history matters. Compare comment counts on decision-heavy cards. |
| Attachments and cover images | partial | high | A Workspace export can include raw attachments in a zip if you tick that option. Otherwise the export only links to files still hosted on Trello. Inbox cards cannot be exported until you move them onto a board. | Move Inbox cards first. Download a Workspace export with raw attachments and open a sample after import. |
| Butler rules and Power-Ups | lost | critical | Atlassian says Trello automation rules do not become Jira automation. Power-Ups that wrote extra card data also stay behind. | Export the Butler rule list. Recreate only approved Jira automation after intake moves. |
| Team-managed versus company-managed spaces | manual | high | The older wizard creates a team-managed space per board. You can later bulk-move work into a company-managed space if you need schemes, more permission control, or a different template. Jira Product Discovery is not this importer. That path needs CSV. | Decide the destination template first. Rehearse the bulk move on the pilot if company-managed is required. |
| CSV as a fallback | partial | high | Trello says you cannot recreate a board from JSON or CSV. Premium CSV omits archived cards unless you add .csv to the board URL. Comments never sit in CSV. | Use CSV only for a field you already reconciled. Prefer the live importer plus a JSON archive. |
Where each thing goes.
| Source | Destination | Method | Notes |
|---|---|---|---|
| Trello board | Jira space plus Kanban board | transform | One board per import on the current importer. |
| List or column | Status, then a board column you place by hand | transform | Confirm the board view after import. |
| Card title and description | Work item summary and description | automatic | Keep the Trello card URL in the description. |
| Members | Jira assignee or people field | manual | Missing emails become Anonymous or @username. |
| Checklist | Sub-tasks, native checklist, or archived text | transform | Outcome depends on importer and space type. |
| Custom field | Jira field or archived note | transform | The older software path drops these. |
| Comment or attachment | Jira comment or file | transform | CSV will not carry comments. |
| Label | Jira label | transform | Compare label counts on the pilot. |
| Butler rule or Power-Up | No destination | unsupported | Rebuild selected rules in Jira automation. |
Make the move recoverable.
Create the source-of-truth backup
Preserve Trello boards, cards, comments, files, and members before any Jira write.
- Export each in-scope board as JSON. Take a Premium Workspace export if you need every comment.
- Include raw attachments in the Workspace zip when history files matter.
- Move Inbox cards onto a board before export. Count archived cards and lists.
- Hash every export and keep a member email sheet.
Proof to capture: A signed manifest reconciles every scoped board, card class, export file, count, and hash.
Importer, space, and user map
Pick the importer and the people path before Jira creates spaces.
- Choose the current importer or the older wizard, and software versus business.
- Map each board to a space name and key.
- Collect a valid email for every member an org admin must invite.
Proof to capture: Save the input, output, command or tool settings, warnings, and final item counts.
Board-by-board import
Create Jira work items without losing list meaning or comments.
- Import the pilot board and rebuild board columns from imported statuses.
- Compare cards, checklists, comments, and files against the JSON export.
- Only then import the remaining boards.
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.
Members import as Anonymous
A missing email, or a product-admin-only import, drops assignees and turns mentions into plain text.
- Consequence
- Active work looks ownerless and comment history loses people.
- Mitigation
- Finish the email sheet and org-admin invites first. Keep the Trello username on the work item.
Stop if: A critical card has no recoverable owner.
The board view hides imported lists
Statuses arrive with Trello column names while the Kanban board still groups them under To do.
- Consequence
- The team thinks cards vanished when they only sit in the wrong column.
- Mitigation
- Rebuild board columns immediately and reconcile counts by original list.
Stop if: List counts and board columns disagree after the pilot.
Both tools keep writing
Butler still runs on Trello while Jira automation starts on the same work.
- Consequence
- Statuses diverge and comments duplicate.
- Mitigation
- Turn off Butler and freeze Trello writes before Jira owns intake.
Stop if: An unapproved Trello writer remains active.
Do the work in this order.
- Days 1–4 · inventory
Inventory and mode choice
8–16 hours active3–4 days elapsedOwner review waiting- Inventory boards, lists, members, Power-Ups, Butler rules, and Inbox cards.
- Choose the importer, space type, and what stays archived in Trello.
Depends on: Trello Workspace admin and Jira org or site admin access
Stop / go checkpointExport?
Go when: Every critical board has an owner and disposition.
Stop when: Software versus business, emails, or consent is unclear.
- Days 4–7 · backup
Backup and reconcile
6–12 hours active2–3 days elapsedWorkspace export processing waiting- Create JSON and attachment exports.
- Reconcile counts, hashes, and the member email sheet.
Depends on: Approved inventory
Stop / go checkpointTransform?
Go when: Source totals and export manifests agree.
Stop when: Any critical board, comment class, or attachment set is absent.
- Days 7–18 · pilot
Map and pilot
14–45 hours active6–11 days elapsedOwner review of the sample waiting- Import one board that includes a checklist, a file, an archived card, and a member without Jira access.
- Rebuild board columns and compare keys, comments, and attachments.
Depends on: Verified backup
Stop / go checkpointScale?
Go when: Pilot mappings, access, and evidence pass.
Stop when: Any critical check fails or a count is unexplained.
- Days 16–28 · cutover
Final delta and switch
6–24 hours active2–6 days elapsedRemaining board imports waiting- Freeze Trello writes and Butler.
- Import the remaining boards, switch intake, and run blocking checks.
Depends on: Passed pilot and approved rollback
Stop / go checkpointOpen production?
Go when: Every in-scope card is accounted for and Jira owns intake.
Stop when: A Trello writer remains active or a blocking check fails.
- Days 20–40 · observe
Observe and close
4–18 hours active5–12 days elapsedOne planning cycle waiting- Watch one complete planning and delivery cycle.
- Sign the verification report before you close rollback.
Depends on: Verified cutover
Stop / go checkpointClose rollback?
Go when: No trigger occurs during the agreed observation period.
Stop when: Work, access, or reporting regresses.
Cut over with a way back.
Cutover
Make Jira the only intake system without losing the final Trello delta.
- Freeze Trello writes, Butler, and new card intake.
- Export and import the final changed boards or cards.
- Switch forms, email, and developer links to Jira.
- Run every blocking check and keep Trello readable.
- Keep the source intact through the rollback window.
Proof to capture: Jira owns intake, every in-scope Trello card is accounted for, and every blocking check has evidence.
Rollback
Return intake to Trello without losing Jira-era changes.
- Stop new writes and automation in Jira.
- Restore Trello access, Butler, and intake.
- Export the Jira post-cutover delta.
- Review and apply safe destination-era changes to Trello.
- Run the same blocking checks against Trello.
Proof to capture: Trello again owns intake with current work and no duplicate Jira action.
- Unexplained missing Trello cards
- Missing or exposed comments or files
- Duplicate production action
- Failed access or assignment check
- A critical workflow has no safe Jira replacement
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 reconciliation | Compare every in-scope Trello card to a Jira work item, archive, or exclusion. | 100% of scoped cards are accounted for. | Card ledger. | |
V-02Blocking | Lists and board columns | Compare each Trello list to a Jira status and a visible board column. | Column placement matches the signed map. | Board configuration export. | |
V-03Blocking | Members and missing emails | Test matched, invited, Anonymous, and product-admin-only cases. | Assignments follow the sheet. Unmatched usernames remain on the work item. | User matrix. | |
V-04Blocking | Checklist survival | Open cards that had checklists on the pilot board. | Each checklist is a sub-task, a native checklist, or a signed archive. | Checklist report. | |
V-05Blocking | Comments and files | Open decision-heavy cards and their attachments as ordinary users. | Required history and files work without a Trello login. | Context log. | |
V-06Blocking | Archived cards and lists | Compare archived Trello items to the chosen software or business path. | Each archived item is imported, marked Done, or explicitly excluded. | Archive ledger. | |
V-07Blocking | Single writer | Create and update a test card after freeze. | Only Jira acts. Trello stays still. | Automation log. | |
V-08Blocking | Permissions | Test admin, member, customer, and unauthorized accounts. | Least privilege holds. | Access matrix. |
Remove the scaffolding safely.
Safe after: One complete planning cycle, at least seven stable days, and owner sign-off on every blocking check.
- Archive Trello exports, maps, and verification evidence.
- Revoke migration tokens and unused Trello OAuth grants.
- Remove obsolete Butler rules, Power-Ups, and webhooks.
- Keep Trello read-only through the approved retention window.
- Cancel paid Trello plans only after billing, legal, and recovery review.
- Schedule the next Jira backup, access, and playbook review.
When the plan met reality.
First-hand accounts are preferred. Vendor case studies are labeled, and every note below is an editorial paraphrase—follow the link for the full context.
Filip Kubala describes THEY.dev leaving free Trello and Clockify after a client asked for a report that no longer matched the original spreadsheet. He spent more than 14 hours in Excel matching Clockify time to Trello cards. The shop had grown from two freelancers to about 20 users including clients. They wanted subtasks, time on the issue, a backlog, and reports. He says Atlassian's Trello importer was easy to find, and the harder work was convincing clients and developers. After a year they kept Jira for estimates, log work, and Bitbucket links. Developers still called Jira slow, and permissions needed a Confluence article. Roadmaps in Next-gen and hour estimates in Classic did not work together when they wrote the post in January 2021.
- Export Trello and time-tracking data before you promise a client report from Jira, and reconcile cards to the original estimate sheet.
- Pilot permissions with a client-visible board. THEY.dev found Users, Groups, Roles, and permission schemes much harder than Trello's per-board membership.
- The importer was not the hard part. Reporting, client buy-in, and speed were.
- Some developers still preferred Trello a year later, even though the company kept Jira.
ServiceRocket, an Atlassian Platinum Partner, published a Thoughtworks case study dated 12 December 2025. It says Trello was the most used enterprise tool, with 3,500 people on at least 6,000 active boards, and 45 Power-Ups to replace. ServiceRocket describes a four-phase path: Jira setup, a mapping matrix for migrate versus archive, custom scripts with sandbox dry runs and UAT, then change management. The published result is 1,000 boards moved to Jira Cloud and about 16 to 18 native Jira functions replacing those 45 Power-Ups, which they also frame as a 62 percent Power-Up reduction. This is a partner case study, not an independent write-up, and it does not show field-level importer fidelity.
- If you have thousands of boards, decide migrate versus archive before any importer run. Thoughtworks did not move all 6,000 active boards.
- Treat the 1,000-board and 62 percent Power-Up figures as ServiceRocket's published results, then count your own boards and Power-Ups.
- The partner path used custom scripts and sandbox UAT, not only Jira's built-in Trello importer.
- Power-Up replacement was part of the project, so a card import alone would not have finished the move.
Verify against the primary material.
Platform behavior changes. Check these sources and the review dates above before executing a production migration.
- Atlassian: import data directly from Trello into JiraAccessed 2026-10-26
- Atlassian: import data from TrelloAccessed 2026-10-26
- Trello: export data from TrelloAccessed 2026-10-26