Frequently asked questions
No. Migration Tool changes monitoring configuration and artifacts. It does not transfer historical metrics, logs, or traces.
Does Migration Tool migrate historical Splunk AppDynamics data?
No. Migration Tool changes monitoring configuration and artifacts. It does not transfer historical metrics, logs, or traces.
Does a successful import prove equivalence?
No. Validate the artifact's data, logic, notifications, ownership, and operational outcome.
Which artifacts can I migrate?
Migration Tool migrates Health Rules, dashboards, and HTTP Request Templates. It converts them to detectors, dashboards and charts, and integrations such as webhooks. Applications define the selection scope; they are not migrated as standalone destination artifacts.
Why must I create a destination connection after logging in?
A separate destination connection is intentional. Logging in gives you access to Migration Tool. The destination connection provides the endpoint and API access token that Migration Tool uses to create or update artifacts in the destination Splunk Observability Cloud organization.
Does Migration Tool migrate database monitoring agent configuration?
No. Migration Tool does not migrate Database Monitoring agent configuration. It can generate a Database Application Inventory report to help you plan the migration, but you must configure database monitoring separately in Splunk Observability Cloud.
How long does dual operation last?
Continue until representative traffic, critical artifacts, notifications, investigations, service quality, and rollback readiness pass the approved checks.
When can I retire Splunk AppDynamics?
Only after the migration wave completes cutover and stabilization, all critical gaps are resolved or accepted, and the responsible stakeholders approve retirement.
Can Migration Tool delete a migrated artifact?
No. Delete or deactivate the target artifact directly in Splunk Observability Cloud when required.
What happens if I migrate the same artifact again?
Re-migration can overwrite the existing target artifact. Review the transformed configuration and preserve the target configuration before continuing.
Why can't I view a migration performed by premium support?
The internal and customer-facing deployments maintain separate migration histories. Obtain the migration report from the team that performed the earlier migration.