This page explains how you can prepare to migrate your Jira or Confluence app data from server to Forge.
There are two main steps when migrating your Forge 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.
Add your Forge function triggers to your app's manifest.
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.
For every uploaded data (event avi:ecosystem.migration:uploaded:app_data
), your Forge function will need to inform us
that the data got processed. That's done by invoking messageProcessed(transferId: string, messageId: string)
from
the @forge/migrations
module. The transferId
and messageId
are provided in the event payload.
See the following pages for instructions on how to:
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: