New research: 1,000 enterprise leaders on the AI decision-confidence gap.

Download the report →

How to migrate to the new Jira integration

This article is for organization admins who already use TheyDo's previous Jira integration. It explains why you need to move to the new integration, what to prepare, and how the guided migration carries your existing setup across.

Why you need to migrate

Atlassian is retiring Connect, the technology behind TheyDo's original Jira integration. Once it's retired, the previous integration stops working: TheyDo will no longer sync with your Jira site after December 10, 2026.

The new integration is faster and more reliable. It connects through Atlassian's standard sign-in (OAuth), so the access TheyDo gets is managed in Jira, by the permissions of the account you connect with. Your existing content in TheyDo is preserved.

In Settings > Integrations, the previous integration now shows as Jira (Legacy), with a banner reminding you of the deadline.

Before you start

Get 3 things ready before you sign in. When you open the new Jira integration, TheyDo shows them in a Migrating your existing Jira setup panel. You can click Copy link to share that page with whoever manages your Jira accounts.

  1. A dedicated service account. Every change TheyDo makes in Jira is made as the account you connect with, and the connection stops working if that account loses access. Ask your Jira admin to create a standard Atlassian user that isn't tied to a person, for example jira-theydo-integration@yourcompany.com, and save its password in your team's password manager.
  2. Access to your existing projects. The panel lists every Jira project that currently has linked solutions or mapped statuses. Click Copy list and make sure the service account can access all of them, with permission to browse, create, edit and transition issues.
  3. The same Jira site. You need to connect the same Jira site as your current integration. TheyDo checks this automatically, and a different site can't be migrated.

Note: Use a normal Atlassian user account, not Atlassian's special "service account" type: that type can't complete the sign-in. A one-time MFA prompt is fine, but policies that force frequent reauthentication can interrupt syncing.

Migrate your existing setup

  1. Go to Settings > Integrations and open the new Jira integration.
  2. Click Sign in to Jira, sign in with the service account and approve access for the same Jira site.
  3. When TheyDo asks how to proceed, choose Migrate my existing setup. It shows how many projects and linked solutions it will bring across.
  4. Select projects: every project with links or mapped statuses is selected by default. Deselect any you don't want to migrate, then click Continue.
  5. Validate: click Validate to check that the service account can access every selected project. If a project shows No access, grant access in Jira and click Re-run, or click Deselect to leave it out.
  6. Migrate: once access is confirmed on every project, click Migrate.

Watch the migration in video

The migration copies your status mappings and then your links one by one, in the background. You can leave the page and come back: a banner on the Jira settings page shows the progress. While it runs, your previous connection's settings are read-only.

Review the migration report

When the migration finishes, you'll see a report with the number of projects tracked, status mappings carried over, links migrated and links skipped.

  • If everything moved, your previous connection is retired: it no longer syncs, and everything now runs through the new integration.
  • If some links were skipped, they keep syncing through your previous connection for now. The What still needs attention section groups them by problem, with the fix for each group. Fix the issue (usually project access in Jira), then click Re-run migration.

Click Download report for a CSV of everything that was skipped, or Copy summary to share the result with your team. Any link that still can't move needs to be relinked by hand on the solution.

When you're done, click Continue configuring to review your projects, workspaces and status mappings. See Jira integration.

Tip: Once your previous connection is retired, you can remove it from Settings > Integrations > Jira (Legacy).

Prefer to start from scratch?

If you'd rather choose projects and mappings yourself, pick Set up from scratch instead of migrating. Your previous connection stops syncing and all its solution links are removed. Each solution keeps a record of the Jira issue it was linked to, so you can relink it by hand. This can't be undone.

Need help?

Your Customer Success Manager can walk through the migration with you. Have the service account ready before the session, so the time goes into the migration itself.

Further reading