Today marks the EAP launch of app migrations support in the Jira Cloud Migration Assistant. This is a follow up to the March 17th 2021 EAP release of app migrations in the Confluence Cloud Migration Assistant.
This post outlines the rollout in more detail to give you more specifics on what customers will see during and after EAP, and updated timelines for Marketplace Partners building automated migration paths.
Participation in the Early Access Program requires a user to signup and accept the following terms,
This is captured in the signup step, as will be explained below.
All users (Atlassian Customers, Marketplace Partners and Solution Partners included) who are interested in participating can get involved as follows:
- Signup at http://go.atlassian.com/appmigrationseap - note that this form will capture your requirements across a broad range of Cloud migration requirements and so we will also notify you of any future EAPs that are relevant. IMPORTANT NOTE to app developers participating in EAP - we recommend temporarily advertising the signup link from within your automated migration path documentation to ensure customers are able to join the program and get access to the features. Once we leave EAP, the link can be removed as signup will no longer be required.
- Atlassian will create a Support ticket for each signed up user on getsupport.atlassian.com - The ticket will have the key MOVE-<ticket#>. If you did / do not get a MOVE ticket, or can’t find it, please leave us a comment below and we’ll get in touch with your ticket.
- When the EAP is ready, instructions will be delivered as a comment via each participant’s MOVE ticket - this will typically be,
- A link to documentation on how to run an app migration
- A reminder to update JCMA or CCMA to the latest version to get the feature
- Instructions on how to activate the feature by setting a feature flag in the Jira or Confluence Server / DC admin UI.
- For further help and feedback please comment on your MOVE ticket - the Atlassian Cloud Migrations Platform team will be monitoring the tickets and responding to your questions and if need reach out for details.
The Early Access Program is about gathering early feedback with 50-100 customers who are using a working copy of the software with their own (real) data. We are seeking validation that users understand how to carry out app migrations using the features we’ve built, and that app migrations can be successfully carried out automatically with little to no support intervention.
Following the Early Access Program, the next milestone is what we will refer to as Public Beta. The most significant difference will be that app migrations functionality will be made available by default to all customers. In practise, this means that manual feature flag activations will no longer be required.
In the Public Beta release, you can expect the following:
- Usability improvements - based on participant feedback and data collected in research before and during practical runs during the Early Access Program
- More apps with automated migration support - You can view the overall number of apps that support automated migration paths in JCMA and CCMA by reviewing this dashboard. For each of the gadgets you can find links to see what apps are To Do / In Progress / Done. To get an easy view of which apps are supported on your Jira or Confluence Server / DC setup, simply use the built-in app assessment feature to see whether your app(s) have migration paths and also for links to documentation provided by the app developers
- For Marketplace Partner development teams, Public Beta will feature general availability - Customers will no longer need to signup to EAP terms and interact via MOVE tickets. The functionality to carry out an app migration will be enabled by default for apps that have built and integrated their automated migration path functionality with JCMA and CCMA. We are still keeping this as a “Beta” milestone as we recognise there will still be apps coming onto the market for the first time with newly minted automated migration paths and want them to be able to also enjoy a period of expectation setting with customers that these migration apps and services are still under “Beta” development
- For Marketplace Partners Support teams , when you get an inbound support request about how to run app migrations, you can simply direct the customer to be sure to mark your app as “needed in Cloud” in JCMA / CCMA and install the latest build of your app in their Cloud site. The migration will then automatically take place as per your implementation.
- If all goes to plan, you won’t get support tickets - your automated app migration will be “advertised” to customers in the app assessment feature, and customers who go on to mark your apps as “needed in cloud” will bring your app and any data to Cloud with little effort.
Our current guidance for the App Migrations Public Beta releases are as follows:
- August 2021 for the Jira Cloud Migration Assistant
- September 2021 for the Confluence Cloud Migration Assistant
As per our public roadmap, app migrations is targeting GA for a Q4 2021. To have a smooth journey to Cloud, customers with multiple apps are going to need a majority of their apps supporting an automated migration path and so the significance of the GA milestone will be about having a critical mass of automated app migration support, such that we can now more widely promote app migrations.
It will certainly be a case of, the more the merrier!
If you are an app developer and reading about app migrations for the first time, please check out our getting started guide to building your own automated app migration path for your app and if you need help, you please reach out by submitting an App migration support ticket here .
Great news with the follow Jira APIs having recently been released
- Delete workflow transition rule - Jira Cloud Rest API for connect apps [MIG-454]
- Provide filter id mappings in the App migration platform [MIG-503]
The following Additional migration APIs are on track to be released sometime in May 2021 (please refer to the ticket to confirm whether the API has been released)
Jira Migration APIs
- Repair custom field references [MIG-420]
- Create an API to convert user references stored in JQL to AAID during the migration [MIG-315]
- Automatically migrate remote workflow extensions (Post Functions, Conditions, Validators created by apps) [MIG-310]
- Create a bulk API for importing entity properties [MIG-312]
- Create a bulk API for importing Jira custom fields [MIG-311]
Confluence Migrations APIs
- Custom content objects are not being imported during server to cloud migrations [MIG-288]
- Atlassian Cloud REST API Rate Limiting may impact reliability of app migrations [MIG-305]
Below are some steps Marketplace Partners can take to support customers:
- Publishing an updated version of your server app and signalling CMA compatibility using our Marketplace migrations API’s
- This data is presented to customers using the app assessment user interface to help guide and register their app migration decisions.
- App Data Migration Readiness EAP Guide for Marketplace Partners building automated migration paths that integrate with the Jira Cloud Migration assistant.
If you have any further questions or ideas, please leave us a comment below!