New Relic migration guide

Move off New Relic to AllStak

APM, alerts, the infrastructure agent, and browser monitoring all have direct AllStak equivalents. The migration is a staged sprint, not a rewrite.

Start free AllStak vs New Relic

What moving off New Relic actually takes

Move New Relic APM to supported application instrumentation, map NRQL alert conditions to AllStak rules, and replace proprietary infrastructure collection with standard Alloy, OpenTelemetry, or Prometheus collection.

AllStak gives you the parts of New Relic most teams actually open every day — application monitoring, errors, distributed tracing, infrastructure, logs, uptime — in one platform with flat pricing and a dashboard that works in Arabic and English. This New Relic migration guide covers the honest path, including the fact that your historical NRDB data stays where it is.

Why teams move off New Relic

Three drivers come up again and again in New Relic migrations — billing, consolidation, and regional fit.

Pricing that does not scale with headcount

New Relic charges for data ingest by the GB and for full-platform users by the seat. AllStak plans are flat — the whole team can see production without each engineer becoming a line item.

Everything in one place, sized for real teams

Errors, logs, traces, uptime, infrastructure, and session replay live in one AllStak project. Less surface to learn, fewer places for an incident's context to hide.

Saudi residency, SAR pricing, Arabic UI

For KSA and GCC teams, AllStak offers Saudi data residency, SAR billing, and a fully Arabic dashboard alongside English — practical advantages no global APM vendor matches.

How to move off New Relic, step by step

Six steps. The example below uses the official Sentry Python SDK; the same DSN-based flow applies to every supported runtime.

  1. 1

    Create an AllStak project and copy its DSN

    Create a project, open Get started, and copy its AllStak DSN. It is the ingest destination for the official Sentry SDK.

  2. 2

    Remove the New Relic agent from the service

    Drop the newrelic package and its config file or env vars from the first service you are migrating. Keep the New Relic infrastructure agent on hosts until the application side has proven itself — staged beats big-bang.

  3. 3

    Install the official Sentry SDK for your stack

    Install sentry-sdk from PyPI and initialize it with the AllStak project DSN. Use the official integration for FastAPI, Flask, or Django.

    terminal
    pip install sentry-sdk
  4. 4

    Set release and environment at startup

    Initialize with environment and release so error grouping and deploy tracking work from the first event — the role your New Relic deployment markers played. For browser JavaScript apps, upload source maps as part of each release.

    main.py
    import os
import sentry_sdk

sentry_sdk.init(
    dsn=os.getenv("ALLSTAK_DSN"),
    environment=os.getenv("APP_ENV", "production"),
    release=os.getenv("APP_VERSION"),
)
  5. 5

    Rebuild NRQL alert conditions as notification rules

    Inventory the alert conditions that actually page people and recreate them as AllStak alert and notification rules. Slack, email, webhooks, PagerDuty, Opsgenie, and Telegram are supported destinations.

  6. 6

    Run both for a sprint, then cancel New Relic

    Let AllStak and New Relic collect side by side for one sprint. Verify errors, traces, host metrics, and every alert route on real traffic, swap the infrastructure agent host by host, then cancel the New Relic subscription.

New Relic concepts, mapped to AllStak

Every daily-driver New Relic surface has a direct AllStak equivalent — use this when rewriting runbooks.

New RelicAllStak
APMApplication monitoring
NRQL alertsAlert rulesDefined in the dashboard rather than a query language, and routed via notification rules.
Infrastructure agentGrafana Alloy / OpenTelemetryStandard collectors for host, process, and container telemetry.
Errors inboxErrors
Distributed tracingDistributed tracing
Browser monitoringBrowser SDK + web vitals

New Relic migration FAQ

Can I import my historical New Relic data?

No. There is no automated importer — historical APM, infrastructure, and log data stays in New Relic. You start collecting fresh the moment AllStak goes live, which is why the recommended cutover runs both tools in parallel for a sprint.

What replaces NRQL in AllStak?

Search and filtering across errors, logs, and traces, plus alert rules defined in the dashboard. You lose a general-purpose query language; you gain alert definitions any teammate can read and edit without learning a DSL.

Does AllStak support OpenTelemetry?

Yes — AllStak accepts OpenTelemetry data, so services already instrumented with OTel for New Relic can be repointed rather than re-instrumented. See the OpenTelemetry feature page for setup details.

How long does the whole migration take?

Plan one sprint. The SDK swap per service is hours; the agent swap per host is minutes; the calendar time goes to the parallel run that lets you verify alert coverage on real production traffic before you cancel.

Do my New Relic dashboards carry over?

No — dashboards are not imported. AllStak ships ready-made views for errors, requests, traces, logs, and hosts, so start from those and only rebuild the custom dashboards your team genuinely opened.

Explore more

Ready to move off New Relic?

Start free at app.allstak.sa, instrument one service, and judge AllStak against New Relic on your own production traffic.

Start free View pricing