Migrating Atlassian Tools Hosting Environments and Things to Consider

19 April 2018 | Atlassian

It’s good practice to have a partner help you with recommendations and to perform an assessment of your environment in order to find the best way to improve your experience.

Furthermore, Server and Cloud versions are now developed separately and their versions are not correlated so it’s good to evaluate your requirements and the functionality you may find in each one.

But before talking about migrating your instances, it’s critical to understand the differences and benefits of choosing Cloud, Server, or Data Center and what scenarios may drive your decision behind choosing a platform.

Atlassian for Cloud Pain Points:

  • Limited number of users on an instance (2000 users max).
  • You can’t control your environment, access database, make complex integrations and you can’t track your disk space usage.
  • You can’t make customizations and custom plugins to support your business requirements.
  • No custom URL.

Atlassian for Server Pain Points:

  • Cost of infrastructure.
  • Highly skilled professionals required to administer your instances.
  • Difficulty assessing size and infrastructure capacity of associated servers and utilization demand.
  • Large effort to set up your environment, apps, and managing users.
  • Your team is responsible for updating/licensing OS/DB/Atlassian Products/Java/disk space/ memory.

Food for thought when migrating from Server to Cloud, and vice versa

Cloud to Server Migration Scenario:

  • You started in Cloud and now that people know how to use it, they want to go further and use the potential that the server platform offers in terms of apps, customization, and control. In Server instances you are able to create your own integration using API which is more flexible than Cloud. Some examples include integrations with ERP and CRM systems; and custom add-ons.
  • Your business requirements show that you need a specific add-on or feature that you can only have in a server scenario.

You have to take into account the apps that you have installed in your environment. Many of them aren’t available for Cloud. They may have different license options and many features may vary because of other restrictions.

Server to Cloud Migration Scenario:

  • Your organization is tired of maintaining their own infrastructure.
  • There are limited available resources or skilled professionals to help administer a server instance.
  • A server environment was originally adopted and it’s now apparent control over the hardware is unnecessary,  and there aren’t any specific/complex integrations or customization requirements needed to match business requirements. The out-of-the-box cloud version would be enough to fulfill their needs.

If these resonate with you, chances are a migration to a cloud environment would suffice and allow your resources to focus on the business, rather than maintaining the business infrastructure.

Server to Data Center Migration Scenario:

If your Atlassian environment is crucial for your business goals, perhaps you want to invest in a Data Center platform. Multiple clusters and load balancers provide sites with High Availability and Disaster recovery to avoid system outages. It’s good to evaluate these scenarios when you are scaling Atlassian tools in your company.

  • With the growing adoption of Atlassian tools, more users, integrations, and add-ons are needed. This expansion can cause performance reduction or service interruption due to high traffic of users and operations.
  • Atlassian tools are becoming mission critical and you need to have flexibility and predictability while scaling your Atlassian environment.
  • You work with distributed teams that need to access code repositories and they are having troubles with the clone times that slow their productivity.

Investing in Data Center allows you to manage and scale with Atlassian as the business continues to evolve. If your organization is adopting DevOps across multiple departments, IT and non-IT, this can be another factor to consider in scaling and planning for support of Atlassian tools within a Data Center environment.

Other migration highlights:

  • Before migrating, we recommend having the server in the latest version available.
  • There are features in the Cloud version that are not released for server yet (and might not ever be).
  • Remember that in server you must link your Atlassian tools after migrating from Cloud.
  • Manage your licenses as they work differently to Cloud. You need to control your user tier and renew your licenses to keep your environment updated.

How can e-Core help you?

It’s good to have an application support team to help you upgrade and maintain your Atlassian environment. We can help you understand your needs and provide guidance on what the best options are in order to achieve your business goals.

We perform health checks, analyze your environment and provide recommendations on sizing and infrastructure capacity of associated servers and apps that you can use in your environment.

Whether you have a team to support your Atlassian environment or want e-Core to host and manage your environment, we are ready to help you as your Atlassian Platinum Enterprise Solution Partner.

Read more:

Atlassian Open Forum NYC 2018

e-Core hosted the Atlassian Open Forum NYC at the Executive Conference Center on Broadway in Times Square. The forum was focused on taking ITSM to the next level with Jira Service Desk and other Atlassian tools.

The Atlassian Approach to ITSM

We live in a world where customer service is of the utmost importance. From startups to large traditional companies, all are facing internal and external service requests and the management of these requests have since evolved. Solution-oriented IT tools are in demand to provide a fast and reliable way to deliver products and services to the marketplace and have a seamless method of supporting them. Adoption of these tools is falling outside of your typical customer service team and being used by multiple departments within an organization to manage workloads.  

Share This