Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Fix the driver behind crashes, sound loss and screen glitches3Repair Windows errors before they cause bigger problemsBefore moving Jira Server or Data Center to Cloud, check more than the Migration Assistant’s green lights. Confirm source and assistant compatibility, user identity and groups, migration-runner permissions, app migration paths, destination settings, data scope, network readiness, and recovery plans. Jira Cloud Migration Assistant (JCMA) runs useful readiness checks and produces reports, but Atlassian says its checks do not cover everything; use them alongside the full pre-migration checklist and guidance from your app vendors.
Start with the source, JCMA version, and network
First establish that the source Jira version is supported by the JCMA version you plan to use. Atlassian recommends updating JCMA to the latest version before migration. Its installation guidance changes over time, so verify the current compatibility and installation instructions against your actual Jira version rather than relying on remembered version thresholds. See Atlassian’s update or installation guidance.
As an Amazon Associate I earn from qualifying purchases.
- Check the source Jira version and installed JCMA version; update the assistant before planning and testing the move.
- If the source is behind a firewall, confirm that required Atlassian IP addresses and domains are allowlisted.
- Check available source resources and free disk space, and identify scheduled jobs that could compete with migration activity.
- Test network health close to the migration window. Egress security controls can slow uploads, so include them in throughput planning.
Confirm who will migrate and how identities will match
User identity problems can create duplicate accounts or prevent users from being matched as intended. Synchronize external directories and review the email addresses JCMA will use. Atlassian says invalid or duplicate email addresses are not supported for migration to Cloud. If an identity provider can identify one person by both a UPN and a separate email address, align its identifier with the email JCMA uses to reduce duplicate-account risk.
- Review user and customer email addresses for invalid values and duplicates.
- Synchronize external directories before migration and verify that the expected accounts are present.
- Compare source and destination group names. Resolve collisions unless merging those groups is intentional.
- Check that users’ groups can access the same relevant Jira products in Cloud as they do on the source.
Verify migration-runner permissions and access exposure
The account running the migration needs the required administrative access in both environments, plus access to the relevant source data. A permission gap may block migration or leave selected content outside the runner’s reach.
#1 Best Overall
- On the source, grant the migration runner Jira System administrator permission.
- On the destination, ensure the runner exists on the Cloud site and has the Cloud organization admin role.
- Give the runner access to the Jira home export directory used for temporary files.
- If migrating boards and filters, verify Browse project permission for every selected project.
- Review project and filter sharing for anonymous or public access. Atlassian says public entities are changed to logged-in users during migration; remove unintended anonymous access before the move.
Assess every Marketplace app separately
Do not assume that installing an app’s Cloud version also moves its data. Use JCMA to assess installed apps, then confirm the specific migration route and requirements with each vendor. The app assessment is not a security review of the app’s data handling; review the Cloud app against your security, legal, and regulatory requirements.
| App assessment result or route | What to confirm |
|---|---|
| Automated migration through JCMA | Whether your installed source app version is compatible, what data is included, and what setup or validation the vendor requires. |
| Install-only | Whether app configuration or data must be recreated, exported, or moved by another route. |
| Partner-built migration path | Who performs the migration, which data is covered, and the vendor’s prerequisites. |
| Upgrade or contact-vendor requirement | Whether an app upgrade or vendor-assisted process is needed before migrating. |
| No suitable Cloud equivalent or unclear path | What functionality or data will not carry over and how the team will handle that gap. |
JCMA’s app assessment can report availability and migration-path information, but those statuses do not establish that an app meets your organization’s data-handling requirements. See Atlassian’s app assessment guidance and ask each vendor about its own process.
Rank #2
Check source integrity, custom fields, and capacity
Run Atlassian’s recommended source integrity checks and resolve the issues they identify. Confirm required fields have values, and inspect custom-field descriptions for HTML or JavaScript that may be incompatible. The checklist also includes SQL checks for specific conditions; use a query only with the database and environment it targets, and have a Jira administrator validate it before running it.
Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minutePC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11- Review source capacity and free disk space for temporary and migration-related files.
- Check Cloud storage limits and, where applicable, character and Assets entity limits.
- Identify unnecessary scheduled jobs or other resource-intensive tasks that could affect migration performance.
- Review any relevant Cloud plan limits before deciding which projects and data to move.
Prepare the Cloud destination
Review the target site before selecting migration scope. Check that it has the Jira apps or products users’ groups rely on; differences can affect access. Atlassian recommends matching the source and Cloud language because language differences can affect field migration. Also review storage, plan limits, and identity or security settings, including Atlassian Guard configuration where applicable.
If the Cloud site already contains data, account for it in the migration plan. Jira migration adds data to Cloud rather than deleting or overwriting existing data. Repeated migrations may link identical configuration items, and Jira entity IDs change in Cloud after migration. Atlassian described configuration-duplication resolution as early access for a limited customer group in the reviewed guidance, so do not assume the tools are available to every site. Details are in the data-selection guidance and configuration-duplication guidance.
Run checks and use the reports as part of readiness review
JCMA checks common readiness conditions, including destination app installation, valid and unique user or customer emails, and user or storage limits. Its check categories cover system; users and groups; customers; projects; cross-project boards and filters; Advanced Roadmaps plans; Marketplace apps and vendor checks; and Assets. Expand each check for remediation guidance and review the pre-migration report for items that will migrate, items needing attention, and summaries. For the current workflow, see Atlassian’s instructions for running checks and reviewing a migration.
Rank #4
Atlassian recommends running checks at least a few days before the migration date. That leaves time to make changes and validate them, and may reduce check time on migration day. Successful eligible results are cached for 30 days, after which those checks run again. This cache is separate from JCMA’s migration-data retention: migration data is stored for 14 days from the day a migration is created, according to Atlassian’s JCMA overview.
Recommended Free Tools
Back up, test, and match the production plan to the test
- Back up the source. Keep a recoverable backup before migration work.
- Back up the Cloud site if it already has data. This is important because migration adds data rather than replacing existing site data.
- Run a test migration. Use it to validate scope, results, app-specific steps, and the remediation of issues surfaced by checks.
- Use the same JCMA version for production that you used for the test. If the assistant changes afterward, reassess and test the relevant changes before production.
- Review the final pre-migration report and operational plan. Make sure the team understands what is migrating, what needs attention, and how the migration window is coordinated.
Choose full, staged, or selective migration deliberately
JCMA supports full and selective migration. Compare plans by what they include and how the work will be sequenced; do not assume an app or configuration migrates identically under every plan.
Best Value
- Used Book in Good Condition
| Planning dimension | Questions to resolve |
|---|---|
| Scope | Which projects, users, groups, attachments, boards, filters, plans, and app data are included? |
| Sequence and downtime | Can users, groups, or attachments be migrated in advance to reduce downtime? What work must happen in the main window? |
| Existing destination data | What is already on the Cloud site, and how will you verify additions and any repeated configuration items? |
| Apps | What route does each vendor support, and what validation or manual work is required? |
| Validation | Which reports, user checks, project checks, and app-specific validations will establish that the chosen scope arrived as intended? |
Atlassian’s selection guidance also explains repeated-migration behavior and changed Cloud entity IDs. Build that into any downstream process that relies on Jira IDs, links, or integrations.
Keep the checklist’s priority labels intact
Atlassian’s pre-migration checklist distinguishes mandatory, recommended, and optional tasks. Those labels matter: a recommended preparation is not automatically a hard technical prerequisite, and an optional item should not be represented as mandatory. Review the live checklist for the label attached to each task, then prioritize blockers, access and identity risks, app-specific requirements, and actions needed to protect existing data.
JCMA releases, supported Jira versions, app migration routes, Cloud plan limits, and check behavior can change. Reconfirm the live guidance and the limits of the actual source and destination when you assemble the migration plan.
Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Clear out junk files and repair common Windows errorsFree Scan →Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
