Get started with the migration procedure

Reference information for migrating an approved application wave through the APM migration phases.

Use this guide to migrate an approved application wave from Splunk AppDynamics SaaS to Splunk Observability Cloud.

Complete the migration phases in order. Each phase has its own prerequisites, activities, expected results, and exit criteria. Do not continue to the next phase until you meet the current phase’s exit criteria.

Important: Begin with a non-critical pilot application or environment. Complete and validate the pilot before migrating production applications or production telemetry.

Prerequisites

Complete Before you begin, including its readiness checklist, before starting the migration.

Do not begin a migration until you satisfy all prerequisites and the required stakeholders have approved the migration scope.

Application Performance Monitoring (APM) migration phases

Complete the APM migration in the following order. Each phase page contains its prerequisites, activities, expected results, and exit criteria. Do not continue until you satisfy the current phase’s exit criteria.

Phase Purpose

Phase 1: Discovery and Assessment

Identify the applications and configurations in scope, assess complexity, define migration waves, and establish baselines and success criteria.

Phase 2: Prepare Splunk Observability Cloud

Prepare the destination Splunk Observability Cloud organization and verify that it can receive data before you configure agents or Collectors for the migration wave.

Phase 3: Enable Application Telemetry

Set the combined-agent mode, select the telemetry route, and validate the deployment.

Phase 4: Migrate Monitoring Configurations

Align Business Transactions, configure required rules and MetricSets, migrate supported monitoring configurations, and resolve nonportable or unsuccessful artifacts.

Phase 5: Validate and Prepare for Operations

Validate telemetry and migrated configurations, resolve significant gaps, and prepare operations teams.

Phase 6: Cut Over and Stabilize

Transition the approved wave to Splunk Observability Cloud, monitor stabilization, and retire superseded monitoring after approval.

If a migration step fails

Use Troubleshooting and FAQ to diagnose connection, discovery, telemetry, artifact migration, validation, or cutover problems.

Preserve the migration job identifier, artifact status, timestamps, versions, sanitized configuration, relevant logs, and rollback result before contacting Support.