Browse all docs
Integrations

Migrating from Jira or Trello

9 min read

Migrating from Jira or Trello

Switching tools shouldn’t mean losing years of project history. Loomstack’s migration assistant imports complete projects from Jira and Trello — tasks, comments, attachments, assignees, and statuses included. And if your team can’t switch all at once, two-way sync keeps both tools consistent during the transition.

Before You Start

  • You need Admin rights in Loomstack and in the source tool
  • Imports create new projects; they never overwrite existing Loomstack data
  • Invite your teammates to Loomstack first — the importer matches users by email address, and unmatched users are imported as plain-text names

Importing from Trello

  1. Go to Settings > Integrations > Import
  2. Choose Trello and click Connect Trello Account
  3. Authorize access, then select the boards you want to import
  4. Review the default mapping:
    • Trello lists → Loomstack workflow states
    • Cards → tasks, with descriptions, checklists, labels, and due dates
    • Card comments and attachments → carried over with original timestamps
  5. Click Start Import

A typical board of a few hundred cards imports in under two minutes. You’ll get an in-app notification and an import report listing anything that couldn’t be matched.

Importing from Jira

Jira projects carry more structure, so the importer walks you through field mapping:

  1. Go to Settings > Integrations > Import and choose Jira
  2. Enter your Jira site URL and authenticate with OAuth (Jira Cloud) or a personal access token (Jira Server/Data Center)
  3. Select the projects to import
  4. Map Jira fields to Loomstack fields:
    • Issue types (Story, Bug, Task) → labels or task types
    • Statuses → workflow states — collapse similar states if your Loomstack workflow is simpler
    • Story points, sprints, and custom fields → Loomstack custom fields
  5. Choose whether to import all issues or only issues updated in a recent time range
  6. Click Start Import

Epics become Loomstack task groups, and issue links (blocks/is blocked by) are preserved as task dependencies.

Setting Up Two-Way Sync

If part of your team needs to stay in Jira temporarily:

  1. Go to Settings > Integrations > Jira > Two-Way Sync
  2. Pair a Loomstack project with a Jira project
  3. Choose the sync scope: titles, descriptions, statuses, assignees, and comments
  4. Set the conflict rule — when the same field changes in both tools between syncs, either “Jira wins” or “Loomstack wins”
  5. Click Enable Sync

Changes propagate within about a minute in both directions. Synced tasks show a small link icon; click it to open the Jira twin. Trello two-way sync works the same way but is limited to card title, list/status, due date, and members.

Verifying and Cleaning Up

After the import finishes:

  1. Open the import report and resolve any unmatched users by assigning their tasks to real accounts
  2. Spot-check a handful of tasks against the source tool — comments, attachments, and dates
  3. Archive the source board or set it to read-only to stop the team from splitting updates across tools
  4. Once everyone has moved, disable two-way sync from the same settings screen

Summary

Use the import assistant under Settings > Integrations to bring over full project history from Trello or Jira, mapping statuses and custom fields as you go. For gradual transitions, enable two-way sync with a clear conflict rule, verify the import report, and switch the old tool to read-only so Loomstack becomes the single source of truth.

Was this helpful?