Atlassian solition partner logo
altassian logo
awards logo

Atlassian gold Partner logo mobile

altassian logo mobile

awards logo mobile

Blog

Migrating from Jira Server to Cloud

Migrating from Jira Server to Cloud

Our Vision for Cloud Migrations

Our general mission is to ensure the smooth transition of your Server product to Atlassian Cloud. Our migration process is as follows:

  • Intuitive: Migrating to Atlassian Cloud is easier than upgrading your Server.
  • Flexible: We support multiple migration modes depending on your project's and configurations' needs.
  • Reliable: We provide real-time updates before, during, and after the migration.
  • Scalable: Everything from a single project to large-scale migrations is transferred securely.

Our long-term vision for Cloud migrations is to help you select the products you want to move, guide you through our migration method, set up and configure your Cloud account, and transition your existing Server product seamlessly. Throughout the process, you'll also be able to track the real-time status of your migration.

6 Steps to Complete Your Cloud Migration;

  • 1. Assessment: Determine if Cloud is right for your team and identify the benefits you can expect after the transition.
  • 2. Planning: Establish your migration strategy and identify the steps to reach Cloud.
  • 3. Preparation: Prepare users, data, and environments for migration
  • 4. Testing: Confirm that your data is transferred correctly and resolve any issues early.
  • 5. Migration: Plan for the final downtime. Data and users are moved to Cloud, and any issues are resolved.
  • 6. Launch: Your teams are trained to use Cloud and explore new features.

Pre-Migration Checklist;

Discover what makes Cloud unique

Cloud brings new advantages, features, and ways of working. We guide you through what sets Cloud apart and help you test the migration process when you're ready.

Examine Cloud security and compliance

Cloud products are designed with security and privacy measures in mind. Atlassian's Cloud security and compliance programs are examined and compared to your organization's requirements.

Learn about Atlassian Access

Atlassian Access provides enterprise-level identity management across your Atlassian Cloud products. Determine if your organization needs Access.

Explore Cloud apps

Visit the Atlassian Marketplace to explore more than 1,000 apps and integrations that extend your products for every use case.

Get a real-time view of future features with a roadmap

New features and improvements are delivered faster in Cloud. See what we're working on and use the Cloud roadmap to help plan your migration.

Migration Tasks;

  • Comparison of Cloud migration methods: Compare different migration methods to see which suits you best.
  • Test migration briefing: We'll summarize the steps for conducting a test migration for Jira or Confluence.
  • Pre-migration checklist: A checklist will be completed to ensure your data is ready before migration.
  • Jira Cloud migration: The above 6-step migration instructions will be applied to complete your migration.

What is Migrated/Not Migrated

 Migrated? Not Migrated?
Jira Software project data

Issue ranking
Epic links
  • Epic name
  • Epic color
  • Epic link
  • Epic status

Issue history (including some custom fields)
  • Epic name
  • Epic color
  • Epic link
  • Epic status
  • Issue ranking
  • Original estimate
  • Remaining estimate
  • Environment
Sprints
Releases
Filters associated with migrated boards
Boards associated with migrated projects

Jira Work Management project data

Project details
  • Name
  • Key
  • Project type
  • Project category
  • Project lead
  • Default assignee
Project roles
Issue types
Issue types schemes
Issue types screen schemes
Workflow schemes
Field configuration schemes
Workflows - fundamental links to the workflow scheme correctly migrated with statuses and transitions
Workflow functions
  • Validators: permissions.
  • Conditions: permissions, permissions granted only to the user who created the issue
  • Post functions: update the resolution field, assign to the current user, assign to the user who created the issue, assign to the team lead
Screen schemes
Screens
Status category
Permission schemes
Issue security

Issue Data

Summary
Description
Issue Type
Status
Priority
Resolution
Labels
Reporter
Assignee
Closed Date
SubTasks
Custom Fields
  • Text
  • Date
  • Number
  • Time
  • Labels
  • Select list(single choice)
  • Select list(multiple choices)
  • Group picker
  • Paragraph
  • Radio button
@mentions
Watchers / Votes
Issue links
Attachments
Comments
Story points
Time spent
Issue history
Issue worklog

Jira Software Boards - boards attached to selected projects will not be migrated during migration)

Boards
  • Name
  • Administrators
  • Filters and permissions
Card settings
  • Columns and statuses
  • Quick filters
  • Swimlanes
  • Sprint permissons
  • Card colors
  • Working days

Active Directory users and groups

Jira Work Management, Jira Software users, and Jira Service Desk agents

Users deleted from the Server will be migrated as "Legacy users". Only deleted users linked to migrated projects will be created in the Cloud.

All groups in active directory

Other types of projects

Archived projects

Project setup
Other Custom Fields
  • Single ve Multi-version picker
  • URL
  • Select list (cascading)
  • Select list (multiple choices)
  • Project picker

Language translations
Workflow functions
  • Validators: Required fields, field changed
  • Conditions: Users in group, project roles, field value, subtask blocking
  • Post Functions: Clear field value, update custom field, copy values from another field, delegate Notification schemes - added to default schemes in Cloud.

Mail Handlers

Project Avatars

Linking to issues or assets that are not migrated

Other Project Types

Jira Service Management Projects

Jira Global Assets and Permissions

Global Permissions
General configuration (time zone, language, etc.)
Dashboards
Cross-project boards
Boards not associated with migrated projects
Filters on non-migrated boards
Confluence links

Users and Groups

JJira Service Management customers - Only Jira Service Management agents will be migrated.

Users and groups from inactive directories - directories must be reactivated to migrate.

Application Data
  • Applications. When migrating from Jira Server to Jira Cloud, application data is not included in the backup. Some applications have export and import features for their data, but you need to check with the app developers or documentation to confirm if this is possible. Your licenses for Atlassian Marketplace apps can be viewed at https://my.atlassian.com
  • Portfolio for Jira is handled in the same way as other server applications.

User Profiles

  • User avatars. Users will need to update their avatars after the migration.
  • Passwords. Unless you've set up SSO, users will need to reset their passwords after the migration.
  • Time zones. Time zone information in the user profile will be lost.

Issue Data

  • Issue key history

Other Issue Types

  • Archived issues

Security

Your data is protected with encryption in transit. Administrative controls like SAML SSO, enforced 2FA, and SCIM are implemented for enterprise-wide protection.

Privacy

Compliance with industry best practices like Privacy Shield and GDPR ensures your and your customers' data privacy.

Compliance Program

Products undergo independent third-party audits, with certifications such as SOC2 and ISO 27001/27018

Reliability

Products are designed for high performance and built on the best core technologies.

Date Milestone What it means
October 29, 2020 October 16, 2020 Customer announcement date Announcement of changes regarding Server and Data Center products to customers
Coming soon
February 2, 2021 End of sale for new licenses and pricing changes

End of new license sales for Server model products and halting development of Server model products. Any quotes generated before this date remain valid until their expiration date.

There will be price increases for renewals and user upgrades to ensure a smooth transition to Cloud and to continue investment in the development of Cloud.

May 1, 2021 End of new app publishing for Server model applications

New apps for Server model will no longer be published on Atlassian Marketplace.

Long-term plans
February 2, 2022 End of upgrades and downgrades Changes to user counts for Server model products or apps will no longer be possible.
February 2, 2023 End of new application sales for existing licenses New app purchases for Server licenses will no longer be possible. Renewals for Server model products will continue until the support end date (February 2, 2024).
February 2, 2024 End of support Support and bug fixes will no longer be available for Server model products and apps, and all renewals will be extended only up to this date.

Summary

The key to a successful migration from Server to Cloud is advanced planning, and the key to good planning is being clear about your short- and long-term goals. You can plan each step of your Cloud migration and begin your Server-to-Cloud journey with our certified expert Atlassian consultants and accurate roadmaps.

Social Media