Skip to main content
Do you build apps on Splunk or are a Splunk admin? If so, we want to hear from you. Help shape the future of Splunk and win a $35 gift card!

Take the Survey
Lantern Home
 
 
Splunk Lantern

Phase 2: Getting started with your Splunk Cloud Platform migration

  1. Last updated
  2. Save as PDF

 

Meet the team

Splunk teams are here to help make your transition to cloud easier. You may decide to chart your own path to Splunk Cloud Platform or take advantage of Splunk Professional Services teams that are available to you to help you in your cloud migration (datasheet for reference). Or, you can seek help from one of the Splunk Partners.

Here are the Splunk teams to reach out to whenever you have a query or concern:

Table 1: Your migration support team at Splunk

Splunk Team What can we do for you?
Support Helps troubleshoot and resolve product issues.
Professional Services Can be engaged to support migrations or lead the end-to-end migration, depending on your needs.
Customer Success Helps confirm migration vision, provide continuity on value delivery, and support your ongoing success.
Technical SMEs Technical SMEs understand technical use-cases of the various usage domains to help the migration team understand scoping and make decisions if knowledge objects, apps, config, etc. require merging/changes.
Technical Support Account Manager (TSAM) Partner with Professional Services, Project Management, Support, and the Account team to help customers succeed in Enterprise to Splunk Cloud Platform migrations.

It would also be useful to determine your own migration team. For a relatively small migration, it may be adequate for one skilled, experienced resource to handle the migration. In that case, that capable individual (likely you) would wear multiple hats and cover the multiple roles/functions listed in Table 2 below. For larger migrations, a larger team may need to be involved. The recommendations and table below are intended to give you a sense of the roles and work involved so that you can develop a “right fit” staffing plan that will set you up for a successful migration.

There may not always need to be a 1:1 fit/assignment between functions and staff. It is up to you to staff and plan the work to best suit the talents, capabilities, and interests of your team and business partners. If you have aptitude and interests in more than one area, it’s fine to dive in, roll up your sleeves, and cover those areas; just make sure you have the support you need to be successful.

While this planning exercise will help you prepare, it is not permanent or mandatory; you always have the ability to ramp up resources and get additional support should you encounter unforeseen challenges or opportunities.

Table 2: Your migration support team at your organization

Role/Function Insert name here Notes/Key responsibilities
Champion  
  • Own and champion the budget, vision, and business value of Splunk
  • Evangelize and grow the impact
Stakeholders  
  • Own one or more business area and/or resource groups that utilize Splunk as part of their daily business function
  • Provide resources (domain expertise) to support migration.
  • Evangelize change
Migration Owner (PM)  
  • Own/accountable for full end-to-end migration
  • Involved in the detailed migration planning & directing (or doing) the execution tasks
  • The main point of contact for business leadership/Splunk team
Tech Lead/ Troubleshooter  
  • Lead the ‘gnarly’ problem-solving efforts
  • Understand outputs of Cloud Migration Assessment app and helps plan deployment
Supporting Technical SMEs  
  • Expertise and resources from organizations outside the Splunk Platform teams which the migration effort will need to coordinate with such as Networking, Storage, Infrastructure, Firewall, Data Centers, etc.
Change Agent/
Business Liaison		  
  • Confirm business-critical apps in scope
  • Communication vision/value of migration
  • Set expectations
  • Build engagement, enthusiasm, and understanding of the impact of solutions

Get acquainted with Splunk Cloud Platform and migration options

Below you will find a couple of resources that will help you become more familiar with what the transition to Splunk Cloud Platform entails and the services available to help you do so.

  • Take the Transitioning to Splunk Cloud course. This is highly recommended by customers and Splunkers alike. The training will highlight key differences between Splunk Enterprise deployed on-premise vs in the cloud to allow Splunk Administrators to transition to Splunk Cloud Platform effectively.
  • Get to know all about Splunk Cloud Services, especially the differences between on-premises Splunk deployments and Splunk Cloud Platform .

As you begin to plan out your cloud migration, it’s important to understand the options available to you based on your environment and needs. For example, here are two types of migrations to consider:

Start fresh Migrate configs, apps, and data
You may choose to run your Splunk Cloud stack as a new environment and not move anything over from on-premises. A more common migration involves migrating existing configuration settings, users and roles, approved/vetted apps, and dashboards to the Splunk Cloud Platform. This is often referred to as "local" configurations and "private knowledge objects".
Recreate configurations/dashboards & install approved/vetted apps. You can do it yourself, with the help of Splunk Professional services or Splunk partners. You can move some or all of your existing indexed data to your Splunk Cloud stack, to allow seamless historic searching. Customers can leave some data on-premises in observance of your organizations’ compliance requirements.
It is often suitable for smaller, less complex environments, or where mostly new use cases are being implemented. We recommend engaging with Splunk Professional Services for copying your data to the cloud. Reach out to your account team or to ps-sales@splunk.com for more information.
Migrating to Splunk Cloud Platform
The guided path below provides an overview of how to migrate to Splunk Cloud Platform. In addition, it contains recommendations on best practices, tutorials for getting started, and troubleshooting information for common situations.
Pages: 7