Try it free

Upgrade scoping

  • Latest Dynatrace
  • Upgrade guide
  • Published Jul 24, 2026

Define the upgrade scope before any technical work begins: identify which teams and applications will be migrated, take inventory of existing classic Dynatrace configuration, and explicitly agree on what stays out of scope.

This stage prevents scope creep and misaligned expectations by establishing a shared, signed-off baseline: what gets upgraded, what gets retired, and what is deferred to a later phase.

Why scope your upgrade?

Starting the upgrade without a defined scope leads to scope creep, misaligned expectations, and rework.

  • Upgrade starts with full alignment: teams, applications, and classic configuration assets are scoped, classified, and approved before any technical work begins, so budget and effort go where they deliver value.
  • Risk is owned before it becomes a problem: out-of-scope items are named, deferred, and assigned an owner up front, and agreed success criteria give the project sponsor and delivery team a shared definition of done.

What will you do?

This stage produces a signed-off scope baseline, the document that governs all technical decisions in the stages that follow.

  1. Define which teams and applications are in scope for the upgrade
  2. Inventory existing classic configuration and classify each asset for migration, retirement, or deferral

Before you begin

At a glance

  • Estimated effort: 1–3 days
  • Estimated timeline: 1–2 weeks

Prerequisites

Access to a Dynatrace Classic environment with admin or read-only export permissions.

Key stakeholders

RoleInvolvementResponsibility
Dynatrace AdminRequiredProvides access to Dynatrace Classic environment, exports configuration, and validates inventory counts
Project SponsorRecommendedApproves scope, confirms out-of-scope decisions, and signs off on success criteria
Application Team LeadsRecommendedConfirm which apps and hosts fall under their team and flag known dependencies
Integration OwnersOptionalConfirm disposition of third-party alerting and ITSM integrations (for example, ServiceNow, PagerDuty)
ArchitectOptionalAdvises on migration strategy, disposition decisions, and success criteria definition

Upgrade scoping

1. Define who is in scope

Decide whether the upgrade targets a single team, a full environment, or multiple environments, and identify dependencies between teams that affect sequencing.

  1. Determine the upgrade scope: single team, full environment, or multiple environments.
  2. Identify the applications and hosts included in the defined upgrade scope.
  3. Document dependencies between teams that affect upgrade sequencing.
  4. Define what is explicitly out of scope, assign an owner to each deferred item, and get written agreement from the project sponsor.

Verify: Scope document lists all in-scope teams, applications, and hosts, with a separate out-of-scope list that includes owner assignments and deferral reasons.

Prevent scope creep: stakeholders may add items mid-engagement without adjusting timeline or effort. Get written sign-off on the out-of-scope list before technical work begins.

2. Inventory classic configuration

Use the Check your upgrade readiness ready-made dashboard to catalog existing classic assets and classify each one as migrate, retire, or defer.

  1. Open the readiness dashboard to catalog existing classic assets: management zones, dashboards, alerting profiles, SLOs, synthetic monitors, API tokens, and third-party integrations.
  2. Record counts and owners for each asset type.
  3. Classify each asset as: migrate (will be upgraded), retire (will be decommissioned without replacement), or defer (out of scope for this phase).
  4. Document success criteria with the project sponsor: agree on what a completed upgrade looks like before starting.

Verify: Scope document signed off by the project sponsor, with all classic assets inventoried and classified before technical work begins.

Complete your classic inventory: undiscovered dashboards, alerting rules, or integrations that surface after migration starts force re-scoping and timeline slippage. Use the readiness dashboard to surface hidden assets before committing to a plan.

Stage complete when:

  • Scope document is signed off by the project sponsor, listing all in-scope teams, applications, and hosts with a separate out-of-scope list including owner assignments and deferral reasons
  • All classic configuration assets are inventoried and classified as migrate, retire, or defer
  • Success criteria are agreed with the project sponsor before technical work begins

With your upgrade scope signed off and your classic configuration inventory complete, you're ready to start the technical work. The next stage is Enrich ingested signals: ensure every monitored signal carries the metadata that IAM boundaries, segments, and cost allocation all depend on. Enrichment is the foundation; it needs to be in place before any configuration upgrade begins.

Ready for more?

With your scope signed off and classic inventory complete, the next stage is to enrich your observability signals, the foundation all downstream stages depend on. Enrichment must be in place before any IAM, segmentation, or cost allocation configuration begins, so invest time here before moving forward.

Continue to stage 2: Enrich ingested signals.

Related tags
Dynatrace Platform