This page explains how you can prepare to migrate your Jira or Confluence app data from server to Connect.
There are three main steps when migrating your app data:
Here's an overview of the pre-migration setup.
Before app data migration begins, you need to prepare your server app and cloud app.
Implement a listener to enable communication between the server app and the app migration platform. This enables the server app to register with the platform and access the data mapping context to prepare for migration.
Component | Description |
---|---|
Your server app | Your server app that's hosted with Jira or Confluence on a user's server instance |
Jira or Confluence Cloud Migration Assistant (JCMA/CCMA) | Contains all the libraries and functions you'll require to migrate data, and provides a user interface that displays the data to be migrated on a server instance |
App cloud migration library | Used to implement the interfaces to enable communication between your server app and the app migration platform |
Add your migration webhook path to your app's connect descriptor. This sets up the communication between the app migration platform and your cloud app, and enables the platform to notify your cloud app when specific events happen on your server app during migration.
Component | Description |
---|---|
Your cloud app | Your app installed on the cloud site |
Atlassian Connect | The framework that your cloud app uses to interact with the app migration platform and the cloud products, and contains all the endpoints for migration |
During the course of the migration your app will mainly interact with an app migration transfer.
Learn more about app migration transfers
Prepare your cloud app to respond to notifications about specific migration events on the server app. The app migration platform notifies your cloud app when:
This infographic shows an ideal data migration process.
Component | Description |
---|---|
Mappings API | Provides endpoints to retrieve mappings |
App data retrieval API | Provides endpoints to access the exported app data from your server app |
Feedback channel API | Provides endpoints to send information from your cloud app to the server product |
Implement the Status API to send progress and settle the transfer when completed. For more information, see Progress reporting.
See the following pages for instructions on how to:
See the following pages for instructions on how to:
This infographic shows an overview of post-migration.
Configure your cloud app to provide updates about the migration status to the app migration platform. The platform displays the status of migration on your server app in the Cloud Migration Assistant.
Component | Description |
---|---|
Your Jira/Confluence server app | Your server app that's hosted with Jira or Confluence on a user's server instance |
Jira or Confluence Cloud Migration Assistant (JCMA/CCMA) | Contains all the libraries and functions you'll require to migrate data, and provides a user interface that displays the data to be migrated on a server instance |
Status API | Provides the status of your migration to the server product. |
Once you've implemented your migration path, assess its readiness and publish its availability to your customers.
Check out our sample apps and tutorials to learn more about how the App migration platform works, or visit our support page.
For more information about migrating to cloud as a Marketplace Partner, check out our journey to cloud hub in the Partner Portal. Request access to the Partner Portal.
Rate this page: