dt-migration

# Smartscape Migration Skill This skill migrates Dynatrace classic and Gen2 entity-based DQL queries and query patterns to Smartscape-based equivalents. Load the **dt-dql-essentials** skill before writing final DQL so the translated query also follows current DQL syntax rules. This skill focuses on Smartscape-oriented DQL migration only. It does not cover asset-level migration workflows. ## Query Purpose Classification **Start here.** The correct migration strategy depends on what the query is actually trying to do — not just which classic constructs it uses. There are three distinct situations: | # | Situation | Classic anti-pattern | Migration strategy | | --- | --- | --- | --- | | 1 | Mass data query filtered by entity conditions | `classicEntitySelector(...)` inline in `filter:` of a timeseries, logs, or metrics query | Resolve entity conditions to raw data dimensions first. Smartscape is a fallback, not the default. | | 2 | Mass data query using entity subquery for filtering | `fetch dt.entity.*` inside `in [...]`, `lookup [...]`, or `join [...]` to filter the outer mass data query | Same dimension-first strategy. Rewrite as raw dimension filter or `in [smartscapeNodes ...]` subquery. | | 3 | Pure entity list query | `fetch dt.entity.*` used standalone or as the primary result source | `smartscapeNodes` is the only valid path. No raw dimension alternative exists. | **Decision:** - **Situations 1 or 2** — load [references/mass-data-filtering-strategy.md](referenc...