AppDynamics to Dynatrace Migration: A Practical Plan
Many AppDynamics customers are reviewing their options now that AppDynamics sits inside Splunk's observability portfolio and Splunk Observability Cloud is positioned as the cloud native direction. If Dynatrace is on your shortlist, here is how the concepts map across, what moves easily, what needs rebuilding, and how to run the migration without a gap in monitoring.
Our position, before you read on. C4C Group is an official Dynatrace partner and we migrate organisations onto Dynatrace. We are also independent, so this guide is factual about AppDynamics: it is a supported product, and staying or moving within Splunk's portfolio are legitimate options too. We do not quote prices for either vendor.
An AppDynamics to Dynatrace migration is mostly a re-instrumentation and rebuild project, not a data move. Dynatrace OneAgent replaces the AppDynamics agents and discovers services and dependencies automatically, so much of what AppDynamics teams configured by hand, such as tiers and flow maps, Dynatrace builds for you. Health rules, dashboards and business transaction definitions need to be reviewed and rebuilt rather than copied. Run both platforms in parallel, move application by application, and time the switch to your AppDynamics renewal.
Why AppDynamics customers are reviewing now
Cisco completed its acquisition of Splunk in March 2024, and AppDynamics has since been renamed Splunk AppDynamics, as part of the Splunk Observability portfolio. Splunk says AppDynamics remains important for customers in self managed, air gapped and heavily regulated environments and that it will continue to support them, while positioning Splunk Observability Cloud as the cloud native platform, with tools to forward AppDynamics data to it and translate AppDynamics configuration. Splunk, unified observability; Splunk, AppDynamics joins Splunk.
To be clear, AppDynamics has not been announced as end of life. Splunk publishes version by version support dates, which is normal for any software. But many customers, especially on SaaS, see a decision coming either way, and if you are going to change platforms it makes sense to look at the whole market. That is where Dynatrace usually enters the conversation.
How AppDynamics concepts map to Dynatrace
| AppDynamics | Dynatrace | What changes |
|---|---|---|
| App, machine and database agents | OneAgent, one agent per host, plus database and extension monitoring | One agent instead of several, with automatic process and service detection |
| Applications, tiers and nodes | Services and process groups, discovered automatically | Less manual modelling, but naming and tagging rules need designing |
| Flow maps | Smartscape, a live dependency map across the full stack | Built automatically, from infrastructure up to services |
| Business transactions | Service endpoints and requests, captured in PurePath distributed traces | Critical transactions need re-identifying; there is no automatic one to one conversion |
| Health rules and policies | Automatic anomaly detection, custom alerts and problems, with notifications through workflows | Many static thresholds become unnecessary; the rest are rebuilt rule by rule |
| Information points and analytics | Business events and DQL queries over Grail | Similar outcomes, not like for like; redesign them |
| Dashboards | Dashboards and notebooks on DQL | Rebuilt, ideally slimmed down to the views people actually use |
Dynatrace documents PurePath® as combining distributed tracing with code level visibility, topology and metadata, captured automatically by OneAgent®. Dynatrace, PurePath distributed traces. Alerting on the latest platform works by grouping related events into problems, with notifications sent through workflows. Dynatrace, alerting and notifications.
No tool converts health rules safely without a human. Even Splunk's own migration assistant, which translates AppDynamics health rules into Splunk detectors, notes that automated translation does not remove the need for rule by rule review. Treat the migration as a chance to retire alerts nobody acts on, not as a copy exercise. Splunk, migrate health rules to detectors.
A migration plan that avoids a gap
- Inventory. List applications, agents, business transactions, health rules, dashboards and integrations, and mark which ones people actually use. Most estates carry a long tail that can be retired.
- Design. Agree host groups, service naming, tags and ownership in Dynatrace before installing anything, so cost allocation, alert routing and dashboards work from day one.
- Pilot. Deploy OneAgent alongside the AppDynamics agents on one or two representative applications. Compare what each platform sees and tune detection.
- Migrate in waves. Move application by application, rebuilding the alerts and dashboards that matter for each, and switch alert routing only when the team owning the application signs it off.
- Decommission. Remove AppDynamics agents and close out the contract at renewal, so you are not paying for two platforms longer than necessary.
Check agent coexistence for each technology during the pilot rather than assuming it: running two deep application agents on the same process is something to test, not take for granted. Dynatrace offers its own expert services for migrations from legacy monitoring tools, and partners such as C4C can run the programme end to end.
If you run AppDynamics on premises
Self managed and air gapped AppDynamics customers should look carefully at deployment options. Dynatrace offers a self managed edition, Dynatrace Managed, but the newer generative and agentic AI capabilities are only available on Dynatrace SaaS. Dynatrace, agentic and generative AI FAQ. If you have a hard requirement to keep monitoring data on premises, confirm which capabilities you need are available in Managed before you commit, and be honest about whether a move makes sense at all.
Licensing on each side
AppDynamics is licensed on infrastructure, with packages such as Infrastructure Monitoring, Premium and Enterprise metered on CPU cores, plus options for end user monitoring, synthetics and analytics. Splunk AppDynamics, infrastructure based licensing. Dynatrace is bought through the Dynatrace Platform Subscription, one annual commitment drawn down across any capability at rate card rates. Size the Dynatrace commitment from what the pilot shows you will consume, and line up the start date with your AppDynamics renewal so the overlap is short and planned. Dynatrace licensing from C4C.
How we help
We are an official Dynatrace partner and we run migrations onto Dynatrace: inventory, design, pilot, waves and decommissioning, timed to your contract dates. Our people spent decades on the vendor side, so we also handle the commercial side, sizing the Dynatrace commitment properly and making sure you are not paying for two platforms for longer than you need to. Migration to Dynatrace.
Planning a move off AppDynamics?
Tell us roughly how many applications and hosts you monitor, whether you run AppDynamics SaaS or on premises, and when it renews. We will give you a straight view on fit and a migration plan with realistic timings. We supply, implement and migrate to Dynatrace.
Prefer email? Reach us directly at hello@c4cgroup.co.uk.
Frequently asked questions
Is AppDynamics end of life?
No. AppDynamics, now called Splunk AppDynamics, has not been announced as end of life. Splunk publishes support dates for individual versions and components, and says it will continue to support AppDynamics, particularly for self managed and air gapped customers, while positioning Splunk Observability Cloud as its cloud native platform.
What is the best alternative to AppDynamics?
For large, complex estates we usually recommend Dynatrace, because OneAgent discovers services and dependencies automatically and its causal AI points to root cause. Splunk Observability Cloud is the natural option inside Cisco and Splunk's own portfolio. The right choice depends on your estate, deployment needs and contract position.
How long does an AppDynamics to Dynatrace migration take?
It depends on the number of applications and how much custom configuration you carry. A pilot on one or two applications is usually the first step, followed by migration in waves. Plan it backwards from your AppDynamics renewal date so the two platforms overlap for as short a time as possible.
Can AppDynamics health rules be converted to Dynatrace automatically?
Not safely without review. Dynatrace detects many anomalies automatically, so a lot of static health rules are no longer needed, and the rest should be rebuilt as custom alerts rule by rule. Even Splunk's own tool for translating health rules says automated translation does not remove the need for rule by rule review.
What replaces AppDynamics business transactions in Dynatrace?
Dynatrace captures every request end to end in PurePath distributed traces and groups them by service and endpoint. Your critical business transactions need re-identifying in Dynatrace and given their own alerting and dashboards; there is no automatic one to one conversion.