Skip to main content
Skip table of contents

Jira Data Center → Jira Cloud Migration Checklist

Jira Data Center will reach the end of support in 2029. While this may feel distant, organizations using DC should begin planning now.

image-20251209-123424.png

This page provides a clear, practical roadmap to help you migrate from Data Center to Cloud with confidence.

Core Phases of Jira DC → Cloud Migration

  1. Check Projects, Users, and Data

  • Identify active vs. inactive projects.

  • Decide what to migrate, archive, or delete.

👉 See Atlassian guide: What to do before migration

  1. Review Installed Apps

  • Check which DC apps have Cloud versions.

  • Identify apps requiring replacement or manual data transfer.

👉 Explore Cloud alternatives if your DC apps are not available in Cloud

A powerful alternative to many Data Center–only apps is Issue History for Jira by SaaSJet. It provides a full timeline of all changes in your Jira tasks — who changed what, when it happened, and which fields were updated — and works almost identically in both DC and Cloud, so you avoid post-migration surprises.

You can test it now in your DC instance and continue using it in Cloud without relearning. It also offers export, restore deleted tasks, and undo options, making it a smart replacement for apps like Recycle Bin for Jira (DC-only).

  1. Identify DC-Specific Customizations

  • Scripts, custom fields that Cloud doesn't support.

  • Plan for replacements.

  1. Clean Up User Accounts

  • Ensure users have unique, valid emails.

  • Remove duplicates and deactivated accounts.

  1. Choose a Migration Style

  • Move all at once (faster but requires downtime), or piece by piece (slower but safer).

  1. Set a Timeline

  • Select cleanup, testing, final move, and user updates dates.

  1. Assign Roles

Determine who manages apps, users, data checks, and communication.

  1. Set Up Your Cloud Site

  • Get a free Cloud trial.

Note: Atlassian offers a Cloud Migration Trial for Data Center and Server customers with active or expired licenses. The trial lasts for the remainder of the DC subscription (or 60 days if expired), and matches user counts up to 20,000. It’s designed specifically to help companies evaluate and prepare their move to Cloud.

👉 Claim your free trial

  1. Plan App Migration

  • Contact vendors for migration instructions.

  • Schedule time for manual exports if required.

👉 Audit all Marketplace apps before migration

  1. Install or Update Jira Cloud Migration Assistant (JCMA)

  • Always run the latest version.

👉 Guide: How to update or install JCMA

  1. Check Your Jira Health

  • Ensure that your system is updated and working well.

  1. Clean Up and Back Up

  • Archive or delete old data.

  • Always make a copy of everything first.

  1. Fix Any Problems Connected with Users

  • Check for incorrect emails or duplicate accounts.

  1. Review Permissions

  • Ensure that you have enough Cloud licenses and admin rights.

  1. Optional: Pre-migrate Users or Attachments (reduces final migration downtime)

  2. Set Up Cloud Apps

  • Install Cloud versions of your apps and allow permission to move data.

  1. Run a Test Migration

  • Migrate 1–2 non-critical projects.

  • Measure duration, note errors.

  1. Check if Everything Works Correctly

  • Look at tasks, users, boards, and filters.

  • Ask a few team members to test things.

  1. Refine the Final Plan

  • Adjust timeline.

  • Resolve blockers.

  • Set the final migration date.

  1. Run Final Checks

  • Check JCMA to make sure it is all correct.

  1. Migrate to Cloud

  • Start the migration in JCMA.

  1. Validate Data

  • After migration completes, verify the following: task counts, users & groups, boards & filters, and attachments.

  1. Go Live

  • Share the new Cloud URL.

  • Disable or lock the old Jira instance.

If you need help or have questions about Issue History for Jira app migration from Data Center to Cloud, please contact SaaSJet Support or email us at support@saasjet.atlassian.net.

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.