New Migration Job

Reference information about the New Migration Job workflow and the prerequisites for creating a migration job.

The New Migration Job task is part of Migration Tool in Splunk Observability Cloud Migration Assistant, a hosted tool that automates and accelerates migration activities from Splunk AppDynamics to Splunk Observability Cloud.

The dashboard enables you to create, configure, and start a migration job that transfers critical Splunk AppDynamics configuration artifacts to a Splunk Observability Cloud destination. These artifacts include applications, Health Rules, dashboards, and HTTP Request Templates.

This task is the central starting point in the migration workflow. It provides a guided interface to select source and destination environments, select the artifacts to migrate, assign a migration tag, and start the migration process.

Prerequisites

Before creating a new migration job, ensure the following prerequisites are complete:

Prerequisite Details

Source connection created

A Splunk AppDynamics Controller connection must be configured on the Configure Connections page with the Controller URL and API access token.

Destination connection created

A Splunk Observability Cloud connection must be configured on the Configure Connections page with the organization URL and access token.

Agent setup completed

Deploy the agents and validate dual ingestion. Confirm that trace and metric data is visible in Splunk Observability Cloud APM for the in-scope applications.

Configuration migration scope available

Review the application inventory, Health Rule inventory, dashboard inventory, and HTTP Request Template inventory to identify what to include in the migration job.

Access the New Migration Job dashboard

Access the New Migration Job dashboard in Splunk Observability Cloud.

  1. Log in to the Splunk Observability Cloud.
  2. Select Data Management>Migration Tool.
  3. In the left navigation menu, select New Migration.
  4. The New Migration Job dashboard opens. The page shows the source and destination selectors, artifact tabs, and migration summary panel.

New Migration Job page

Start a migration job

Select source and destination environments, select artifacts, and start a migration job.

  1. Select the Source Environment— Select the Splunk AppDynamics Controller connection.
  2. Select the Destination Environment— Select the Splunk Observability Cloud connection.
  3. Select Artifacts— Use the Health Rules, Dashboards, and HTTP Templates tabs to select what to migrate. Use the Application tab to view the applications, associated artifacts, and the migration status.
  4. Review the Migration Summary— Confirm selected items and the migration tag.
  5. Start Migration— Select Start Migration to begin.
  6. Monitor Progress— Go to the Migration Jobs page to view status, success or failure details, timestamps, and error messages for each artifact.

Dashboard details

Reference information about the environment selectors, artifact tabs, and migration summary panel.

The New Migration Job dashboard is organized into three main areas: environment selectors, artifact selection tabs, and the migration summary panel.

1. Environment selectors

The top section defines the migration direction from the Splunk AppDynamics source Controller to the Splunk Observability Cloud destination organization.

Selector Description

Source Environment

The Splunk AppDynamics Controller from which artifacts are migrated. The selector displays the configured connection name and Controller URL.

Destination Environment

The Splunk Observability Cloud organization where artifacts are created. The selector shows the configured destination connection and organization URL.

An arrow between the selectors visually indicates the migration direction. Each selector includes controls to clear or change the selected connection.

2. Artifact selection tabs

The dashboard contains tabs for the artifact types that can be included in the migration job.

Tab Description How to use
Applications

Lists applications discovered in the source Splunk AppDynamics Controller. Applications define the migration scope and are used to group related configurations.

Browse or search the list and select one or more applications to include. If the list fails to load, the UI displays an error message and a button.
Health Rules

Lists Splunk AppDynamics Health Rules associated with selected applications. These rules are translated into Splunk Observability Cloud Detectors.

Search and select an application to filter Health Rules. Use filters such as and to refine the list, then select the Health Rules to migrate.
Dashboards

Lists Splunk AppDynamics dashboards. Widgets such as time series graphs, metric values, gauges, text widgets, and event lists are translated to Splunk Observability Cloud dashboard charts where supported.

Select the dashboards to migrate. After migration, review the converted queries and visualizations, especially for complex widgets.
HTTP Templates

Lists Splunk AppDynamics HTTP Request Templates, also known as webhook action templates. These are translated to Splunk Observability Cloud webhook integrations.

Select the templates to migrate. Review any templates containing conditional logic because or logic requires manual restructuring after migration.

New Migration Job health rules sample

Migration summary panel

The panel provides a real-time summary of the migration job as users select items from the tabs.

Element Description

Search selected items

Filters selected artifacts so users can review the included artifacts before starting the migration.

Total Health Rules

Displays the count of Health Rules selected for migration.

Total Dashboards

Displays the count of dashboards selected for migration.

Total HTTP Templates

Displays the count of HTTP Request Templates selected for migration.

Tag Name

A unique migration tag to identify and track the migration job. You can customize it before starting the job.

Start Migration

Starts the migration using the selected source, destination, artifacts, and tag.

What gets migrated

Reference information about the artifacts that migrate and the items that require manual review.

Artifact What is migrated What requires manual review

Applications

Application metadata and migration scope used for configuration migration.

Business Transaction naming alignment, workflow rules, operation grouping, and endpoint rules.

Health Rules

Converted to Splunk Observability Cloud detectors with SignalFlow conditions, thresholds, and severity rules.

Complex baseline rules, custom metric references, schedule-based evaluations, and Splunk AppDynamics wait-time behavior.

Dashboards

Dashboard widgets are translated to Splunk Observability Cloud charts, including time series, single value, text, gauge, and event-feed equivalents where supported.

Pie charts, iFrame widgets, health list widgets, baseline visualizations, and complex metric expressions.

HTTP Templates

Recognized webhook payload variables are mapped from Splunk AppDynamics syntax to Splunk Observability Cloud syntax.

Conditional logic such as #if and #else, custom retry behavior, success/failure criteria, and unsupported Splunk AppDynamics actions.

Additional information

Reference information about error handling, migration tags, and post-migration considerations.

Error handling

If the system cannot fetch data, the center panel displays an error message and a Retry button. For example, an application list may fail to load if the source API token is missing or invalid.

Common causes include:

  • The source connection API token has expired or is invalid.

  • The Splunk AppDynamics Controller is unreachable.

  • There are network connectivity issues between Migration Tool and the Splunk AppDynamics Controller.

Resolution: Go to the Connections page, verify or refresh the source connection API token, confirm Controller connectivity, and retry.

Migration tag

Each migration job is assigned a tag to help identify and track it in the Migration Jobs list. You can keep the generated tag or customize it for easier reference, such as wave1-prod-apps or appd-to-splunk-july-2026.

Important notes

  • Run this workflow after combined agents are deployed and Splunk Observability Cloud data ingestion has been validated.

  • Review migrated detectors and dashboards after the job completes to confirm SignalFlow logic, dimensions, units, and alert behavior.

  • Duration metrics in Splunk Observability Cloud may be stored in nanoseconds. Use scaling where required to display milliseconds consistently.

  • For Splunk AppDynamics Business Transaction parity, configure the required workflow, operation-grouping, and endpoint rules. For guidance, see Refine the Business Transactions and Optimize Business Transaction Detection.

  • Use the Migration Jobs page to validate status and troubleshoot failures for each selected artifact.