Challenges moving to Cloud

What is the best migration path? Well, it kinda depends... In this talk we'll dive into less of the method of migrating the data (we'll still share with your vital resources and apps to help you do that), but instead explore the strategic challenges and opportunities available to you as you embark on building and migrating to a new future in Atlassian Cloud. The best first step is building a solid, strategic map. One that considers where you’ve come from and where you are heading, and adaptive to your organizational architecture and future ways of working. We'll talk about transformational migrations, and introduce a new framework we've developed with our customers & technical account managers to help you navigate these strategic questions.

Presented at Sydney Atlassian User Group - Atlassian Community Event on 6th Dec 2022
https://ace.atlassian.com/events/details/trello-sydney-presents-sydney-user-group-atlassian-december-meetup/

Transcript

1. JASON WONG Principal Product Manager, Atlassian Challenges moving to Cloud
3. ,6"-"
   -6.163 4:%/&: '6,60," .&-#063/&
4. Cloud is the future Elevated IT impact Reallocate infrastructure costs and IT resources to strategic business priorities Accelerated team productivity Win back valuable time for users and admins with Cloud-only functionality Built-in security and compliance Mitigate security and compliance risk with our trusted Atlassian Cloud platform
5. Canva + Atlassian Jira Software Project and issue tracking Jira Service Management High-velocity ITSM Confluence Document collaboration Atlassian Access Security and control for cloud Canva team estimates they are saving over 150 hours each month through Jira automation.
6. Mobile apps keep work moving forward from anywhere
7. Build smarter plans across multiple teams and keep stakeholders informed
8. Atlas Instant insight into what teams are working on, and why
9. Automating work to scale efficiently and allocate resources to what matters most
10. Automating work to scale efficiently and allocate resources to what matters most
11. CLOUD-ONLY BETTER-IN-CLOUD Cloud-only and better-in-cloud integrations reduce context switching
12. Atlassian is A PLATFORM FOR TEAMWORK We help you build a connected enterprise by empowering your teams to work differently, together.
13. How do I get to Cloud? Should I migrate all at once or in phases? Or start fresh in Cloud? Should I migrate by team, product, BU, or instance? Should I re-arrange my footprint? Consolidate or federate? What about multi- site? Should I do that before, during or after my migration? Is it secure? How long will it take? How much will it cost? What do you recommend?
14. How end users want it to work How we want it to work GET TO CLOUD IT’S How Partners make it work NEED HELP? How Support makes it work CHECK OUT THIS WORKAROUND Why admins know it won’t work WTF CONFIGURED THIS? How Twitter can make us laugh & cry Why is it so challenging?
15. CHECK FLIGHT PLAN - CREW, PATH & STATUS
16. Strategic Challenges People 1 To help you build and migrate into the future 2 Paths 3 Predictability Adapting cloud to your architecture Migration readiness state of mind
17. Moana by Disney
18. People 1 2 Paths 3 Predictability Adapting cloud to your architecture Migration readiness state of mind Strategic Challenges To help you build and migrate into the future
19. Find your Project/Space/Repo Leads Projects Spaces Repos
20. Container Lead 429 days ago
21. Assemble your Cloud migrations dream team Project/Space/Repo Lead Executive Sponsor(s) Technical SMEs Business SMEs
22. Identify key use cases Current challenges Potential use cases Team A Dept B Sponsor C
23. Identify key use cases Current challenges Potential use cases Team A Manage cross-functional collaboration during campaign creation and execution Tracking campaign performance and metrics Create team-specific service desks (ie email, design, web) 
 to standardize work intake and service delivery Tracking goals and OKRs and assign owners Dept B Provide answers to common questions Onboard new employees consistently Create a knowledge base that centralizes HR polices 
 and resources to enable self-service Automate onboarding workflow to ensure timely 
 and consistent experience Sponsor C Manage the sharing of internal vs. external 
 documentation in a secure and compliant way Deliver consistent service to internal customers 
 for contract reviews, etc. Share legal documentation with external parties 
 (external collaboration) Create a service desk for internal legal requests
24. Continous improvement Were we successful? What are our success metrics telling us? 
 Do we need to course-correct? Are there successes in one department that can be highlighted and shared to keep up the momentum? How are our teams feeling about the change? What other steps can we take to support them? Are teams asking for additional features, add-ons, or products? Are there other helpful training resources? Are we ready for teams to start using another Atlassian product to help solve an ongoing challenge? How can we take this to the next level? Is there a new use case we want to land org-wide?
25. “Before, the joke was that we never got to address planned work because we were always doing service work. Now, after the migration, we’ve crushed the entire backlog twice.” Chris Van Cleve, Software Engineer EMC Insurance + Atlassian KEY CLOUD VALUE Guaranteed uptime Jira Software Project and issue tracking Jira Service Desk Collaborative IT Service Management Confluence Document collaboration Bitbucket Git code management
26. People 1 To help you build and migrate into the future 2 Paths 3 Predictability Transformation vs Migration Migration readiness state of mind Strategic Challenges
27. Is this the fastest, least disruptive way to move?
28. Figure out how you’re going to use the new space Methodology Design your architecture in cloud “Your dream house” Atlassian guides Customer decides (the architecture) Partners offer professional help Then choose the best way to build & move in Method Atlassian recommends
29. 1. Portfolio Design
31. Adoption stages How do Atlassian products spread beyond Dev and IT? TECH 
 TEAMS ADJACENT 
 TEAMS ALL KNOWLEDGE WORKERS ALL 
 EMPLOYEES
32. 1 week 1 month 3 months 6 months 1 year FINANCE SALES CUSTOMER SERVICE DEVOPS MARKETING DESIGN OPERATIONS EXECS PROJECT MGMT IT SUPPORT ENGINEERING ANALYTICS PRODUCT SALES CUSTOMER SERVICE DEVOPS MARKETING DESIGN OPERATIONS EXECS PROJECT MGMT IT SUPPORT ENGINEERING ANALYTICS PRODUCT MARKETING DESIGN OPERATIONS EXECS PROJECT MGMT IT SUPPORT ENGINEERING ANALYTICS PRODUCT PROJECT MGMT IT SUPPORT ENGINEERING ANALYTICS PRODUCT PROJECT MGMT IT SUPPORT ENGINEERING How Confluence grows Confluence starts in tech teams and spreads to non-tech teams over time **Functions show in bar: at a specific time, more than 20% of customers have such a function using Confluence. **Only consider customers whose employee size > 250.
33. Which departments in your organization are you looking to enable next? 

34. Transform Rethink your architecture and footprint to improve ways of working Translate Replicate the existing architecture you currently have on Cloud
35. Transform Rethink your architecture and footprint to improve ways of working Translate Replicate the existing architecture you currently have on Cloud Make the transition to Cloud less disruptive Take advantage of the migration to improve your set-up
36. 2. Rate of change
37. POP QUIZ What % of Atlassian customers migrate all at once vs incrementally?
38. POP QUIZ What % of Atlassian customers migrate all at once vs incrementally? a) 1-20% b) 20-40% c) 40-60% d) 60-80% e) 80-100%
39. 52% 48% ALL AT ONCE INCREMENTALLY
40. Centralised Decentralised How you will run the migration?
41. Rapid Migrate everything to Cloud now Gradual Migrate by cohort, when teams are ready Start fresh Migrate the baseline, but otherwise create everything new Ability to support
42. Tenant map examples
43. Tenant map examples
44. Tenant map examples
45. 3. Specify the method
46. Take the full DC/server instance as-is and migrating within a single downtime window Migrating only necessary data and users in a single downtime window Breaking your migration into 2-4 batches based on value- specific cohorts Multiple product-by-product, space- by-space, or team-by-team migrations performed continuously over an extended period of time. • Everything migrated at once • Shorter overall timeline • Decreased costs • Only migrate what you need • Simplify cloud navigation • Improve performance • Phased user onboarding and change management • Gather iterative feedback • Same benefit as phased approach, but negative of extended timeline Option to use both Jira Cloud Migration Assistant and Jira Site Import Option to use both Jira Cloud Migration Assistant and Jira Site Import Jira Cloud Migration assistant Not well-supported You need to move to cloud quickly You want to move to cloud in one migration window You are unable to move to cloud due to internal business drivers Some of your critical apps are not available in cloud yet Overview of migration methods Lift and shift (Big bang) Optimize and shift Phased approach Continuous (Granular phased) Description Benefit Tooling Recommended when…
48. Geo A - Cat A Single Cloud Site Geo B - Cat A Geo C - Cat B Grew by acquisition in multiple geos -> time to merge into a Global team! All at once All at once All at once
49. 1,000s of projects Multiple product lines Product A Product B Function C Need to be more focused, necessitating a structure that recognises the needs of different products, different roles, different timings for implementing the org changes.. All at once By cohort Start fresh Multiple Cloud Sites
50. MIGRATION METHODOLOGY 1. Portfolio Design 2. Rate of Change 3. Specify the method = Business strategy Org structure Operating Model
51. MIGRATION BLUEPRINT go.atlassian.com/migrationblueprint-SYDACE Download a PDF copy
52. Strategic challenges People 1 To help you build and migrate into the future 2 Paths 3 Predictability Adapting cloud to your architecture Migration readiness state of mind
53. Server Cloud 1001001 0 0 1 0 0 1 0 0 1 0 0 1 1101010 1010101 0 0 1 0 0 1 1110001001 0011110010 1100101011 01111110001
54. Server Cloud 1001001 0 0 1 0 0 1 0 0 1 0 0 1 1101010 1010101 0 0 1 0 0 1
55. exactly the same data structure completely different data structure Somewhere here
56. by M. Gulin
57. Server Cloud 1001001 0 0 1 0 0 1 0 0 1 0 0 1 1101010 1010101 0 0 1 0 0 1 Data compatibility issues
58. Our best measure of progress
59. Our best measure of progress is working software
60. Data compatibility Fix at a health issues - run data integrity checkers, and test… Achieving migration readiness Working software Test flight success -verify that you are truly migration ready Minimise Prioritise what to migrate. Clean up but don’t go overboard.
61. Strategic challenges People 1 To help you build and migrate into the future 2 Paths 3 Predictability Adapting cloud to your architecture Migration readiness state of mind
63. Jason Wong Principal Product Manager, Atlassian Journey to Cloud Demo & tips for using the Cloud Migration Assistants
64. GO TO GATE. WE’RE READY FOR TAKEOFF 🛫
65. THE BEST (AND LAST) ATLASSIAN UPGRADE
66. SEE YOU ON CLOUD!
67. Q&A