Skip to main content
Version: Atlas v5.1

Migration Tracker

Overview​

Migration Tracker gives migration teams a shared view of progress from one Splunk environment to another. It compares a selected source server with a selected destination server and reports whether datasets and knowledge objects are present, different, or complete in the destination.

Open Splunk Migration Tracker from Power Utilities. Select the source and destination servers in the page banner, then use Data Volume and Knowledge Objects to review the migration.

Capabilities​

  • Compare source and destination ingest by index, sourcetype, source, and host.
  • Compare supported Splunk knowledge objects, including dashboards, saved searches, macros, event types, field extractions, and data models.
  • Record destination rename mappings without changing Splunk objects or data.
  • Add definitions, labels, notes, acknowledgments, and ignore decisions to coordinate migration work.
  • Track Missing, Partial, Acknowledged, Complete, and Ignored items over time.

Select Migration Environments​

Select a Source Server representing the environment being migrated and a Destination Server representing the new environment. The same server cannot be selected for both. Atlas saves the selections in the browser so the comparison is restored when the page is reopened.

The page banner changes with the selected dashboard. Data Volume summarizes source and destination ingest, migration progress, and remaining dimensions. Knowledge Objects summarizes object types, migration progress, and remaining objects.

Data Volume​

Use Data Volume to confirm that expected data has reached the destination and arrived under the expected metadata values.

Compare ingest across a cutover​

Select the calendar button beside the destination server to open Comparison Time Ranges. Choose the Ingest Amount of 1, 4, 8, or 24 hours, then select representative Source Date and Destination Date values from before and after the cutover. Future dates cannot be selected. Atlas saves the selected time ranges in the browser and includes them in the page URL.

Dimensions, filters, and navigation​

Results can be organized by Index (IX), Sourcetype (ST), Source (S), and Host (H). By default, the table groups by index and sourcetype. Use the dimension controls to add, remove, or reorder dimensions, then expand a group to drill into the next selected dimension.

Use the filter panel to focus results by:

  • Migration Status: Missing, Partial, Acknowledged, Complete, or Ignored.
  • Labels: labels assigned to datasets.
  • Destination display mode: aggregate destination values or show each destination separately.

Use Columns, the quick filter, and standard grid controls to tailor, search, sort, filter, or paginate the table. Atlas retains selected filters, dimensions, and visible columns in the browser.

Rename dataset mappings​

Use Dest Dataset Rename in a row action menu when a dataset dimension has a different destination value. Enter the destination value for each dimension shown in the dialog, or select the blue Source value to restore a source value, then select Confirm Rename. For example, map source index security to destination index security_cloud.

The mapping changes how Atlas compares matching source values with destination values; it does not change indexes, props, inputs, or events in Splunk.

Dataset actions​

Use Define Dataset Info to maintain the Atlas Data Definition for a supported dataset level. Select compatible rows and use Define Datasets for a bulk update. You can also select rows for these actions:

  • Label Datasets adds labels without removing existing labels.
  • Ignore/Unignore excludes results from tracking or restores them. Ignoring requires a reason and can include a note.
  • Acknowledge/Unacknowledge accepts a reviewed difference as complete or restores its calculated status.

Group-level edits apply to the dataset dimension represented by that group. Composite rows that combine multiple dimensions cannot be edited as a single migration item.

Knowledge Objects​

Use Knowledge Objects to compare supported Splunk content on the source with its expected counterpart on the destination.

Group, filter, and inspect objects​

Use KO Grouping to group results by Category or Type. You can also filter by migration status and labels. The table begins with the least-complete statuses so Missing and Partial objects are visible first; expand groups to review individual objects.

Use Columns to reveal source, destination, and mapped values for name, app, owner, sharing, local status, notes, and other object metadata. Atlas saves grouping, filters, and column visibility in the browser.

Rename knowledge-object mappings​

Select a destination server, then use Dest KO Rename from a row action menu when the destination object uses a different Name, App, or Owner. Enter only the values that differ, or select a blue Source value to copy it into a field, then select Confirm Rename. Clearing a mapped value or restoring the source value removes that override.

Use Rename app globally to apply an app mapping to all compared objects from the source app. Use Rename owner globally to apply an owner mapping to all objects with the source owner. Review the scope before confirming: global mappings affect every matching object in the comparison. These mappings affect Atlas comparison only; they do not rename or move Splunk knowledge objects.

Details and bulk actions​

Select View KO Details from a row action menu to review source and destination identity and properties. Where supported, the dialog can query non-default REST properties and show _configtracker change history for selected periods. Use it to decide whether a Partial result is incomplete, intentional, or ready to acknowledge.

Select one or more objects to use these bulk actions:

  • Label KOs adds labels while retaining existing labels.
  • Ignore/Unignore KOs excludes selected objects or restores them. An ignore reason is required and a note is optional.
  • Acknowledge/Unacknowledge KOs accepts reviewed differences or restores the calculated status.

Migration Status and Workflow​

Atlas compares the source with the destination and assigns a status:

  • Missing: the source item or value is not found in the destination.
  • Partial: the destination item exists, but compared values differ.
  • Acknowledged: a user reviewed and accepted the difference; Atlas counts it as complete while retaining the acknowledgment.
  • Complete: compared source and destination values match.
  • Ignored: the item is excluded until it is restored.

Status is recalculated from the current comparison except where an acknowledgment or ignore override applies. Use this workflow to keep the review focused:

  1. Select the source and destination servers, then choose representative dates on either side of the cutover.
  2. Review Missing and Partial datasets, beginning with index and sourcetype before drilling into source and host.
  3. Add dataset, object, app, or owner mappings for intentional destination differences.
  4. Use details, labels, and notes to record investigation and ownership.
  5. Acknowledge reviewed differences; ignore only content that is outside the migration scope.
  6. Revisit progress indicators as remediation and migration work continues.

Use overrides deliberately: Acknowledged counts an understood difference as complete, while Ignored removes it from active monitoring. Unacknowledge and Unignore restore the calculated comparison status.