Troubleshoot create a migration from your cloud organization
This page describes some troubleshooting information for creating a Jira and Confluence migration from your cloud organization.
Before you run the migration
Pre-migration checks
Pre-migration checks are a mandatory step of every migration. They make sure that your configuration is correct and that the data can be migrated to Cloud.
Common problems shown by checks
Here are common problems shown by checks and steps you can take to solve them.
Problems | Fixes |
|---|---|
| The server may ‘no longer’ exist causing checks not to run. For example, upgrading your license may cause your server ID to change and invalidate previous connections to cloud. | Connect to cloud again and ensure that you select the last server on the list (if there are duplicates), and attempt to run the pre-migration checks again. |
You may encounter some errors when using the migration API. | |
It’s possible that your cloud site is unavailable for migration. | Here are the reasons and fixes: Reason 1: Your sandbox has been deleted. Fix:
Reason 2: Your cloud site couldn’t be found or your Jira Cloud subscription has been deactivated due to inactivity.
|
If your Jira Server site is highly customized, you may face additional issues when migrating. For example, if you have any required field with a null value the migration will fail because this is not supported on your Cloud site. | We recommend cleaning up your instance data before migrating. |
Get support
If you encounter any issues or have questions, you can reach out to our team by leaving a comment under your request to join the Early Access Program.