If you missed our recent webinar, ‘Is Your Organization Atlassian Cloud Ready?’, and are interested in learning more about the benefits of using or migrating to Atlassian Cloud, we have a replay of the webinar for you to watch here.
In addition, we’ve also posted an in-depth recap of the question and answer portion of the webinar that you can take a look at here.
Also, if you’ll be attending Summit in Las Vegas March 31 – April 2, 2020, we will be there! So please come stop by and say hi. We’ll be at Booth #1337.
If you’re interested in the webinar but would rather just get to certain portions of the discussion, we’re also including this post which you can use to jump to whichever section you have questions about.
Webinar Agenda Sections
- Coyote Creek’s Atlassian Experience
- Why Atlassian Cloud?
- Atlassian Cloud vs. Server (and Data Center)
- Are you Atlassian Cloud Ready
- Atlassian Cloud Costs
- Atlassian Access
- Atlassian Migration Types
- Cloud Optimization
Coyote Creek’s Atlassian Experience
We’ve found more and more IT teams using the Atlassian stack, and as a result, their business’ demands are changing. IT is demanding higher availability and service level agreements, and we’re also seeing a lot of infosec and compliance requirements.
In addition, many of our clients are terminating self-hosted services, not just with Atlassian but in the environment in general, and are facing cloud mandates from their CIO or CTO. In response to this evolution, Atlassian’s cloud capacity and capability has increased.
Why Atlassian Cloud?
Every organization will have their own unique reasons for switching, but here some of the recurring reasons we hear from our clients.
Quick Start – it’s the fastest way to get set up and running in minutes.
Cost Savings – on your hardware storage, maintenance, and staff to support.
Automatic Updates – Atlassian will perform these for you as new versions/features are available.
Remote Access – You can securely access your instance from anywhere in the world.
Security – Another feature handled by Atlassian for you. We’ll go over that later.
Some of the recognizable customers who have either started with or still currently use Atlassian Cloud include AirBNB, Spotify, Zoom, Visa, Costco, Hertz, Delta, LG and Lowes. 90% of Atlassian customers start with cloud because of how easy it is to get up and running. Later on down the road, depending on their needs, they may move to Data Center.
Atlassian Cloud vs. Server (and Data Center)
Now we’re going to review the critical differences between Atlassian’s Cloud and Server/Data Center products.
Deployment & Admin – Atlassian handles this for you in Cloud. In Server, you will be responsible for your deployment and administration.
Upgrades – Again, Atlassian handles this automatically for you in Cloud. In Server, you’d have to arrange to upgrade your instance and features manually and you have control over when and how those upgrades happen.
User Management – In the Cloud, a new layer called “Organizations” lets you assign rights and access centrally to all your Atlassian applications. You also have Access which provides some more security capabilities such as SSO (single sign on). If you’re on Server, you’re going to designate the rights, product to product for each user. Your SSO would be through Crowd.
Scalability & Extensibility
Mobile Apps – With Cloud, you get out of the box iOS and Android apps. There are apps available as well for Server, but you will need to either be in Confluence 6.8 or Jira 8.3 to use these.
Marketplace Apps – Most of the same apps in the Atlassian marketplace are available in both Cloud and Server. In Cloud you will get some default integrations to things like Slack and Dropbox, which would need to be manually set up in Server.
APIs – Available in both Cloud and Server but in Cloud, you would go through Atlassian Connect for these.
User Limit – The high range for Cloud right now is 5,000 but you can go as high as 10,000 with the early access program. If you’re interested in that, please let us know. We can help you with that. In Server, there isn’t a defined limit but if you’re in the 1,000 range, it’s time to consider upgrading to Data Center which is Server at scale.
Products – With Server, you have Jira Software, Core, Service Desk, Portfolio, Confluence, Bitbucket, Bamboo, Fisheye, Crucible, and Crowd. On Cloud, you have Jira Software, Core, Service Desk, Portfolio, Confluence, Bitbucket, Trello, OpsGenie and Access.
Hosting and Security
Security – Atlassian handles all the security, reliability and compliance issues for you. On Server, you must handle this all yourself but Atlassian does provide documentation to help you navigate these issues.
Hosting – Atlassian hosts cloud in six regions: US East, US West, Ireland, Germany, Sydney, and Singapore because many countries have particular requirements for their hosting environments. With Server, or course, you host on your own servers.
Reliability – Atlassian offers up to 99.9% uptime reliability SLA with their premium plan. With Server, you are responsible for your own uptime and if you’re looking for a reliability standard, you will be better off upgrading to Data Center.
Compliance – Atlassian carries numerous third party audit certifications including SOC2, ISO27001/28018, PCI DSS v3.2, SAQ A and more, for Cloud. For Server, you are responsible for your compliance.
Pricing and Licensing
Pricing – On Cloud, you have the option of both monthly and annual subscriptions. With Server, it is a perpetual license and an annual payment for the first year. In year two, you will pay 50% of your license fee for maintenance.
Plans – On Cloud, you get a limited number of users and storage with the free plan. With the standard plan you get more users and up to 50GB of storage. With premium, you get a 99.9% uptime SLA, unlimited storage and 24/7 premium support. With Server, there are no plans.
Academic/Community/Classroom Discounts – available on both Cloud and Server.
Site Name (URL) – With Cloud, your URL is what you choose and will look like “example.atlassian.net”. On Server, you host your products under any domain you control.
Languages – Cloud currently is offering about two dozen languages and will continue to add to that. In Server, you would download language packs for Confluence and select your default language in Jira Server.
Backups – Cloud offers daily backups that are kept for 30 days and offline backups are available every 48 hours with a 7 day retention. With Server, of course you would be responsible for scheduling and maintaining your own backups.
IP Allow List – With Cloud, Bitbucket premium allows you lockdown access to users for certain IP addresses but this is not available yet for Jira and Confluence. With Server you control access.
DB Direct Access – Not available for Cloud, although Cloud does have extensive APIs. Server, however, does allow you direct access to the database.
Atlassian Cloud Ready
Users: 1-500 users is recommended for Cloud. 500-5000 users also allowed with Cloud but we recommend caution here. If you have over 5,000 users, Data Center is recommended.
*NOTE: Your number of users is an important consideration, but it isn’t the only consideration. We recommend a thorough analysis of all the factors we discuss here before deciding whether or not to move to the Cloud.
New or Existing Customers: New users are advised to use Cloud first after considering the requirements. Existing customers on Cloud are advised to move to Data Center if more scalability is needed. Server customers are advised to either upgrade to Cloud or Data Center depending on their environment and needs. Data Center customers with less than 5,000 users are advised to consider Cloud.
Products Available on Atlassian Cloud vs Server
Products For Cloud and On-Premise (Server and Data Center): Jira Product Family, Confluence, Bitbucket.
Cloud Only: Trello, OpsGenie, Atlassian Access
On-Premise Only: Bamboo, Fisheye, Crucible, Crowd
Data Residency: but is currently an issue under development.
FedRamp or HIPAA
InfoSec: if you have detailed security requirements for hosting, this might be a blocker.
Customizations and Marketplace Apps
Apps: It is recommended that you have 6 or less apps if you are considering Cloud. 6-18 apps proceed with caution after analysis. If you have more than that, you may not want to consider Cloud because you are unlikely to get the same functionality across all apps. Number of APIs allowed by Atlassian is greater in on-premise vs Cloud.
Atlassian Cloud Costs
You will need to calculate your migration costs. Atlassian has made it very attractive to use Cloud by not having cost directly associated with moving to the Cloud, but it’s important to note that there are other costs you should consider, such as the time and resources it takes to migrate. You can use this Atlassian Cloud Pricing Calculator to help!
Free Trial: For anyone with a current on-premise license, Atlassian is offering a free cloud trial so you can test it to see if it’s a good fit for your organization.
Payment Options: As stated previously, Atlassian Cloud offers both monthly and annual plans.
Plan Options: Free, Standard, and Premium (discussed in a previous section) of course we recommend Premium for the SLA.
App Costs: Don’t forget to factor these into your overall costs for migrating.
Atlassian’s enhanced security features in the Cloud are available through Atlassian Access, which if you’re a current Server customer, this is basically Atlassian Crowd for the Cloud. Through Access, you have access to:
- SAML & SSO (Single Sign On)
- Organization Audit Log
- Enforced 2FA
- User Provisioning
- Organization Insights
- Security Integrations (CASB)
- Active Directory Sync
- API Token Controls
- Atlassian Access Support
Atlassian Migration Types
Type 1: All At Once – You move everything at once. Essentially it’s a backup and restore into the Cloud.
Type 2: Merge – Consolidating multiple Cloud and Server sites to help streamline your operations.
Type 3: Hybrid – This is the most common we see with our clients and involves a migration in stages and keeping some data segregated. Some of our customers find that some of their applications or features aren’t available in the Cloud so they keep some things in their On-premise solution.
Type 4: Other – For enterprise corporations with more complexity involved, they will split off one project on it’s own and merge it with an existing instance. For these scenarios, we recommend using an Atlassian partner who can help with the significant planning that will need to be done.
Be sure to review each of these elements to make sure you’re getting the most out of your Cloud environment.
- Governance plan with user permissions and groups.
- Security best practices through Atlassian Access.
- Data Elements
- APIs & Integrations
- App Curation – make sure users aren’t just installing applications that may have duplicate functionality.
If you’re looking for an expert, white glove approach to your migration, please contact us to set up a consultation today! We’d love to help you through this process and optimize your infrastructure for best practices so that you’ll be up and running on the right foot.
At Coyote Creek, as an Atlassian Platinum Solution Partner, we know it’s the human connection that makes the difference in all that we do.