For those of you who attended AtlasCamp in September, located in the wonderful city of Vienna, you may remember a slide that looked something like this in the Keynote.
This screen is part of a Migration Assistant that is available today for Confluence Server & Data Center customers, and coming soon for Jira Server & Data Center.
What is a Migration Assistant?
A migration assistant is an app built by Atlassian that allows a customer to plan and execute their migration from Server or Data Center to Cloud.
App Assessments
Early in planning, we recommend customers perform an app assessment. An app assessment is an exercise to take inventory of the apps that are installed an enabled on an instance and decide if they would like to migrate that app to cloud.
With the migration assistants, we present data to help inform their decision.
This includes:
- cloud version availability available today
- usage information coming soon
- feature comparison between server and cloud versions coming soon
- migration path from server to cloud versions coming soon
You may be wondering how this information gets compiled and presented to customers through the migration assistant. If you’re not, you should be because it influences a significant decision the customer is making about taking your app with them to cloud.
Cloud version availability is collected from the Atlassian Marketplace. We match the app key for all apps that are installed and enabled in a server or data center instance to an app key from the marketplace. If that app key has a cloud version the customer is presented with a :check_mark:. Everything else is presented with a :cross_mark:.
Pro Tip #1
If you have separate app listings for your cloud version and your server / dc versions (which is recommended for other reasons), you can link your listings to signal that a cloud version is available in the Migration Assistant.
To link your listing:
- Create a new version for your server / dc app that is compatible with cloud but not installable.
- Select “Provide another URL” in app file location.
- Add the URL for your cloud app in the “Learn more URL” field.
- Delete server compatible applications.
- Update your build number.
See below:
Usage information will be collected from the customer’s instance. Specifically, apps with macros will have macro usage counts displayed next to the app. Apps that don’t use macros will have an indicator that usage couldn’t be calculated because the app doesn’t use macros. If you have suggestions for us on how to determine usage for apps that don’t use macros please comment below.
Feature comparison between server and cloud versions information and migration path from server to cloud versions will display links to your documentation (when you have a cloud version available).
If you haven’t provided URLs for either of the above, the link will direct customers to your support page in Atlassian Marketplace.
Pro Tip #2
Create documentation describing the differences between the server and cloud versions of your app and a migration path from server to cloud.
We don’t have field available in Marketplace for those URLs, yet.
Please provide them to us via AMKTHELP so that we can display them in the Migrations Assistant while we build the fields in Marketplace.