Wave planning and approval

Generate the APM Migration Wave Planning report by following Generate Reports.

Generate the APM Migration Wave Planning report by following Generate Reports.

The report recommends a migration sequence based on application complexity, traffic patterns, agent types, and business criticality.

Wave Purpose Typical applications
Wave 0 - Pilot Validate the migration process Two or three non-critical applications representing different technologies
Wave 1 - Nonproduction Refine the migration procedure Development, test, and staging applications
Wave 2 - Lower-risk production Begin production migration Internal, lower-traffic applications
Wave 3 - Medium-risk production Expand the production migration Customer-facing applications with moderate traffic or complexity
Wave 4 - Business-critical production Complete the most carefully controlled migrations High-traffic, revenue-impacting, or business-critical applications

Validate the assignments

For each application:

  • Confirm that its complexity is represented accurately.
  • Confirm its normal and peak traffic patterns.
  • Confirm its agent type, runtime, and deployment method.
  • Confirm its business criticality.
  • Review its upstream and downstream dependencies.
  • Confirm that required application owners and validation resources are available.
  • Confirm that the proposed wave aligns with approved change windows.
  • Move the application to a different wave when the report does not account for an important dependency or operational requirement.

Approve the wave plan

For each wave, record:

  • Included applications and environments.
  • Wave owner and application owners.
  • Dependencies and required coordination.
  • Planned schedule and change window.
  • Success criteria and validation period.
  • Rollback triggers and decision owner.
  • Deferred or excluded applications.

The wave plan is complete when application owners and migration stakeholders approve the application assignments and migration sequence.