Atlassian Cloud Migration with catworkx: 

 

icons8-complete
Standardized and proven!

We ensure that all data is provided in the target environment in the best possible way.

icons8-edit-account
Personal contact

Migrations often have their challenges: As an Atlassian Solution Partner, we support you in all steps for a successful migration of Atlassian products.

icons8-suitcase
Comprehensive consulting

With us, you will not be processed as quickly as possible but will receive comprehensive advice to optimise the migration plan to your needs.

icons8-cash-in-hand
Cost optimization

Before migration, we evaluate which licensing option is best suited for the existing conditions.

icons8-broken-link
Downtime minimization

In migration planning, we keep downtime to a minimum.

icons8-stocks-growth
Scaled for Enterprise

Our enterprise services also support scaled migration projects: We advise you along the entire process.

How to migrate:

We distinguish between complete and hybrid migration - another option is a fresh start. In general, cloud migration should be used as an opportunity to question and improve existing processes. In this way, your system will run more user-friendly and efficiently in the cloud. In a full migration, the goal is to transfer your system to the cloud as faithfully as possible. In hybrid migration, a selective approach is taken and Jira is configured for a fresh start so that it optimally fits your processes.

 

  Full Migration Hybrid Migration Starting from scratch
Description
  • Small Improvements on Self-hosted
  • Only necessary Housekeeping
  • Migration of all projects and spaces
  • Migration of all Apps
  • Deep Housekeeping (Project archiving, Rebuilding processes, Removal of unnecessary fields, schemes & configurations)
  • Migration of selected projects and spaces
  • Migration of selected Apps
  • Evaluation of current processes
  • Rebuild selected projects and spaces on Cloud
  • Configuration of necessary Apps on Cloud
Manual Effort low medium high
License Costs high low low
Migration Costs low high medium
Migration Duration low high high
Pros
  • migrate all content (historical & current)
  • fast way to migrate
  • migrate only important content
  • nice way to migrate (cleaned up system)
  • reduce downtime
  • reevaluate all security permissions
  • new structure for every space
  • no actual migration - no migration errors
  • no downtime (clear cut; per use case)
  • easy way to update business processes
  • reconfigure all security permissions
  • no data migrated (historical or important)
Cons
  • historical (confusing) structure
  • long downtime
  • hold on to (historical) business processes
  • hold on to (historical) security permissions
  • mix of historical and new structure
  • mix of historical and updated business processes
  • high manual effort because of new configurations

Migration Phases

Assessment
  • small effort in Analysis and Assessment
  • Self-hosted instance will be migrated as is
  • long Analysis and Assessment phase
  • all projects and spaces have to be evaluated if they are needed in the Cloud environment
  • all Apps have to be analyzed in usage and Cloud functionalities
  • long Analysis and Assessment phase
  • all projects and spaces have to be evaluated if they are needed in the Cloud environment
  • all Apps have to be analyzed in usage and Cloud functionalities
Planning
  • migration can be planned more flexible
  • planning might take more time for what will be migrated and how the Atlassian Cloud will be used in the future
  • evaluation and planning on how the Cloud could be used in the future takes a lot of time
Preparation
  • small effort in preparation of Server instance
  • no housekeeping tasks need to be completed first
  • high effort in preparation of self-hosted instance
  • all processes which are needed on Cloud have to be configured completely new
Testing
  • more errors could occur because of no big efforts in data preparation
  • test migration might take longer because all of the data will be migrated - the more data the longer it could take
  • more effort in troubleshooting / post-migration tasks
  • errors are minimized with preparation work when less data is in scope for the migration it will take less time
  • troubleshooting will be easier with less data to analyze
  • testing can be done on the fly
  • only newly configured processes need to be tested
  • no real test migration troubleshooting
Migration
  • migration might take longer - the more data the longer it can take to migrate
  • more effort in post-migration tasks
  • when less data is in scope for the migration it will take less time
  • post-migration tasks are minimized with good preparation
  • no actual migration process is needed
  • user can switch easily to the new instance
Handover
  • Handover of live Cloud environment Hyper care for possible requests after migration
  • Handover of live Cloud environment Hyper care for possible requests after migration
  • Handover of live Cloud environment Hyper care for possible requests after migration

Software, that we migrate:

Jira Software
Jira Software Cloud Migration

Jira Cloud Migration includes all the features you use in your server or data center environment. This of course includes your tasks as well as projects, Kanban or Scrum boards, custom fields, filters and much more. If you use extensions and apps, we analyze the migration possibilities of these apps. If the apps do not have a migration path, we try to remedy the situation with other apps or native functions. There is the possibility to optimize existing processes during the migration. This will be determined in the initial assessment.

jira service management
Jira Service Management Migration

Jira Cloud Migration includes all the features you use in your server or data center environment. This of course includes your tasks as well as projects, Kanban or Scrum boards, custom fields, filters and much more. If you use extensions and apps, we analyze the migration possibilities of these apps. If the apps do not have a migration path, we try to remedy the situation with other apps or native functions. There is the possibility to optimize existing processes during the migration. This will be determined in the initial assessment.

mark-gradient-blue-confluence
Confluence Cloud Migration

Confluence cloud migrations are often underestimated. It includes migrations of all your pages to the cloud. Not only must the structure be maintained, but also links between your pages. In addition, there is the functionality of your macros and apps that needs to be verified. During a Confluence migration, we migrate Spaces, Permissions, User Groups, Authorizations, Pages and much more!

bitBucket
Bitbucket Cloud Migration

Migrating Bitbucket to the cloud is usually straightforward. Repositories and projects are transferred from a workspace, and users are moved to the cloud and assigned their licenses through user groups. This ensures that unnecessary users are not licensed. The Bitbucket migration process is similar to Jira migration, but with two main differences. First, the cloud version does not have the Bamboo continuous delivery product. Instead, the integrated Bitbucket Pipelines feature handles CD/CI functionalities. This eliminates the need for separate tools. Second, forked repositories cannot be migrated. Prior to the migration, all open pull requests from forks must be merged to avoid data loss.

Migrate
yourself?

The migration process:

Migration should be well prepared. As a roadmap, we, therefore, use Atlassian's proven migration process, consisting of the following steps:

icons8-support

Pre-assessment

Before the migration starts, we look at the scope of your systems. We look at the number of users, apps and other components that will help make a good decision.

Start Pre-Assessment

icons8-eyebrow

Evaluate

Then, we assess your requirements and decide when cloud migration is right for you. This is also where we analyze your current landscape and start building your migration team.
icons8-education (1)

Plan

Once we have worked out your goal, we can start planning the technical and operational aspects of your migration. Here we jointly select your migration strategy and method and define the project and schedule.

 
icons8-sync

Prepare

As your plan takes shape, we can begin preparing your domain and users for migration to the cloud. During this phase, we'll help you upgrade your product to a supported version and clean up your data and users so everything is ready for migration.

 
icons8-bug

Test

The plan is in place and solid? Then we can start testing.  This is an important step to ensure your production migration goes smoothly. At this point, we prepare any training materials your teams may need to get used to life in the cloud.

 
icons8-upload-to-cloud

Migrate

Once the tests are complete and everything is running smoothly, we work together to pick a date for the migration. We make sure that your systems are offline at a convenient time and for as short a time as possible.

 
icons8-deploy (1)

Launch

Your cloud products are online and ready to go. We help you get started and get your teams on board. We provide them with guides to help you work in your cloud sites and get your teams started.

 
Platinum+Solution+Partner+Enterpise+clear+big-01

Atlassian Enterprise Platinum Solution Partner

Solution Partners provide the services, implementation, consulting, and unique solutions that help our users create what's next.

Our experts hold the following certificates and accolades: 

Your point of contact:

 
Hans Zimmermann:

IT System Administrator

8
Specialization: 
Cloud migration, ITSM