Phase 1: discovery and assessment

Define the migration scope, identify dependencies and risks, assess application complexity, create migration waves, and record the baseline required for later validation.

Define the migration scope, identify dependencies and risks, assess application complexity, create migration waves, and record the baseline required for later validation.

Complete the following tasks in order:

  1. Assess the Splunk AppDynamics Environment
  2. Configure Connections
  3. Create and Verify the Application Inventory
  4. Wave Planning and Approval
  5. Establish Baselines and Success Criteria

Confirm readiness

Before beginning Phase 2, confirm that:

  • Every Splunk AppDynamics SaaS Controller and account in scope has a completed environment assessment.
  • Every required source connection is configured and passes its connection test.
  • Application Discovery and APM Application Inventory reports are generated for every source Controller and account in scope.
  • Every discovered application has an In scope, Out of scope, Deferred, or Review required decision.
  • Every in-scope APM application has a verified inventory.
  • Missing or unexpected applications and configurations have been investigated.
  • Preliminary source-to-target mappings and naming requirements are documented.
  • Every material APM item has an initial migration disposition.
  • Risks, dependencies, and special-handling requirements have assigned owners and actions.
  • Migration-wave recommendations have been reviewed and adjusted when required.
  • Migration-wave assignments and sequence are approved.
  • Baselines and migration success criteria are documented.
  • Application owners and migration stakeholders approve the discovery results, migration scope, and wave plan.

Phase 1 is complete when every checklist item is confirmed.