When you use the upgrade skill with a coding agent, for example, Claude Code, the upgrade skill guides you through the migration one step at a time.
An upgrade session is a conversation with the upgrade skill in your development environment.
It's not a Claude Code session but a back-and-forth exchange in which the skill asks questions, checks with you at key points, and gathers evidence of progress.
Understanding how upgrade sessions work helps you get better results and know when to move forward or ask for help.
Prerequisites
A coding agent, such as Claude Code.
dtctl installed and configured for your environment.
In every upgrade session, the upgrade skill works step-by-step and checks with you before moving on:
Request classification: The upgrade skill first classifies your request as a question, a single task, or a full program, and tells you which one it chose so you can override it.
Clarifying questions: The upgrade skill asks clarifying questions one at a time and prefers multiple answers.
Checkpoints between tasks: The upgrade skill stops at a checkpoint between tasks and waits for you.
Evidence-based verification: The upgrade skill reruns readiness checks as evidence instead of only stating that a task is complete.
Deletion assessment: One of the skill's first questions is whether you still need a Dynatrace Classic object at all. A large share of Dynatrace Classic configuration is no longer used and should be deleted rather than migrated, which saves you from upgrade work.
Know when the upgrade stops
The upgrade skill doesn't keep trying indefinitely.
It stops and hands control back to you in these cases:
After three failed attempts at a problem, the upgrade skill stops and escalates instead of trying again.
A missing permission or credential is a blocker, not something to retry.
The upgrade skill names the missing scope and hands control back to you.