Assessing and migrating apps with the Cloud Migration Assistant

On this page

Still need help?

The Atlassian Community is here for you.

Ask the community

When should I assess my apps?

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


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.

ScenarioRecommended solution
I need to assess my apps but haven't yet planned the rest of my cloud migrationYou can find an overview of migration planning in the Plan your cloud migration page.
I want to learn more about the strategic benefits of an audit prior to migrating my appsWe 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 instanceYou may be interested in an Extended cloud 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 table can be complex if you're new to migrating apps, so the following expand section is a breakdown (by column) of some of the terms and functions used in the table. 


Click here to expand...

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. 

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 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 vendor has built a cloud version of an app installed on your server. You'll see either (tick) (yes), (error) (no) or (question) (not sure). The text below each symbol gives you further information.

View differences: will take you to the vendors 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 vendor.

(question) Not sure: the migration tool is unable to see any information from the vendor about whether a cloud app exists. You should contact your vendor 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.

Disabled: the app is installed, but disabled in your server instance. 

Not applicable: the app is enabled, but is not an app that has macros, and is not applicable to this column.

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.

Disabled: the app is installed, but disabled in your server instance. 

Not applicable: the app is enabled, but is not an app that has macros, and is not applicable to this column.

x users: 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 vendor for this app. You'll see either (tick) (yes), (error) (no) or (question) (not sure). The text below each symbol gives you further information.

See pathway: This will take you to the relevant vendor page to read about the migration pathway.

(question) Not sure: the migration tool is unable to see any information from the vendor about whether a migration pathway exists. You should contact your vendor to find out.

Contact vendor: means there is no information available, and you need to ask the vendor.

Assessing your apps 

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 and install apps card.


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


Jira cloud migration assistant - Assess your apps table

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.



4. Connect your cloud site

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



5. Install your apps

The assessment stage of your apps is now complete. You can now move forward with preparing your apps for migration.


Once you're ready, you can click Install app to begin the app migration process.

Last modified on Jun 22, 2020

Was this helpful?

Yes
No
Provide feedback about this article
Powered by Confluence and Scroll Viewport.