---
title: "Trello to Jira Migration: Field Mapping & Rollback"
description: "Migrate Trello to Jira with FlitStack AI: field-level mapping, a sample run you approve, full history and one-click rollback."
url: "https://flitstack.ai/migrations/pm/trello/to/jira"
---

# Trello to Jira migration

We migrate Boards, Lists, Cards, Custom Fields, Labels, and Attachments from Trello into Jira Projects and Issues with the archived-card gap, checklist-to-subtask behavior, and assignee-limit resolved before cutover, and we deliver a written inventory of every Butler automation requiring manual rebuild in Jira.

Short answer

FlitStack AI migrates projects, status, issues, sub-tasks and custom fields from Trello to Jira, with their history and the associations between records. Every field is mapped and validated, a sample run is checked with you before the full migration, and the whole move can be rolled back in one click. Typical timeline: 2-4 weeks.

![](https://flitstack.ai/images/authors/aditya-kumar.webp)By [Aditya Kumar](https://flitstack.ai/about/aditya-kumar) Updated November 5, 2026

[Get a quote ](https://flitstack.ai/contact) [See what moves →](https://flitstack.ai/migrations/pm/trello/to/jira#what-moves)

![](https://flitstack.ai/images/illustrations/pair-stage.webp)

Source Trello ![](https://flitstack.ai/platforms-trim/trello.webp)

Destination Jira ![](https://flitstack.ai/platforms-trim/jira.webp)

Project Status Issue Sub-task Custom Field

Mapped field by field · sample run · one-click rollback

## What moves from Trello to Jira?

Trello and Jira are both Atlassian products, but their data models differ significantly.

Read the full summary

Trello uses a flat board/list/card hierarchy; Jira uses Projects containing Issues organized by Issue Type (Epic, Story, Bug, Task) within configurable workflows. Each Trello board maps to one Jira Project, each List maps to a workflow status, and each Card maps to an Issue. The native Jira Trello importer does not carry over archived cards, custom fields, or Butler automation rules, and it drops multiple card assignees silently. We extract Trello data via the REST API, resolve Custom Field storage locations (core API versus legacy pluginData), map all Labels to Jira component or label fields, download attachments from Trello's S3 storage, and re-upload them to Jira with its 10MB per-file ceiling enforced. We do not migrate Butler automation rules or Power-Up data as code; we document them for the customer's admin to rebuild in Jira Automation or Jira Workflow.

1:1

### Board → Project

Each Trello board maps to one Jira Project.

How it maps

We provision the Jira Project using the board name as the Project Key (first 9 characters, uppercase) and map board visibility (public/private) to the Jira project's permission scheme. Atlassian recommends keeping board count below 15,000 per workspace for migration performance; we flag any workspace exceeding this and work with the customer to archive inactive boards before migration begins.

1:1

### List → Status (workflow step)

Trello lists map to workflow status values within the Jira project's default workflow.

How it maps

List order is preserved as the sequence of status values. We configure the Jira workflow to include each list name as a distinct status (To Do, In Progress, Review, Done) and map archived lists: in software space they are skipped; in business space archived lists and their cards are imported with Done status.

1:1

### Card → Issue (Epic, Story, Task, Bug)

Trello cards map to Jira Issues.

How it maps

Card title becomes Issue Summary; description (Markdown) migrates as Jira text. Due dates and start dates migrate to Due Date and Start Date fields. Card cover colors migrate as Jira label or comment with color metadata. We map card position within list to Jira priority or a custom ranking field if the customer uses ranked backlog views.

1:N split

### Checklist → Sub-task

Trello checklists (multiple named lists per card, each with completion states) map to Jira sub-tasks.

How it maps

In Jira business space, the native importer converts checklists to sub-tasks automatically. In software space, the importer does not transfer checklists at all. We detect the destination Jira space type during scoping and apply either the native import path or our own sub-task generation from the Trello API checklist data to ensure no checklist data is lost in software-space destinations.

mapping

### Custom Field → Custom Field

Custom Fields graduated from Power-Up to core API in 2023, but older boards may store Custom Field definitions and values in card pluginData rather than the structured API response.

How it maps

We detect which storage mechanism is in use during discovery and apply the appropriate extraction method. Legacy pluginData extraction is less reliable and may require a post-migration manual audit of field values. Core API Custom Fields (text, number, date, checkbox, dropdown) map to Jira Custom Field equivalents with type-matching.

1:1

### Label → Label or Component

Trello labels (color + name per board) migrate to Jira Labels on each Issue.

How it maps

We preserve the label name and append the color code as a tag suffix if the customer needs color metadata for post-migration reporting. If the customer uses Jira Components as a parallel categorization layer, we map Trello label groups to Components and individual labels to Component names.

******What moves 11 objects

Trello Jira

- Board Project 1:1
- List Status 1:1
- Card Issue 1:1
- Checklist Sub-task split
- Custom Field Custom Field transformed
- Label Label or Component 1:1

\+ 5 more in the mapping below

## How Trello and Jira differ

The differences that decide how each record is mapped. These are what a CSV export and a native importer don't resolve for you.

| Dimension        | Trello                                                          | Jira                                                                                            |
| ---------------- | --------------------------------------------------------------- | ----------------------------------------------------------------------------------------------- |
| Data model       | Flat board/list/card hierarchy with no parent-child issue types | Hierarchical Projects with Epics, Stories, Bugs, and Tasks linked by parent-child relationships |
| Assignee model   | Unlimited members per card                                      | Single assignee per Issue; multi-user picker field requires custom configuration                |
| Archived records | Archived cards and lists stored and API-accessible              | Software space: archived cards NOT imported; business space: imported as Done status            |
| Custom fields    | Custom Fields via Power-Up (legacy pluginData) or core API      | Custom fields available at all tiers with type configuration per project                        |
| Checklists       | Multiple checklists per card with completion states             | Software space: checklists NOT imported; business space: imported as sub-tasks                  |
| Automation       | Butler rules per board (250-1,000 runs/month by tier)           | Jira Automation for project and cross-project rules; requires separate configuration            |
| Reporting        | None built-in; Premium views are display layers                 | Velocity, burndown, sprint, and custom reports from Standard tier upward                        |

## What to watch for in a Trello to Jira migration

The issues we plan around on this pair: limits and data-model gaps that the official import tools leave to you.

high

### Archived cards drop silently in software space imports

Jira's native Trello importer treats archived cards differently depending on the destination space type.

How we handle it

In a Jira software space, archived cards are not imported at all. In a Jira business space, archived cards are imported with Done status. We detect archived cards via the Trello API (idBoard, closed, pos fields) during discovery, report the count, and recommend the customer review whether archived cards should be restored before migration or excluded from scope. If the customer needs archived cards in a software-space destination, we re-activate them via the Trello API before import or generate Jira Issues with a Done-equivalent status manually.

high

### Multiple card assignees have no direct Jira equivalent

Trello allows unlimited members on a card.

How we handle it

Jira enforces single assignee per Issue. The native Jira importer drops all but the first member silently. We detect every card with more than one member during discovery and present three options: map the first member only, map to a Jira multi-user picker custom field (requiring Jira Premium or a Marketplace app), or distribute assignments across a linked sub-task structure. The choice is made during scoping so the mapping rule is applied consistently across all cards before any Issue is created.

medium

### Custom Field data may live in legacy pluginData storage

Custom Fields started as a Power-Up before becoming a core API feature in 2023.

How we handle it

Boards created or edited before the Custom Fields API was available may store field definitions and values in card pluginData rather than in the structured customFields API response. We detect which storage mechanism is in use during the discovery scan and apply the appropriate extraction method. Legacy pluginData extraction is less reliable and may require a manual post-migration audit of field values on a sample of records.

medium

### Butler automation rules do not migrate and have no Jira equivalent

Trello Butler rules (board-level command triggers, button commands, calendar commands) are configuration-as-code stored in Trello's proprietary format.

How we handle it

They have no Jira automation equivalent that can be auto-converted. We document every active Butler rule during discovery (trigger, conditions, actions) and deliver a written inventory with recommended Jira Automation rule equivalents. The customer's admin rebuilds these in Jira Automation post-migration. Butler automation run history is not preserved and does not migrate.

medium

### Trello API rate limits block bulk extraction at scale

Trello's API enforces 300 requests per 10 seconds per API key and 100 requests per 10 seconds per token, with a ceiling of 100 requests per 900 seconds on member endpoints.

How we handle it

Large workspaces with 500+ cards risk 429 errors and key-level blocking during bulk extraction. We throttle requests dynamically using exponential backoff and paginate aggressively. Workspaces exceeding 1,000 cards may require extended migration windows or a multi-window extraction strategy to stay within rate limits without data loss.

## How the migration runs

1. ### Discovery and workspace audit

   We audit the Trello workspace via the REST API across all boards, extracting board metadata, list names, card counts, member rosters, label definitions, Custom Field schemas (core API and pluginData), attachment URLs, and active Butler rules.

   What this step covers

   We identify archived cards, multi-member cards, and any board with more than 500 cards that may trigger API rate-limit issues. The discovery output is a written migration scope document with board-to-project mapping, Custom Field extraction method determination, and Butler rule inventory.

2. ### Jira destination setup

   We create Jira Projects for each migrating board, configure the default workflow to include Trello list names as status values, and provision custom fields matching the detected Trello Custom Field types.

   What this step covers

   We resolve the assignee strategy (single assignee or multi-user picker) with the customer's admin before project creation. If the customer uses Jira business spaces, we configure the space type upfront; for software spaces we document the archived-card and checklist gaps and agree on the handling approach before extraction begins.

3. ### Data extraction with rate-limit handling

   We extract Trello data via the REST API using paginated requests, extracting cards, attachments, comments, checklists, Custom Fields, and labels per board.

   What this step covers

   We run discovery and extraction in separate API windows to avoid exceeding rate limits on active token usage. Attachments are downloaded from Trello's S3 storage to a staging environment, re-named by card ID for traceability, and held for upload after Jira Issue creation. Custom Field extraction uses both the core API response and pluginData fallback where legacy storage is detected.

4. ### Sandbox migration and reconciliation

   We run a full migration into a Jira Sandbox or a parallel non-production project, then reconcile record counts per board (cards in, Issues out), verify that card descriptions, due dates, labels, and checklists transferred correctly, and confirm that attachments appear in Jira.

   What this step covers

   The customer's project lead spot-checks 25-50 random Issues against the Trello source and signs off before production migration. Mapping corrections for Custom Field type mismatches, status name changes, and assignee strategy adjustments happen at this stage.

5. ### Production migration in board sequence

   We migrate boards one at a time in agreed sequence, creating the Jira Project first, then Issues in list order with parent-child sub-tasks for checklists, then attaching files.

   What this step covers

   Each board migration emits a reconciliation report (cards migrated, issues created, attachments uploaded, attachments flagged for size, comments transferred, members resolved, multi-member cards flagged). We apply a write-freeze on Trello during the production migration window and run a final delta pass to capture any cards modified during extraction.

6. ### Cutover, validation, and Butler rebuild handoff

   We disable Trello write access during cutover, run a final delta migration, enable Jira as the system of record, and deliver the Butler automation inventory document.

   What this step covers

   We support a 72-hour hypercare window for reconciliation issues. We do not rebuild Butler rules as Jira Automation inside the migration scope; that work is documented and handed to the customer's admin or a Jira automation consultant for post-migration configuration.

![](https://flitstack.ai/platforms/trello.svg) Trello ![](https://flitstack.ai/platforms/jira.svg) Jira

1. Connect
2. Map
3. Sample
4. Migrate
5. Verify

- **Contacts** 48,210 / 48,210 Done
- **Companies** 9,134 / 9,134 Done
- **Deals** 6,377 / 11,920 In progress

Example run

******Restore points · Jira Rollback ready

1. Before sample run Restore point 01 Restore
2. Before full migration Restore point 02 Restore
3. After verification Restore point 03 Current

Example

## How long it takes, and what drives the quote

**2-4 weeks** Typical, smaller accounts

**4-8 weeks** Large or heavily customised accounts

A quote scales with board count, card volume, and automation rebuild scope. Every quote is scoped with you; there is no self-serve pricing.

[Get a quote for Trello to Jira →](https://flitstack.ai/contact)

## Why teams move from Trello to Jira

- Teams outgrow Trello's flat board/list/card schema when project complexity increases. Trello has no concept of parent-child issue types, sprint planning, or hierarchical backlogs. Jira provides Epics, Stories, Bugs, and Tasks with explicit parent-child linking, which enables proper Agile planning for engineering teams that have outgrown a single-board view. Reviewers on G2 and Atlassian Community consistently cite this as the structural gap that prompts the switch.
- Trello has no built-in reporting or analytics. Jira from Standard tier upward includes velocity charts, burndown charts, sprint reports, and custom JQL-based dashboards. Teams managing SLAs or tracking team throughput cannot do so in Trello without third-party integrations or manual spreadsheet work, whereas Jira delivers this natively at a lower feature-gate threshold than Trello's Premium tier.
- Trello's deadline tracking runs 24/7 with no pause for waiting states and no business-hours calculation. Teams with SLA contracts or support SLAs cite this as operationally unacceptable. Jira Service Management or Jira Software with an SLA Time app calculates elapsed time, pauses during Waiting-for-Customer transitions, and reports against contractual targets. This capability is absent from Trello at any tier.
- Trello's pricing jump from Free to Standard feels disproportionate for teams that need Calendar, Dashboard, or Workspace Table views. Jira Software Standard at $7.91/user/month provides Scrum and Kanban boards, reporting, and custom workflows without the Premium Power-Up tax, making it more cost-effective per capability for structured project teams. Atlassian's own blog positions Trello as a productivity hub and Jira as the structured project management tool, signaling the intended upgrade path.
- Butler automation caps on lower tiers (250 runs/month on Free, \~1,000 on Standard) create friction for active teams. Jira Automation rules have no run cap at Standard and above, and the rule builder supports cross-project triggers, JQL conditions, and Slack notifications that Butler cannot match. Teams with complex board automation find Jira's rule engine more capable at comparable or lower per-seat cost.

Questions, answered

## Trello to Jira migration questions

How long does a Trello to Jira migration take?

Most migrations land between two and four weeks for workspaces under 5,000 cards across fewer than 20 boards with no legacy pluginData Custom Fields. Migrations with 500+ cards per board, multi-workspace configurations requiring separate Jira organizations, large attachment libraries, or legacy Custom Field extraction move into four to eight weeks because of API rate-limit handling, per-board project provisioning, and the reconciliation work for multi-member cards and archived cards.

Do Trello Butler automations migrate to Jira?

No. Butler automation rules are Trello-specific configuration stored in a proprietary format that has no automated conversion path to Jira Automation. We document every active Butler rule during discovery (trigger, conditions, actions, run frequency) and deliver a written inventory with recommended Jira Automation equivalents for the customer's admin to rebuild post-migration. Butler run history is not preserved and does not migrate. Power-Up data similarly does not migrate; we provide a Power-Up inventory identifying each active add-on and its Jira or Marketplace alternatives.

What happens to archived cards during migration?

It depends on the destination Jira space type. In a Jira software space, archived cards are not imported at all by the native importer. In a Jira business space, archived cards import as Done status. We detect all archived cards during discovery and present two options: restore them in Trello before migration so they are included in the import, or exclude them from scope and handle them as a separate post-migration project. We recommend the customer review archived cards before migration to determine which are still relevant.

Can we migrate Trello cards with multiple assignees to Jira?

Trello allows unlimited members per card; Jira enforces one assignee per Issue by design. We detect every card with more than one member during discovery and present three options: map the first member only (dropping the rest), map all members to a Jira multi-user picker custom field (requires Premium or a Marketplace app), or create linked sub-tasks with each additional member assigned to their own sub-task. The chosen strategy is applied consistently across all cards before any Jira Issue is created.

What happens to Trello Custom Fields during migration?

Trello Custom Fields created via the core API (available since 2023) migrate to Jira Custom Fields with type-matching. Custom Fields created before 2023 may exist only in card pluginData storage rather than the structured API response, which requires legacy extraction logic. We detect which storage mechanism is in use during discovery and apply the appropriate extraction method. Legacy pluginData extraction is less reliable; we recommend a post-migration manual audit of Custom Field values on a sample of migrated records.

Do card attachments migrate completely?

File attachments download from Trello's S3 storage and upload to Jira during migration. Jira has a 10MB per-file attachment ceiling. Trello Free allows 10MB attachments and Enterprise allows 250MB. Any attachment exceeding 10MB is flagged for the customer's admin to host externally (Confluence, SharePoint, or S3) with a hyperlink inserted into the Jira Issue description. Board-level attachments migrate to the Jira project's description or a linked Confluence page.

Can FlitStack AI migrate Trello Power-Up data and data from third-party integrations?

No. Power-Up data is stored in third-party schemas maintained by each Power-Up developer and is not accessible via the Trello API. We do not migrate Power-Up state, configuration, or history. During discovery we inventory every active Power-Up per board and document its purpose, data type, and recommended Jira or Atlassian Marketplace equivalent so the customer's admin can evaluate replacement options. Any data held exclusively within a Power-Up requires manual export or a direct export from the Power-Up's own interface before migration begins.

## Related migrations

[![](https://flitstack.ai/platforms-trim/jira.webp) Migrate to **Jira** Every source we move into Jira, native options and the checklist. Guide, checklist & sources ](https://flitstack.ai/migrations/pm/jira) [**Jira to Trello** The same pair in reverse](https://flitstack.ai/migrations/pm/jira/to/trello) [**Slack to Jira** Mapping · history · rollback](https://flitstack.ai/migrations/pm/slack/to/jira) [**Notion to Jira** Mapping · history · rollback](https://flitstack.ai/migrations/pm/notion/to/jira) [**ClickUp to Jira** Mapping · history · rollback](https://flitstack.ai/migrations/pm/clickup/to/jira) [**Asana to Jira** Mapping · history · rollback](https://flitstack.ai/migrations/pm/asana/to/jira) [**Wrike to Jira** Mapping · history · rollback](https://flitstack.ai/migrations/pm/wrike/to/jira) [**Redmine to Jira** Mapping · history · rollback](https://flitstack.ai/migrations/pm/redmine/to/jira) [**Trello to Asana** Mapping · history · rollback](https://flitstack.ai/migrations/pm/trello/to/asana) [**Trello to monday Work Management** Mapping · history · rollback](https://flitstack.ai/migrations/pm/trello/to/monday-work-management)

## Sources: official documentation

1. [Import data from a CSV file — Atlassian Support](https://support.atlassian.com/jira-cloud-administration/docs/import-data-from-a-csv-file/)
2. [Link your object schema to a Jira project — Jira Service Management Data Center](https://confluence.atlassian.com/spaces/SERVICEDESKSERVER/pages/1044784360/6.+Link+your+object+schema+to+a+Jira+project)
3. [Importing data from CSV — Administering Jira applications Data Center](https://confluence.atlassian.com/adminjiraserver/importing-data-from-csv-938847533.html)
4. [Working with Custom Fields — Trello Support](https://support.atlassian.com/trello/docs/custom-fields/)
5. [Import data from Trello — Jira Cloud Administration Support](https://support.atlassian.com/jira-cloud-administration/docs/import-data-from-trello)
6. [File size and storage limits on Trello — Web Applications Stack Exchange](https://webapps.stackexchange.com/questions/19209/file-size-and-storage-limits-on-trello)

Get a quote

## Moving from Trello to Jira?

Tell us roughly how many records and objects you have. We scope the mapping and the Jira setup with you, then send a quote.

[Get a quote](https://flitstack.ai/contact)
