Migration to Dynatrace

Moving to Dynatrace without losing sight of anything

Consolidation onto Dynatrace usually fails in the migration, not the selection. We plan the move so both tools run in parallel for as long as they need to, dashboards and alerts are rebuilt rather than half converted, and the old contract ends when you are ready, not before.

Official Dynatrace partner, and an independent adviser

How do you migrate to Dynatrace?

A migration to Dynatrace runs in four stages: inventory what the current tools actually do, deploy Dynatrace alongside them, rebuild the dashboards, alerts and reports people rely on, and switch off the old tool once Dynatrace has proved it sees everything the old one did. Running both in parallel for a period is normal and is what makes the move safe.

Dynatrace has its own migration routes for some tools, including AppDynamics and a log migration service for Splunk. For others, such as Datadog, New Relic and Elastic, the work is mostly rebuilding rather than converting, because dashboards and alert logic rarely translate one to one. Grafana can query Dynatrace through a data source plugin, which helps teams keep familiar dashboards during the transition.

Migration to Dynatrace

Where we move you from

AppDynamics

Application performance monitoring moved onto OneAgent, with business transactions and health rules rebuilt as Dynatrace services, alerting and dashboards.

Splunk

Logs and alerting moved into Grail through OpenPipeline, with searches rebuilt in DQL and retention designed for what you actually query.

Datadog and New Relic

Infrastructure, APM and log monitoring consolidated onto one platform, with dashboards and monitors rebuilt around Smartscape dependencies.

Elastic, Prometheus and Grafana

Open source and self managed stacks brought onto a managed platform, keeping OpenTelemetry instrumentation and Grafana dashboards where they still earn their place.

Older Dynatrace

Classic dashboards, USQL tiles and management zones moved onto the latest Dynatrace platform, where they need rebuilding rather than converting.

What you get

Deliverables you can hold us to

We are an independent UK consultancy and an official Dynatrace partner. Our people spent decades on the vendor side, so we know how enterprise platforms are sold, sized and deployed, and we use that on your side of the table.

The honest part

Not everything converts automatically, whatever any tool promises. Dashboards and alert logic usually need rebuilding, and that is where migrations overrun. We plan for it from day one, and we time the cutover to your existing contracts so you are never paying for two tools longer than you need to, or forced into an extra renewal.

Talk to us

How it works when you get in touch

  1. Tell us what you run today, what each tool is used for, and when each contract renews.
  2. We inventory the dashboards, alerts and integrations that matter and build a migration plan timed to your contract dates.
  3. We run Dynatrace in parallel, rebuild what people rely on, and retire the old tool once nothing is lost.

We reply within one working day. Prefer email? Write to us at hello@c4cgroup.co.uk.

Prefer email? Write to us at hello@c4cgroup.co.uk.

Questions

Migration to Dynatrace: frequently asked questions

Can we migrate from AppDynamics to Dynatrace?

Yes. Dynatrace has a published migration route from AppDynamics. The agents are replaced by OneAgent, and business transactions, health rules and dashboards are rebuilt as Dynatrace services, alerting and dashboards. We plan the parallel run and time the switch to your AppDynamics contract.

How do we move logs from Splunk to Dynatrace?

Logs are ingested into Grail through OpenPipeline, and Dynatrace offers a log migration service for Splunk. Searches and alerts are rebuilt in Dynatrace Query Language. It is also the right moment to decide which logs are worth keeping and for how long, because log retention drives cost on any platform.

Will our dashboards and alerts convert automatically?

Mostly not. Dashboards and alert logic rarely translate one to one between tools, so they are rebuilt. That is normal and is the part a good migration plan budgets time for.

Do we have to switch everything at once?

No. Running Dynatrace in parallel with the existing tools is the safe way to migrate. Each tool is retired once Dynatrace has shown it sees everything the old tool did, and ideally in line with that tool’s contract end date.

Can we keep using Grafana?

Yes, where it helps. Grafana has a data source plugin that can query Dynatrace, so teams can keep familiar dashboards during the move and retire them gradually.

More Dynatrace services from C4C