30 March 2028 No new DC Purchases
28 Mar 2029 Licences expire
How Exalate can fill the gaps in your Jira DC to Cloud Migration plan
A lot of Jira DC to Cloud guides stop at “run JCMA.” But your Jira is connected to other tools: other Jira instances, service desks, ServiceNow, automations, reporting. JCMA does not move these connections.
After the migration, you have to set them up again. Plus, some data needs extra care: comments, worklogs, attachments, custom field values, and app fields from tools like Tempo or Insight.
This guide covers that layer, written from the migrations we’ve run.
- How a Jira DC to Cloud migration usually runs, and the step where most plans slip
- How to keep DC and Cloud in sync while you migrate in phases, with no work freeze
- Which data needs extra care, and what arrives with it
- How your connections are rebuilt after JCMA finishes
- Three things that are not yours to solve, and who owns each one
- A week-by-week pre-cutover timeline, starting six weeks out
One of the biggest reasons why I would recommend using Exalate is that you can clean up your data while migrating, and that’s a very interesting option. Especially useful if your Jira has a lot of ‘dirty’ data. The normal approach is to usually clean up before or after migration.
Atlassian Consultant | ACA Group
