Webinar follow-up: Countdown to Cloud Event and Q&A

tgoyette
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
October 11, 2022

Hi Atlassian Community!

Thanks to everyone who joined us for our Countdown to Cloud online event! We were thrilled to see so many of you there! If you missed it, or weren’t able to catch the whole thing, you can view the recording on-demand at any time.

For those just tuning in:

With Server End of Support (EOS) around the corner, we want to make sure you don’t get caught without a plan. That’s why we hosted an online event with Cameron Deatsch, Atlassian’s Chief Revenue Officer, the Atlassian Product Owners of recent migrators Sun Life and Sophos, and Cloud Specialized Solution Partner Valiantys to cover the most important things you need to know to start your journey to cloud.

You had a lot of great questions for us, and we weren’t able to answer all of them during the live session. In this post, we’ll cover the most popular ones and highlight the best resources to find the answers you need.

We’ve broken these out into a few topics, which you can navigate below:

  • Questions about the process of migrating to cloud

  • Questions about cost

  • Questions for Sun Life & Sophos

 


1. Questions about Cloud Migrations

  • We plan to migrate about 25% of our tickets, which account for active projects. Can we retain the other 75% of tickets in an archive as a historical record?

  • Are cloud licenses perpetual in the same way that Atlassian server licenses are?

    • Cloud licenses operate on a subscription model at a monthly or annual cadence.

  • Who should be working with a Solution Partner? How do I know if I need one?

    • While the Atlassian team is here to help you through it, you may feel more confident with even more hands-on support. From assessing cloud, to managing your end-to-end migration, and beyond, Solution Partners provide front-line support with a cloud migration. Our advice is to get a Solutions Partner involved in the process as early as possible so they can help you navigate the change, understand the options that are available, and create a clear migrations strategy. Learn how both Lucid and Sophos successfully made the move to Atlassian Cloud with the help of their indispensable Solution Partners.

  • When migrating Confluence server to Confluence cloud is there a migration assistant that will identify issues with spaces and pages that won't migrate?

  • Will Confluence Data Center continue to exist as a licensing option after 2024?

  • Does cloud have better features for project management (Kanban) that server does not? If so, what is different in cloud?

    • In cloud it’s easier to hold teams accountable with greater visibility into their work, all thanks to the nature of the Atlassian Cloud platform. With cloud only features like Roadmaps, you can help individual teams plan and track their big picture by visualizing their progress in real-time. And for projects requiring cross-functional teams, you have Advanced Roadmaps that lets you strategically plan, map dependencies across teams, and assess total project capacity. 

  • Is it possible to migrate in 3 days??

    • The short answer is, it depends! Just like your instance is like no one else’s, no two migrations are the same. As an example, Lucid Software adopted an aggressive migration strategy and was given a 90-day estimate. They pushed for more and wanted to know if this could be done in 2 weeks! At the end of the day, we were able to get the job done in 30 days. Get in touch with us to discuss your migration plan

  • Will the cloud version be covered by a BAA?

    • Customers who are subject to HIPAA compliance and want to partner with Atlassian must purchase an Enterprise Plan and enter into a Business Associate Agreement (BAA) that covers the applicable products and services. For more information on the signed BAA, please contact us.

      • Learn more about HIPPA and BAA from our compliance resource center.

  • Our on-prem server Confluence is being renewed, when we enable a cloud trial instance for migration will we need to procure additional licenses or will on-prem licenses be transferred automatically to cloud instance?

  • Will our current license not be valid once the server support ends?

    • While your license will be valid in perpetuity, support and bug fixes (maintenance) will no longer be available. This will pose a security risk for you which is why we recommend moving to cloud before the Server EOL. Learn more about Server end of support here.

  • A Jira or Confluence cloud migration is much easier to justify than Bitbucket; what are some talking points that we can bring to our leadership to justify migrating Bitbucket to cloud?

    • Beyond the benefits of adopting a cloud solution, such as not needing to manage servers or product updates, Bitbucket cloud offers several advantages.

      • Secure & Complaint: Being on the Atlassian cloud platform means centralized security and governance across your org and enterprise-grade security like SOC II and encryption at rest.

      • Best-in-class Jira integration: Bitbucket cloud has deep integration with Jira and the Atlassian cloud ecosystem. This means better automation features to save your developers time and increase development visibility across stakeholders, product managers, and other teams that are part of the software development process.

      • Ship quality code: Collaborative code review features to help your developers ship quality code.

      • Integrated CI/CD: Bitbucket Pipelines is Bitbucket’s integrated CI/CD solution that sits alongside your repos. Or you can continue using Bamboo, Jenkins, or other third-party CI tools because Bitbucket cloud works with most major CI/CD providers. Learn more

      • DevSecOps: Native integration with Snyk means that you can view security scan results right within Bitbucket cloud.

2. Questions about cost

  • Do we have to buy a new license for the cloud? And is the pricing for the support/maintenance costs?

    • Yes, our cloud offerings are a separate subscription service. Check out our migration cost calculator to compare server and cloud pricing.

  • What talking points would you suggest we use to rationalize the price increases to leadership at our organizations?

    • Every decision to change our prices is based on increased investments in R&D to help your teams deliver faster, collaborate more efficiently, and leverage analytics for better decision-making. We believe our prices adequately reflect the value our cloud product provide, and there are a number of examples detailing the ROI customers have seen following a migration, such as this recent study by Forrester on the value of a migration to Jira Software Cloud.

    •  

      When you consider the full cost-benefit equation of a migration to cloud, it’s clear that with significant productivity gains, various migration discounts, and reduced costs from no longer having to babysit your infrastructure, cloud’s ROI is well worth its cost.

3. Questions for Sophos and Sun Life

  • Did you have any issues with adopting users/accounts who had independently stood up accounts/tools in the cloud prior to your migration?

    • Sun Life: Although there were a lot of users with pre-existing accounts in the Atlassian Cloud, we did not encounter any issues with granting them access to our Atlassian Cloud.  We use Atlassian Access, so I believe Access helped us manage all users using our email domains.

    • Sophos: This is a classic yes and no. From a tools adoption perspective existing cloud users made the experience easier, we had real experience of the tool usage which was embedded in the team. The bigger challenges came in the form of SSO and corporate policy enforcement. When we moved to the cloud we enforced certain policies which were not enforced on content that had been independently stood up, therefore we had certain friction for some users when they were moved.

      • It is best to treat each independent account as a separate migration project, initially work to set up connectivity between the different products stood up then look to find ways to consolidate them into a single account/instance. It is not straightforward but again a partner will be able to help you plan this similar to a migration to the cloud.

  • What’s been most surprising about life on Cloud?

    • Sun Life: We realized $250k in time savings captured in the first 10 months post migration. In addition, our teams have a 97% Atlassian cloud satisfaction rating, so the entire process has been incredibly welcome within our organization.

  • What has project management looked like for teams on cloud and how is it different than on-premises?

    • Sun Life For enterprise cloud subscriptions, Atlassian released cloud roadmaps for free - so our teams are happy with that as well as the basic roadmap feature. From an enterprise perspective on the Jira line, we value OKR management and delivery management.

    • Sophos: The project management toolsets that are available now are significantly better than they had been on-premises. We found that with our 5,000 seats on Jira that there were a large number of different business practices and ways of approaching project management that existing across our teams. We were able to matchmake the good actors/exceptional users with those who needed help and this allowed us to standardize the our efforts across the platform while engaging with more teams.

  • How did you manage migrating applications to cloud?

    • Sophos: Our cloud migration strategy took about 20 months in total. We spent the first 6 months working with out Solutions Partner to analyze each app that we were using, getting in contact with them to find out what their cloud migration strategy was before we even started our migration. The migration itself took about 14 months and the vast majority of third-party application providers are already well prepared and responsive to this shift to cloud.

  • How much time was there between your Confluence migration and then Jira to cloud?

    • Sun Life: The migrations overlapped between Jira and Confluence. Our Confluence migration is complete, and we still have ongoing Jira Software migrations. I do need to mention that our Confluence instance was not integrated with our on-prem Jira instance, so there wasn’t a need to make sure Jira links migrated correctly.

  • Did all of your plugins have Cloud versions?  If not, how did you navigate that?

    • Sun Life: The Apps for our Jira on-prem instance did have cloud versions.

    • Sophos: Simply no, however this hides a more complicated problem. Not all plugins work the same on the Cloud version, so the planning not only needs to include a check of which applications are not there but also which applications are there but are no longer fit for purpose. The short cut for this is engage a partner and come with a very clear understanding of what you are using the plugin for. In our case this meant that the business users were given a choice, fix the content before or after the migration. One thing you will hear from most people who have gone through this process is that migrating core Atlassian data is fairly simple, it is the add-ons that make it significantly more complicated.

To learn more about how to assess your apps, start with our cloud migration app assessment so you can confidently plan for your Cloud migration.

 


Stay up-to-date with the latest news on cloud and see what is on the horizon with our Cloud Roadmap and find all of the tools you need to get your migration journey underway by exploring the Atlassian Migration Program.

 You can view the recording on-demand at any time and if you still have questions, just get in touch.

0 comments

Comment

Log in or Sign up to comment
TAGS
AUG Leaders

Atlassian Community Events