Migrate Jira Align from on-premise to the cloud

This article provides an overview of the roles and process when migrating Jira Align from an on-premise instance to the cloud.

On this page:

• Roles involved
• Migration steps

Roles involved

Depending on the method used, one or more individuals and teams may assist with your migration request:

• Jira Align Enterprise Solutions Specialist (ESS), or Solution Architect (SA): Assists with coordination between you and Jira Align Support.
• Jira Align Support: Intakes and manages your migration request through a submitted support ticket.
• Your team: Assists with administration and configuration in Jira Align. Please ensure you have contacts in your organization with administrative privileges ready to perform any requested changes. 

Migration steps

To migrate Jira Align, complete the following steps for pre-migration, migration, and post-migration:

Pre-migration

1. Contact your Enterprise Solutions Strategist (ESS), or Solutions Architect (SA) to review your requirements.
2. Submit a ticket to Jira Align Support. You and your ESS or SA should include the following information:
   1. The desired migration timeline.
   2. Confirm that an Amazon Web Services S3 bucket is acceptable for transferring your Jira Align database backup files. This method is preferred, and recommended by support.
   3. If the migration will be to a multi-tenant or dedicated virtual private cloud (VPC).
   4. If there are any SSO connections that will be required.
   5. If you have the on-premise version of Enterprise Insights (EI) installed, and if EI should be provisioned to a multi-tenant or dedicated virtual private cloud (VPC).
   6. If there are any connectors that must be migrated. If so, include network connectivity requirements including, but not limited to:
      1. The version of Jira being used, Cloud or Data Center.
      2. If there is an IP allowlist or mutual TLS for your Jira site. If so, Jira Align Support will need to provide Jira Align IPs and/or the certificate to enable communication between Jira Align and Jira.
   7. The requested instance URL names for Jira Align Cloud. A support engineer can work with you to create these. 
   8. Confirm that the license dates, site location (e.g. USA, Frankfurt, Sydney), and user counts will remain the same after migration to the cloud.

Migration

1. Prepare your on-premise instance for backups:
   1. Stop the connector Windows service(s) from the Jira Align on-premise web server.
   2. Deactivate the connector(s) from the Jira Align UI.
   3. Stop the website from the Jira Align on-premise web server.
   4. Stop Internet Information Services (IIS) from the Jira Align on-premise web server.
2. Create a database backup and upload it to an AWS S3 bucket (encrypted) provided by Atlassian.
   1. There is only one database per site that is required: the [CUSTOMERNAME] named database that was defined in the on-premise install process.
   2. Native and compressed SQL Server backup files in .bak or .bacpac format are required.
   3. A full database backup file is required.
3. Do not use the on-premise site after the database backup file is generated.
4. The Jira Align infrastructure team will load your database backup file into the Jira Align Cloud instance. We’ll let you know once this is complete.

Post-migration

1. Jira Align Support will activate the manual login page for your cloud instance.
2. You'll be asked to log in as a Jira Align Administrator, and validate the following:
   1. User migration
   2. Project migration
   3. Access to all connectors