Here are the most common questions about the Cloud-hosted migration assistant.

• Setup

• Migration

• Data residency

• Data security

• Audit and log tracking

• Billing and payment

• Marketplace app migrations

Setup

1. Where can I download the Migration Connector app?
   The app is available in Atlassian Marketplace. View Migration Connector on Atlassian Marketplace

2. How long does it take to run the Migration Connector app to copy my data to the cloud? Can I use my Data Center instance while it is running?
   The duration of data copy depends on your data size and network bandwidth. During the testing phase, you can use your Data Center instance as it is; the app does not impact it. However, if you’re migrating your data incrementally, you’ll need to set your instance data to read-only mode before the final migration. This ensures further changes in the Data Center instance won’t be copied.

3. Is it possible to copy only part of my Data Center database?
   We cannot copy part of the database. We currently copy data in its entirety. It is not possible for customers to specify an exclusion list or copy data only for specific projects.

4. What are the memory/CPU requirements for the Migration Connector app?
   Using the Migration Connector app requires significantly less memory/CPU/resources in comparison to Jira Cloud Migration Assistant. The database is captured using Debezium, an industry-standard tool known for its lightweight nature. For more details, refer to Debezium’s support documentation.

Migration

1. Can we use the Cloud-hosted migration assistant for migrating data in multiple phases?
   Yes, however, there will be downtime during multi-phase migrations.

2. Are cross-project entities supported for migration through Cloud-hosted migration assistant?
   Yes, cross-project data entities are supported. However, some entities can’t be incrementally migrated and need to be migrated entirely. Contact support for the full list of entities supported for incremental migrations.

Data residency

1. Where will my Jira data be stored during and after the migration?
   During migration, your Jira data will be stored in AWS S3 buckets & Atlassian Cloud storage.
   After migration, data resides in the region of its destination cloud site. As part of Atlassian’s data residency offering, you can pin in-scope data to a specific region. Read about data residency

2. How will migration impact our data residency choices?
   Before and after migration, in-scope app data will be hosted in the region you have chosen. During migration, data will be in transit for up to 14 days and may pass through Atlassian cloud environments in the United States. Read how data residency works

3. What happens if I change my data residency region during migration?
   If you change the data residency location of a destination cloud site during migration, the changes will not be applied and the migration will fail.
   To change the data residency location, restart the migration and select the appropriate location.

Data security

1. How is my data protected in transit during migration?
   Any Jira data during migration is encrypted in transit over public networks using TLS 1.2+ with Perfect Forward Secrecy (PFS) to protect it from unauthorized disclosure or modification. Data drives on servers holding migration data use full disk, industry-standard AES-256 encryption at rest.

2. How does Atlassian manage Atlassian employee access to tenant data during and after a migration?
   At Atlassian, we prioritize the security of your data. Only authorized employees with an active support ticket can access a customer instance. Atlassian employees who directly assist with the migration of customer data will be granted access to the customer’s instance. These employees are added as participants on the MOVE ticket, which the customer can also access. Access to the tenant is strictly controlled to ensure only authorized roles have access during and after migrations.
   You can reach out to Atlassian support for assistance.

3. How does Atlassian secure my data as it moves between Atlassian services during migration?
   We use checksum verifications (e.g., multipart upload checksums) along with HTTPS (TLS 1.2+ with PFS), ensuring encryption in transit when it's initially uploaded from Data Center to Atlassian Cloud Services. During migration, all communications between the customer environment and Atlassian’s Cloud Infrastructure occurs over HTTPS (TLS 1.2+ with PFS), ensuring encryption in transit.

4. What happens to temporary copies of data after migration?
   The temporary data copies stored for migration are deleted automatically after 180 days. You can request data deletion sooner by contacting Atlassian support.

5. How does Atlassian monitor outbound traffic?
   We use McAfee MVision CASB to supervise outbound traffic, adding an extra layer of security. This is our standard practice, including our migrations. You also have the option to use McAfee MVision to monitor your own instances via Atlassian Guard. Learn about CASB integrations with Atlassian Access

6. Who can initiate a migration process?
   Only a site admin for the source instance, or an organization admin or site admin for the destination cloud site can initiate a migration.

Audit and log tracking

1. Are there logs that monitor access to Jira migration tickets and their content?
   Yes, all access to customer apps, including Jira migration tickets, is logged for auditing and security purposes. These logs, along with other relevant security logs (ie: AWS CloudTrail), are sent to Splunk and Alert Logic for thorough offsite analysis. Any access triggers an alert, ensuring a detailed record for security and auditing purposes. Note: These logs and alerts are all internal to Atlassian.

Billing and payment

1. Do I have to pay for using the Cloud-hosted migration assistant to migrate my data?
   For the early access program, there are no additional costs associated with using the Cloud-hosted migration assistant.

Marketplace app migrations

1. How are third-party Marketplace apps migrated?
   When you set up your Data Center instance and copy your data to the migration environment, this will include all third-party, Marketplace app data from your selected Data Center site(s). Once copied, support engineers can assist you in migrating third-party app data. Read about what Marketplace app data will be migrated

2. How do third-party Marketplace app migrations work while migrating incrementally?
   Marketplace apps can’t be incrementally migrated and need to be migrated entirely in one go. You can choose to migrate apps as required.