• Products
  • Documentation
  • Resources

Assess and migrate apps with the Cloud Migration Assistant

When should I assess my apps?

Ready to go?

  • For a simplified, step-by-step overview of app assessment and migration, see the assess and audit apps and integrations section on the Server to cloud migration guide.

  • For Atlassian's full, simplified guide on cloud migration, see the Server to cloud migration guide.

  • App migration is now available with the EAP (Early Access Program)
    On 13 May 2021, we released the Early Access Program (EAP) for app migration using the Jira Cloud Migration Assistant (JCMA). This means that you can now migrate your apps to cloud.

    In summary you can:

    • choose apps to migrate from server to cloud

    • give consent to migrate your app data to cloud

    • view migration preflight checks about users and groups, projects and apps

    • perform the app migration

    • view logs and reports about the migration

    If you are interested in joining the app migrations EAP, you can begin here by completing the EAP survey.

     

 

Assessing your apps is part of the migration process and ideally is done as part of the Assess phase.

Migration-phases-planning-guides.001.jpeg

If you need assistance knowing which stage you're in, there are a few specific scenarios listed below based on migration stages that could be relevant for you.

Scenario

Recommended solution

I need to assess my apps but haven't yet planned the rest of my cloud migration

You can find an overview of migration planning in the Server to cloud migration guide.

I want to learn more about the strategic benefits of an audit prior to migrating my apps

We recommend reviewing the Audit apps for your migration to cloud guide, before starting your app assessment.

My migration is mostly complete and assessing my apps is one of the last steps

We recommend checking our product pre-migration checklists to make sure you're completely ready. These are the Confluence pre-migration checklist, and the Jira pre-migration checklist.

My migration is ready to test, or I want to check out a cloud instance

You may be interested in a Cloud migration trials for server and Data Center customers. These trials are designed with on-premise customers in mind, and are longer than a normal cloud trial, to give you time to test properly.  

Familiarizing yourself with the assessment table

The assess your apps screen can be complex if you're new to migrating apps, so we've listed a breakdown (by column) of some of the terms and functions used in the table. 

Status

You assign a status to each app, once you've made a decision on how to proceed. There are four statuses that can be assigned to an app. Statuses can be changed, you can move back in the app assessment flow to reassign a status if you change your mind. 

Status options

Description

No decision made 

Each app in the table will start in this state. If you're unsure or haven't yet made a decision, you can leave an app in this state until you're ready.

If you leave an app in this state and continue, the assistant won't move it forward for migration.

Needed in cloud

You can use this status when you know you need to migrate an app and its data to a cloud instance. 

Not needed in cloud

You can use this status, if an app doesn't need to be migrated to your cloud instance. This could be because:

  • it's already installed on an existing cloud site 

  • there is native functionality in cloud that replaces the need for the app, or 

  • your end users are not engaging with the app on server, and you see no need for it to be migrated.   

During your audit, you should get an idea from your end-users if an app is useful and necessary. You can look at columns in the table such as appears on and viewed by, to get an idea of what the usage is.

Use alternative

Not every Marketplace Partner (previously known as app vendor) with a server app available on the Atlassian Marketplace has created a cloud version, or your requirements around a particular functionality may shift. In these cases, you may wish to use a different app in cloud, than the one you have installed on your server. 

Assigning this status to an app will allow you to select an alternative app later in the flow.

Exists in cloud

This column will show you if the Marketplace Partner has built a cloud version of an app installed on your server. You'll see either  (yes),  (no) or  (not sure). The text below each symbol gives you further information.

Status types

Description

View differences

Takes you to the relevant Marketplace Partner page so you can review the differences between the cloud and server versions of the app.

Contact vendor

There is no information available, and you need to speak to the Marketplace Partner.

 

Not sure

The migration tool is unable to see any information from the Marketplace Partner about whether a cloud app exists. You should contact the Marketplace Partner directly to find out.

 

Appears on (Confluence only)

This column shows you how many pages the macros of a given app appears on in the last 30 days. It does not appear in the Jira Cloud Migration Assistant.

Status types

Description

Disabled

The app is installed, but disabled in your server instance. 

Not applicable

The app is enabled but doesn't have macros, and so is not applicable to this column. It doesn't mean the app isn't used.

It doesn't mean the app isn't used.

x pages

The app macro appears on this many pages in the last 30 days.

Viewed by (Confluence only)

This column shows you how many views the macros of a given app appears on in the last 30 days. It does not appear in the Jira Cloud Migration Assistant.

Status types

Description

Disabled

The app is installed, but disabled in your server instance. 

Not applicable

The app is enabled but doesn't have macros, and so is not applicable to this column. It doesn't mean the app isn't used.

It doesn't mean the app isn't used.

x pages

This many users have viewed the macros of this app in the last 30 days.

 

Can be migrated

This column will show you if there is current migration pathway supplied by the Marketplace Partner for this app. You'll see either  (yes),  (no) or  (not sure). The text below each symbol gives you further information.

 

 

screenshot_automated-path-linked

The app can be migrated to the respective cloud app using the Jira Cloud Migration Assistant.

The Automated path label links you to the respective Marketplace Partner’s documentation to read about their available automated migration path.

For EAP, a link that says Sign up for EAP will appear below the Automated path label. This link takes you to the EAP sign-up form.

screenshot_automated-path-signup-link

The app can be migrated to the respective cloud app using the Jira Cloud Migration Assistant.
The Automated path label is disabled because the Marketplace Partner has not provided links to their migration documentation.

screenshot-automated-path-unlinked

The app can be migrated to the respective cloud app using the Jira Cloud Migration Assistant.
The Automated path label is disabled because the Marketplace Partner has not provided links to their migration documentation.

screenshot_view-path

The app has an equivalent cloud app.
However you cannot (at the time of app assessement) use the Jira Cloud Migration Assistant to migrate to the Marketplace Partner’s cloud app.
The View Path label links customers to the Marketplace Partner migration strategy to migrate you app data without using the Jira Cloud Migration Assistant.

screenshot_upgrade-path

The app has an equivalent cloud app.
However, you are using a server app version that is not compatible with the Jira Cloud Migration Assistant (JCMA).

Recommended action:

  • You will need to upgrade to a version of the server app that supports JCMA.

  • When you have upgraded to a supported server app version, and redo this app assessment. At that point, the Upgrade app status of this column should change to Automated path.

screenshot_contact-vendor

The app has an equivalent cloud app.
However, the Marketplace Partner probably has not yet built a migration path to migrate your app data to their cloud app.
Note: This status can also appear if the Jira Cloud Migration Assistant is unable to retrieve information from the server app for technical reasons.

The Contact vendor label links you to the support section of the Marketplace Partner listing.

screenshot_red-cross

The app does not have an equivalent cloud app. This means that you cannot migrate your app data to cloud for this app, until the Marketplace Partner builds a cloud app and migration path.

 

Assessing your apps 

For a simplified, step-by-step overview of app assessment and migration, see the assess and audit apps and integrations section on the Server to cloud migration guide.

The app assessment table helps you step through the assessment process to streamline your decision-making process. You should assess your apps before testing and running your migration.

1. Migration assistant home

You begin assessing your apps by clicking into the Assess your apps card.

screenshot_JCMA-migration-assistant-home-screen

 

2. Assess your apps table

The app assessment table will populate with the apps you have installed on your server instance. This may take some time, depending on how many apps you have installed. 

Work your way through the installed apps, checking the criteria, and assigning a status to make a decision about each app. 

Note: The Confluence and Jira cloud migration assistants look slightly different, as they are measuring slightly different things. 

You can download a CSV file of this table at any time, to show stakeholders or get sign-off on a business plan, to work offline, or to create a checklist of tasks.

 

Confluence cloud migration assistant - Assess your apps table

confluence-assess-your-apps-screen

 

Jira cloud migration assistant - Assess your apps screen

screenshot_assess-your-apps-screen

3. Choose app alternatives

 If you have assigned Use alternative to any of your apps, you will now be prompted to select the alternatives you need.

If you no longer need an app on your cloud instance, go back a screen and change the status to Not needed in cloud. This removes the app from the list of apps that will require an alternative.

screenshot_select-app-alternatives

4. Connect your cloud site

You can link your chosen cloud instance at this step. There are four ways to do this:

screenshot-connect-to-cloud-prepare-your-apps-flow

5. Install your apps

You can now move forward with installing the apps that you’ve chosen for your cloud site.

screenshot_install-your-apps

Once you're ready, you can click Done.  

You currently need to contact the Marketplace Partner (app vendor) to migrate your app data, as app data migration is not yet supported by the migration assistant.

Last modified on Aug 17, 2021
Cached at 11:29 AM on Sep 20, 2021 |

Additional Help