Troubleshoot Migration Tool issues

Connection validation fails for Source

The Controller URL is incorrect, the API client name or secret is invalid, or the Controller is unreachable.

Verify the Controller URL, confirm the API client credentials in Splunk AppDynamics, and check network connectivity.

Connection validation fails for Destination

The organization URL is incorrect, or the access token is invalid or expired.

Verify the organization URL, regenerate the access token in Splunk Observability Cloud, and update the connection.

API token not found in cache

The source connection token has expired or the system evicted it from cache.

Edit the source connection, reenter the API client secret, and save the connection to refresh the cached token.

Artifacts do not load

The API client lacks permission to read the requested artifact type.

Grant the API client read access to applications, Health Rules, dashboards, and action templates.

Cannot create detectors or dashboards in destination

The access token has read-only permissions.

Generate a new access token with write scope and update the destination connection.

Connection test returns 401 or 403

The credential is invalid or expired, lacks the required role or scope, or belongs to the wrong account or realm.

Verify the selected connection, credential ownership and expiration, required role and scope, account, realm, and endpoint. Rotate the credential if necessary, then retest.

Connection times out or TLS fails

DNS, proxy, firewall, TLS inspection, certificate trust, endpoint, or port connectivity is incorrect.

From the network zone where Migration Tool or Collector runs, verify the endpoint, DNS, port 443, proxy and firewall routing, and certificate trust. Do not turn off certificate verification.

Report status shows Failed

The source API token expired, the Controller is unreachable, or the API client lacks permissions.

Go to Connections, verify or refresh the source credentials, and generate the report again.

No source connections available

No source connection exists on the Connections page.

Add at least one source connection before generating a report.

Report takes a long time

The source Controller has many applications or artifacts.

Wait for the report to complete, or generate reports during off-peak hours for large environments.

Download button is unavailable

The report continues to generate or has failed.

Wait until the status changes to Ready or regenerate the report if it failed.

Applications or artifacts do not appear

The source connection points to the wrong Controller or account, the credential lacks read permission, the application is inactive or outside the released scope, filters exclude it, or discovery completed with a partial error.

Verify the Controller and account, credential permissions, application status and support, and active filters. Run discovery again if necessary, then reconcile the displayed inventory with the source inventory.

A migration job completes but an artifact fails

A terminal job state can include artifact-level failures that result from mapping, transformation, permission, or destination errors.

Review each artifact’s status, warnings, and errors. Preserve the job ID, timestamps, artifact names, mapping details, and destination, then correct the cause and confirm that retrying is safe.

A dashboard value does not match

The source and target use different metric names, units, rollups, aggregations, filters, dimensions, time ranges, missing-data behavior, or chart types.

Compare the source and target configurations using equivalent traffic periods. Validate the underlying data and calculations rather than relying on visual similarity.

A detector does not match a Health Rule

The signal scope, threshold, baseline, duration, schedule, severity, clear behavior, notification routing, or missing-data behavior differs. Custom metrics might not translate automatically.

Compare each setting and manually reconstruct unsupported custom-metric behavior. Keep the migrated detector inactive until the comparison passes.

A migration overwrote an existing target artifact

Re-migrating an artifact can overwrite an existing detector, dashboard, chart, or integration.

Stop further migrations for the artifact, record the job and artifact IDs, compare the target with the approved pre-migration configuration, and restore it manually if required. Correct and review the transformation before retrying.

I cannot delete a migrated artifact

Migration Tool does not delete detectors, dashboards, charts, or integrations from Splunk Observability Cloud.

Use the applicable Splunk Observability Cloud procedure and permissions to deactivate or delete the artifact. Before deleting it, confirm that no dashboard, detector, notification route, or operational workflow references it.

A previous migration job does not appear

The internal Splunk AppDynamics-hosted tool and the customer-facing Splunk Observability Cloud-hosted tool maintain separate job histories.

Contact the team that performed the migration and obtain the applicable reconciliation or audit report.

Another migration job does not start immediately

Only one migration job can run per tenant at a time. Additional jobs for the same tenant are queued.

Wait for the active job to reach a terminal state. Do not submit duplicate migration requests.

Telemetry is missing or duplicated

Agent initialization, deployment mode, Collector receivers or exporters, endpoint, token scope, queues, context propagation, or duplicate OpenTelemetry SDK initialization is incorrect.

Determine whether Splunk AppDynamics, Splunk Observability Cloud, or both are affected. Review the agent and Collector configuration and logs, then correct the missing or duplicate telemetry path.

Performance degrades in dual-signal mode

Dual export increases resource or network use, or the agent or Collector experiences queue pressure, retries, export failures, or excessive attributes.

Compare CPU, memory, latency, throughput, errors, and network use with the approved baseline. Review agent and Collector logs, and stop the wave and run the rollback plan if an approved trigger is met.

Cutover stops target telemetry

The cutover changed or removed an agent or Collector setting required to export telemetry to Splunk Observability Cloud.

Restore the last verified dual-signal configuration, generate traffic, and verify both telemetry paths. Correct the cutover configuration before attempting cutover again.