PC 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 & 11Outdated 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 automatically or behave exactly as they did before. The Jira Cloud Migration Assistant (JCMA) assesses Marketplace apps and can migrate app data only when an app is marked “Needed in cloud” and has a vendor-provided migration path. Other apps may need a separate vendor process, an upgrade, replacement, or retirement. Integrations may need new links, credentials, endpoints, or Cloud-compatible implementations.
What carries over—and what does not?
JCMA helps administrators assess apps and select Jira and app data for migration, but it does not guarantee that every installed app, app-owned record, or outside connection will transfer unchanged. The path depends on the individual app and its vendor. Atlassian Support says that app-data migration is highly dependent on Marketplace partners, which must provide a path for moving app data to Cloud. Atlassian’s app-assessment guidance explains how to review those paths.
This guidance concerns Server or Data Center to Cloud migrations. Cloud-to-Cloud consolidations, Government Cloud, and other migration methods can have different requirements. For any particular app, confirm its current migration scope and support arrangements with its vendor; a Cloud listing alone does not establish that its data or features will transfer.
How do Marketplace apps migrate?
Use JCMA’s Assess your apps screen to review each installed Data Center app’s Cloud availability, migration path, migration stage, and vendor information. Decide whether the app is still needed, whether a Cloud alternative fits the workflow, or whether the app can be retired. If app data is important, contact the vendor early about its migration instructions, timing, support, and security and compliance requirements.
#1 Best Overall
JCMA’s path labels describe different situations; they are not interchangeable. Atlassian’s definitions of app migration paths include:
| JCMA path or status | What it means for planning |
|---|---|
| Automated path | The partner has supplied a path that 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. For a failed stage 1 app-data migration, Atlassian advises contacting the vendor. |
| Install-only | Install the Cloud app. Its data is embedded in Jira core data, such as projects or issues, and moves with that core data rather than through a separate app-data migration path. |
| View path | A Cloud app is available, but its partner directs customers to a migration route outside JCMA. |
| Upgrade app | The installed Server or Data Center app version is not supported by JCMA. Upgrade the source app to a supported version and assess it again. |
| Contact vendor | A Cloud equivalent may exist without a migration path, or JCMA may have failed to retrieve the status. Ask the partner for current instructions. |
| No | No equivalent Cloud app is available. The app’s data cannot be migrated to that app unless the partner builds a Cloud app and migration path. |
“Cloud available” and “data migrates” are separate questions: an app may be installable in Cloud while its data requires another process or cannot be transferred. Atlassian’s public path lists may not include every app, and Atlassian says it does not verify all partner-provided feature or migration claims. Use the vendor’s current instructions, and contact the vendor if an app is not listed. JCMA’s assessment is not a security assessment of app-data migration; review the partner’s Cloud privacy, security, legal, and regulatory information when the app handles critical data.
Rank #2
- Used Book in Good Condition
How does app-owned data move?
In JCMA’s migration plan, All means app data for apps marked Needed in cloud that have a vendor-provided migration path; None excludes app data. The selection is therefore conditional, not a promise to transfer data for every installed app. See Atlassian’s guidance on choosing Jira data to migrate. Administrators must review and consent to each applicable partner agreement so the partner can access data for migration.
A successful Jira core migration does not by itself prove that every app-owned entity, configuration, or historical record has moved. Compare the result with the vendor’s documented scope and validate the records and features the business relies on.
Separate app-data migration
JCMA supports migrating Marketplace app data separately from Jira core data starting with JCMA 1.12.46, according to Atlassian’s separate app-data migration guidance. This can separate the app-data run from the core-data run, but it has specific prerequisites:
- The relevant project data must have been migrated within the preceding 14 days.
- The selected project migration can have a success or incomplete status, but the required projects must have migrated successfully.
- Do not edit the migrated project data until the app-data-only migration has finished.
Atlassian names app custom fields, workflow rules, configuration, and other app-owned entities as examples of data this feature handles. Confirm the exact scope for the app with its vendor.
What happens to custom or internally developed apps?
A Server or Data Center app binary is not automatically a Cloud app. Atlassian says Cloud apps are installed through Marketplace; Cloud does not support uploading an app file, including for an app built in-house or designed for Server or Data Center. If internally developed functionality is still required, plan a Cloud-compatible implementation with the relevant developer guidance and architecture in mind.
What happens to Atlassian application links?
The required setup depends on where the connected products are hosted. Atlassian’s post-migration integration guidance describes these cases:
| Connection | What to expect |
|---|---|
| Jira Cloud and Confluence Cloud on the same site | They are already connected through application links. |
| Atlassian Cloud apps on different sites | Configure application links manually. |
| Cloud app and Data Center instance that remains on-premises | Atlassian documents application tunnels with tunneled app links. The stated benefit is a secure connection without opening the private network for incoming connections, which ordinary app links require. |
| Atlassian Government Cloud and Data Center | The cited 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. |
What changes for third-party and custom integrations?
Check integrations against Jira Cloud’s capabilities rather than assuming a Server or Data Center mechanism still works. Atlassian says Jira Cloud does not support configuring listener interfaces and points to webhooks for event-triggered connections. An integration that depended on listeners may need to be redesigned around webhooks or another Cloud-supported method. See Atlassian’s comparison of Jira Data Center and Cloud administration.
Also identify integrations that depend on the old Jira base URL, permissions, user identity, Marketplace app data, network routes, or numeric Jira entity IDs. Issue, project, and comment IDs change during a Server-to-Cloud migration, so an external service that stores those IDs may need reconciliation. Atlassian documents a source-instance ID mapping API for post-migration reconciliation, but the endpoint is beta and may change or be removed; it should not be treated as a permanent integration contract. See Atlassian’s notes on the ID mapping API.
Build an integration inventory
Before cutover, record each integration’s owner, purpose, authentication method, endpoint, stored Jira IDs, and dependencies. Note whether it uses a Marketplace app, listener, webhook, application link, or private network route. This makes it possible to assign a Cloud compatibility check and a post-migration owner to every connection.
Quick Recap
How should you plan the migration?
- Inventory what is installed and connected. Ask users and system owners which apps and integrations are still needed; check usage information where available.
- Classify each Marketplace app in JCMA. Record its Cloud availability and migration path, then decide whether to retain it, replace it, or mark it as not needed in Cloud.
- Confirm the retained app’s scope with its vendor. Review feature differences, data coverage, security and compliance requirements, timing, and support arrangements.
- Resolve source-app prerequisites. If JCMA reports an unsupported app version, upgrade it and assess again. Install Cloud versions and provide applicable partner consent for data migration.
- Choose the app-data schedule. Decide whether eligible app data moves with core data or in a separate run; if separate, follow the JCMA version, project-timing, and no-edit requirements described above.
- Plan reconnection and redesign work. Configure links required by the hosting topology, replace listener-dependent triggers with a Cloud-compatible method, and check credentials, URLs, permissions, and network access.
- Validate against the vendor’s migration scope. Check important app features and records, application links, webhook delivery, identity and permissions, and any external system’s stored Jira IDs. Use vendor instructions and migration reports to confirm what completed.
Which migration choices need a decision?
| Decision | Factors to compare | Why it matters |
|---|---|---|
| Keep, replace, or retire a Marketplace app | Cloud feature coverage, actual usage, required data, security posture, vendor support, and migration path | A Cloud equivalent may differ from the Server or Data Center app; functional fit and data-migration feasibility are separate questions. |
| Migrate app data with core data or separately | JCMA version, project migration timing, vendor path, test schedule, and whether project data can remain unchanged during a separate run | A separate run offers scheduling flexibility but has documented prerequisites. |
| Connect Atlassian products | Same Cloud site, different Cloud sites, or Cloud-to-Data-Center topology; network exposure and authentication requirements | Some connections are already linked; others require configuration. Government Cloud has distinct constraints. |
| Adapt an external integration | Listener versus webhook, old IDs versus Cloud IDs, Cloud API and authentication support, and vendor ownership | Some Server mechanisms and identifiers do not carry forward unchanged. |
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.
The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →
