Windows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallOutdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchFor a Jira Server or Data Center to Cloud migration, apps and integrations do not all move unchanged. The Jira Cloud Migration Assistant (JCMA) assesses Marketplace apps, but app-data migration depends on each vendor’s path; external connections may need to be rebuilt or reconfigured. Treat app compatibility, app-data transfer, and integration setup as separate migration tasks.
What does JCMA assess for Marketplace apps?
Use JCMA’s Assess your apps screen to review installed apps, Cloud availability, migration path, stage, and vendor information. For each one, decide whether it is still needed, should be replaced, or can be retired. Where usage information is available, consider it alongside input from the people who rely on the app.
As an Amazon Associate I earn from qualifying purchases.
A Cloud version being available does not by itself mean that the app’s data will migrate. Atlassian says app-data migration depends on the Marketplace partner providing a path. For apps that hold important or regulated information, review the partner’s Cloud privacy, security, legal, and compliance material: JCMA’s app assessment is not a security assessment of the data migration.
How to read the migration-path labels
| JCMA status or path | What it means | What to do |
|---|---|---|
| Automated path | The partner has provided a path JCMA can use. Atlassian distinguishes stage 2 apps, which have demonstrated high migration success rates, from stage 1 apps, whose success rates are unknown or demonstrated to be low. | Review the vendor’s instructions and migration scope. Atlassian advises contacting the vendor if a stage 1 app-data migration fails. |
| Install-only | Install the Cloud app; its relevant data is embedded in Jira core data, such as projects or issues, and migrates with that data. | Confirm the Cloud app is installed and test the app’s features and records after migration. |
| View path | A Cloud app exists, but the partner’s migration route is outside JCMA. | Follow the partner’s separate instructions and schedule its migration accordingly. |
| Upgrade app | The installed Server or Data Center app version is not supported by JCMA. | Upgrade the source app to a supported version, then assess it again. |
| Contact vendor | A Cloud equivalent may exist without a published migration path, or JCMA may have failed to retrieve the status. | Ask the partner to confirm availability, migration steps, timing, and support. |
| No | No equivalent Cloud app is available through the indicated path. | Decide whether to replace or retire the functionality, or ask the partner about its plans. Do not assume the existing app’s data can be moved into an unavailable Cloud app. |
Atlassian’s app path definitions explain these distinctions. Its public path list may not include every app, and Atlassian says it does not verify all partner-provided feature or migration claims. Check current partner instructions; if an app is not listed, contact its vendor.
#1 Best Overall
Which app data migrates, and when?
In a JCMA plan, choosing All includes app data only for apps marked Needed in cloud that also have a vendor-provided migration path. Choosing None omits app data. The app partner performs the app-data migration, and administrators must review and consent to each applicable partner agreement so the partner can access data for migration. The JCMA data-selection guidance describes the selection.
Do not treat a successful Jira core migration as proof that every app-owned record, configuration, or historical item has transferred. Check the vendor’s documented migration scope and validate the items that matter to your workflows.
Rank #2
- Used Book in Good Condition
Run app-data migration separately
Separate Marketplace app-data migration is available starting with JCMA 1.12.46, according to Atlassian’s current guidance. It can be useful when the app’s data needs a different schedule from Jira core data, but it has prerequisites:
Do these 3 things before closing this tab:
1Fix the driver behind crashes, sound loss and screen glitches2Clear out junk files and repair common Windows errors3Scan for outdated or missing drivers - takes under a minute- The relevant project data must already have been migrated within the preceding 14 days.
- The selected project migration may show success or incomplete, but the required projects must have migrated successfully.
- Do not change the migrated project data until the app-data-only migration is complete.
Atlassian lists app custom fields, workflow rules, configuration, and other app-owned entities as examples of data handled by this feature. See its separate app-data migration instructions for the current procedure and requirements.
What happens to custom or internally developed apps?
A Server or Data Center app is not automatically a Cloud app. Atlassian says Cloud apps are installed through Marketplace; Cloud does not provide an option to upload an app file, including for an app built in-house or designed for Server or Data Center. If custom functionality must continue, plan a Cloud-compatible implementation with the people who own and maintain it. The appropriate approach depends on the app’s architecture and current Atlassian developer guidance.
What happens to Atlassian product links?
- Jira Cloud and Confluence Cloud on the same site: Atlassian says these products are already connected through application links.
- Atlassian Cloud apps on different sites: Configure application links manually.
- Cloud connected to Data Center that remains on-premises: Atlassian documents application tunnels with tunneled app links. Its stated benefit is a secure connection without opening the private network to incoming connections, which ordinary app links require.
- Government Cloud connected to Data Center: Atlassian’s post-migration guide says application tunnels are unavailable; the instances need direct access to each other, and OAuth 2.0 application links are required instead of OAuth 1.0.
See Atlassian’s post-migration integration guidance for configuration details. These connection rules concern the documented Server or Data Center to Cloud migration context; other migration types can differ.
What should happen to third-party and custom integrations?
Inventory integrations before cutover so an owner can test each connection in Cloud. Record its purpose, authentication method, endpoint, network path, dependencies on Marketplace apps, and whether it stores Jira issue, project, or comment IDs. Those details help identify changes that a simple connectivity check could miss.
One important redesign case is a custom integration that relies on listener interfaces. Atlassian says Jira Cloud does not support configurable listener interfaces and points to webhooks as an event-trigger option for Cloud Jira products. Review the Cloud-compatible approach for each integration rather than assuming a Server or Data Center listener will continue to work. See Atlassian’s Jira Data Center and Cloud administration differences.
Also test connections that depend on the old Jira base URL, permissions, user identity, app data, or numeric Jira entity IDs. Issue, project, and comment IDs change in a Server-to-Cloud migration, so a third-party system that stored the old IDs may need reconciliation. Atlassian documents a source-instance ID mapping API that may help with post-migration reconciliation, but the endpoint is beta and may change or be removed. Treat it as a possible one-off aid, not a permanent integration contract; see the ID mapping API notes.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.How should you choose whether to keep, replace, or retire an app?
| Choice | Compare before deciding | Practical consequence |
|---|---|---|
| Keep the app | Cloud feature coverage, data needed, vendor migration path and support, and security or compliance posture. | A Cloud equivalent may not match the Server or Data Center app, and having a migration path does not by itself establish functional parity. |
| Replace it | Whether another app or native Cloud capability meets the workflow, and how any required data or process will move. | Plan the replacement as a functional change, not merely an app installation. |
| Retire it | Whether users still need the functionality and whether records or configuration must be retained elsewhere. | Mark obsolete apps as not needed in Cloud and resolve any data-retention needs before cutover. |
For retained apps, get the migration scope, schedule, support expectations, and any feature differences from the partner early enough to act on them.
Quick Recap
Migration sequence: apps and integrations
- Inventory: List installed Marketplace apps and external integrations. Confirm owners and whether each remains necessary.
- Assess in JCMA: Review Cloud availability and migration-path status for every app. Decide whether to keep, replace, or retire it.
- Confirm vendor requirements: For each retained app, check migration scope, feature differences, security and compliance needs, timing, and support. Upgrade a source app if JCMA requires it, then reassess.
- Plan app data: Choose whether eligible app data moves with Jira core data or in a separate run. For a separate run, meet the JCMA version and project-timing requirements above, and leave migrated project data unchanged until the run finishes.
- Configure connections: Set up cross-site Atlassian application links and Cloud-to-Data-Center connections as needed. Rework listener-based integrations for a Cloud-compatible event trigger, such as a webhook where appropriate.
- Validate in Cloud: Check app features and records, links, webhook delivery, identity and permissions, and any external system’s stored Jira IDs. Use vendor instructions and migration reports to verify each app’s documented scope rather than assuming parity.
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.
