New Relic to Datadog Migration

Point this agent at your New Relic-instrumented codebase and ask it to plan your migration to Datadog.

What it does

1. Map your New Relic footprint: agent configs per language, custom instrumentation call sites (newrelic.* APIs), dashboards and their NRQL queries, alert policies and conditions, synthetics, and log forwarding.
2. Plan a service-by-service migration with a parallel-run window, an alert-policy migration order, and a naming/tagging convention mapping so dashboards stay comparable across both platforms.
3. Scaffold the Datadog side: Agent + tracer config per language, translated custom-instrumentation calls, NRQL-to-Datadog query translations, and monitors + dashboards as Datadog API JSON payloads.
4. Sandbox — create the monitors and a dashboard in a Datadog sandbox org via the API, submit a sample metric, confirm they render and evaluate, and report PASS/PARTIAL/FAIL evidence.

Prerequisites

• DD_API_KEY — Datadog API key for a sandbox org
• DD_APP_KEY — Datadog application key for the same org
• DD_SITE — your Datadog site, for example datadoghq.com or datadoghq.eu
• NEW_RELIC_API_KEY — optional; enables read-only NerdGraph export of dashboards and alert conditions from the source account

Current scope

This solution migrates instrumentation config, custom instrumentation call sites, monitors, and dashboards. It does not migrate historical telemetry data (retention windows restart in Datadog), does not port New Relic synthetics scripts automatically (each scripted check needs its own translation pass), and does not attempt to auto-translate every NRQL query — complex facet and funnel constructs are flagged for redesign instead.