Splunk's Cloud Migration Journey

Introduction

• Greg Warner, Senior Manager of Collaboration and Productivity Platforms at Splunk, worked with his CIO to create 3 migration musts: seamless use of core features, zero downtime, and flexibility.
• Splunk had a large inventory of data to migrate including 2 million issues, 3.5 million attachments, 3 million Confluence pages, 6.4 million comments, and 40 apps.
• Approximate 35% time reallocation was achieved by freeing technical teams from on-premise maintenance and offering more effective tools.

Essential Foundations of Platform Realization

Platform Realization

• Users can experience the full value of Atlassian Cloud by approaching it as a platform with integrable tools and collaborative capabilities.
• Warner's Critical Insights:
  • Platform Management: Unifying data sets and tools across departments for a cohesive work environment.
  • Governance: Ensuring stability and predictability for stakeholders. Empowering team members to focus on strategic efforts.
  • Data Accessibility: Making data and assets more accessible by moving them to the Cloud.
  • Enablement: Providing resources for technical teams to make the most of the platform.
  • Measure: Checking if current use cases are thriving and getting the right integrations.

Splunk's Post-Migration Experience

1-4 Weeks After Migrating

• Positive growth was observed across the organization.
• Existing use cases were better served on the platform.

1-6 Months After Migrating

• Splunk's solution partner ramped off, leaving the team to operate on Cloud independently.
• Non-technical teams, like procurement and HR, embraced the new tools and processes, and automation.
• Ongoing adoption and engagement were observed throughout the platform.