Migration Guide

How to Migrate From Jira: The Complete Guide

What moves, what breaks, and how long it takes.
Not a vague “up to 80% savings” pitch. The actual shape of the job.

What a Jira Migration Actually Involves

Most guides on this topic cover one thing: getting issues out of Jira and into whatever tool you’re switching to. That part’s mechanical, honestly the easiest piece to get right. What trips people up is everything sitting on top of the issue data.

  • The data itself. Issues, comments, attachments, users, history. Exports fine in most cases. Rarely where the pain is.
  • Apps and add-ons. Zephyr/Xray, Tempo, Assets/Insight, eazyBI, and a long tail of others. Most of these keep their data outside Jira’s own tables, with no standard export path for any of it.
  • Automation and business logic. ScriptRunner scripts, Automation for Jira rules, workflow validators and post-functions. None of it comes along. Somebody has to figure out what it’s doing before it can be rebuilt.
  • People and process. Where things live, what a status means, how a ticket moves through the team. Almost no migration guide mentions this one, but it’s usually what decides whether the switch sticks or people quietly drift back to old habits.

This guide covers all four. What to expect, what you’ll lose along the way, and how to plan for it instead of finding out mid-migration.

The Step-by-Step Process

Most importer tools stop at “connect and import” and call it done. We’d add two steps to that: an actual pilot before you commit, and a window where both systems run at once before you shut the old one off. Skip either one and you find out about problems from your team, instead of from a test run.

1. Connect & Export

Pull issues, comments, attachments, and users out of Jira. Check what your export actually captures before you assume it’s complete. Some fields and history only come through if you’ve got the right settings turned on.

2. Map Fields & Workflows

Match custom fields, issue types, and workflow statuses to their new equivalents. This is where you find out which parts of your setup don’t map cleanly onto anything else.

3. Dry-Run on One Project

Pick one live project and migrate it. Not a sample dataset someone built for testing. Whatever’s odd about your specific instance shows up here, while it’s still cheap to fix.

4. Validate

Check the counts. Spot-check history and attachments. Get the team that actually owns that project to sign off before you touch anything else.

5. Cutover

Migrate the remaining projects in batches, on a schedule your teams actually know about ahead of time. Tell people the exact day Jira access goes read-only.

6. Parallel-Run Before Decommission

Leave Jira up in read-only mode for a while (two to four weeks is typical) before you cancel any licenses. Off-the-shelf importers don’t build this in, but it’s cheap insurance.

What Doesn’t Survive the Move

Every migration loses something along the way. The question is whether you find that out before you set a cutover date or after. This is condensed from our full breakdown on leavingjira.com. Worth reading in full if any of these apply to you.

App & Add-On Data

Zephyr/Xray, Tempo, Assets/Insight, eazyBI. These keep their data in their own proprietary structures, outside Jira’s tables. None of them offer a clean export path.

Custom Logic

ScriptRunner Groovy scripts, JMWE extensions, Automation for Jira rules. None of it migrates. Someone has to reverse-engineer what it does before it can be rebuilt anywhere else.

Reporting Structures

Advanced Roadmaps hierarchies, JSM portals with SLAs, cross-project Gantt plans. Most tools don’t have a real equivalent for these. Budget for redesigning the process, not just re-pointing it.

Everything Quietly Pointing at Jira

Confluence macros embedding live issues, commit messages that reference old ticket keys, Slack or Teams integrations, SSO and directory sync. Most people forget these exist until one of them breaks.

Read the Full Breakdown →

How Long It Actually Takes

Most vendor guides skip this question, or answer it with one number regardless of the situation. In our experience, timeline tracks complexity a lot more than it tracks headcount. How many projects you’re moving. How much custom logic is layered in. How many apps you’re carrying along.

Complexity Tier What That Looks Like Typical Timeline
SimpleSmall team, few projects, minimal automation or add-onsDays to about a week
ModerateMultiple projects, a handful of apps, some custom workflow logicOne to three weeks
ComplexMany projects, heavy automation, portfolio/reporting apps, tight integrationsSeveral weeks to a couple of months

Treat these as a starting point, not a quote. The sizing calculator below gets you closer to a number for your setup.

What It Costs. Run Your Own Numbers.

We could throw a “save up to X%” figure at you like everyone else does. It wouldn’t mean much without knowing your team size, your current Atlassian bill, and how custom your setup is. Our sizing calculator asks for those specifics and estimates cost and migration complexity from them. No signup, nothing sent to a server.

Run Your Numbers →

On-Prem & Regulated-Environment Migrations

Air-gapped networks, classified programs, compliance requirements. If any of that applies, the plan above needs adjusting, and it’s not something most migration guides touch. If you’re in defense, aerospace, government, finance, or healthcare, start with what we’ve already written on what these environments need.

On-Premise ALM Tools: What Defense Contractors Need to Know →

Frequently Asked Questions

What happens to data residency during migration?
Depends how you deploy. Cloud region of your choice, self-hosted on your own infrastructure, or fully air-gapped if that’s what you need. Schedule a call and we’ll talk through what your environment requires.
What happens to our attachments?
They come along with their parent issues. We’d still spot-check a sample after the dry-run step, before you commit to the full cutover. It’s a cheap check and it catches most surprises.
Can we run Jira and GForge in parallel during the switch?
We’d recommend it. Keep Jira around in read-only mode for a few weeks after cutover, so your team has something to fall back on while they get used to the new system.
Do we lose our issue history?
The core stuff (comments, status changes, timestamps) travels with the issue. Anything living inside a third-party Marketplace app is the exception. See what doesn’t survive migration for specifics.
Can you migrate our data from Jira?
Yes. We can migrate your Jira issues, Confluence pages, and Bitbucket repos to GForge. Schedule a call to discuss your specific situation.

Ready to Plan Your Migration?

Ready to Leave Jira Behind?