About the migration tool

Prepare for migration

Use this documentation if you are an AppDynamics SaaS customer planning to migrate supported monitoring artifacts to Splunk Observability Cloud.

Before starting, confirm that:

• Your Splunk Observability Cloud organization is eligible and has migration-tool access enabled.
• Your account has the required administrator or power-user role.
• The applications and artifacts in your pilot are supported.
• You have completed the prerequisites in Before You Begin, including access, ownership, rollback planning, and manual-migration responsibilities.

Splunk AppDynamics On-Premises is not supported.

For supported artifacts, limitations, and required manual work, see Supported Migration Scope and Limitations.

Migration boundary

The migration tool migrates supported monitoring configurations and artifacts. It does not transfer historical AppDynamics metrics, logs, traces, or transaction snapshots.

A successful migration does not guarantee identical behavior between AppDynamics and Splunk Observability Cloud. Validate the monitoring outcomes that matter to your team, such as alerting, dashboards, notifications, ownership, and incident-response workflows.

Recommended approach

Migrate in waves. Start with a noncritical pilot and retain AppDynamics monitoring while you validate the target environment.

After each migration job, review artifact results and complete any required follow-up for failed, partially supported, or unsupported items.

For the end-to-end workflow, see Get Started with the Migration Procedure.

How to access the tool

Before accessing Migration Assistant, confirm that you have an Admin or Power User role in Splunk Observability Cloud and that Migration Assistant is enabled for your organization. See Confirm Eligibility and Support.

1. Log in to the Splunk Observability Cloud.
2. Select Data Management > Migration Assistant.

The following image displays the New Migration Job dashboard with the Applications tab selected.

See New Migration Job.