Migrate from Datadog
Switch to TigerOps without losing a single metric, dashboard, or alert. Our migration team handles the full transition in days — and you'll spend 40–70% less than Datadog when it's done.
TigerOps vs. Datadog
How the Migration Works
Export Your Datadog Config
Run our one-line export script to pull your Datadog dashboards, monitors, SLOs, and alert policies via the Datadog API. Takes under 2 minutes.
Import into TigerOps
Upload the export bundle to TigerOps. Our migration engine automatically converts Datadog dashboards to TigerOps format and imports all monitors as alert policies.
Run Both in Parallel
Install the TigerOps agent alongside the Datadog agent. Run both for 1–2 weeks to verify parity. Your Datadog contract continues — no gaps in monitoring.
Cut Over & Cancel Datadog
Once you verify TigerOps has full coverage, uninstall the Datadog agent. Our team provides a cutover checklist and is on-call for your go-live day.
Export Your Datadog Config
Run this script to export your Datadog dashboards, monitors, and SLOs for import into TigerOps.
#!/bin/bash
# TigerOps — Datadog Migration Export Script
# Requires: DD_API_KEY and DD_APP_KEY environment variables
DD_SITE="${DD_SITE:-datadoghq.com}"
OUTPUT_DIR="./dd-export-$(date +%Y%m%d)"
mkdir -p $OUTPUT_DIR
echo "[1/4] Exporting dashboards..."
curl -s "https://api.${DD_SITE}/api/v1/dashboard" \
-H "DD-API-KEY: ${DD_API_KEY}" \
-H "DD-APPLICATION-KEY: ${DD_APP_KEY}" \
| jq '.' > "${OUTPUT_DIR}/dashboards.json"
echo "[2/4] Exporting monitors..."
curl -s "https://api.${DD_SITE}/api/v1/monitor" \
-H "DD-API-KEY: ${DD_API_KEY}" \
-H "DD-APPLICATION-KEY: ${DD_APP_KEY}" \
| jq '.' > "${OUTPUT_DIR}/monitors.json"
echo "[3/4] Exporting SLOs..."
curl -s "https://api.${DD_SITE}/api/v1/slo" \
-H "DD-API-KEY: ${DD_API_KEY}" \
-H "DD-APPLICATION-KEY: ${DD_APP_KEY}" \
| jq '.' > "${OUTPUT_DIR}/slos.json"
echo "[4/4] Packaging export bundle..."
tar -czf "${OUTPUT_DIR}.tar.gz" $OUTPUT_DIR
echo "Export complete: ${OUTPUT_DIR}.tar.gz"
echo ""
echo "Upload this file to TigerOps > Settings > Migration Import"Common Migration Questions
How long does a Datadog-to-TigerOps migration typically take?
For teams with under 100 hosts and 50 dashboards, migration is typically complete in 3–5 business days. Larger environments with custom integrations and complex monitors may take 2–3 weeks. Our dedicated migration team handles the heavy lifting.
Will my existing Datadog dashboards carry over?
Yes. TigerOps's migration tool imports Datadog dashboard JSON via the API and auto-converts widget types, queries (from DogStatsD/Metrics to TigerOps PromQL-compatible format), and layout. Most dashboards migrate with 90–95% fidelity. Our team manually fixes the remainder.
Can I run TigerOps and Datadog at the same time during migration?
Yes — and we strongly recommend it. Run both agents in parallel for 1–2 weeks so you can compare metric values, verify alert coverage, and train your team on TigerOps before cutting over. There is no downtime required.
What happens to my existing Datadog integrations?
TigerOps supports 450+ integrations — nearly all of which overlap with Datadog's catalog. AWS, GCP, Azure, Kubernetes, Docker, all major databases, and messaging queues are covered. Custom StatsD and Prometheus integrations also migrate transparently.
How much can I expect to save vs. Datadog?
Most teams switching from Datadog to TigerOps save 40–70% on their observability bill. The biggest savings come from TigerOps's per-host pricing model, which eliminates Datadog's per-metric, per-log, and per-user charges that typically 3–5x the nominal host price.
Move Off Datadog in Days, Not Months
Get a dedicated migration engineer, a full dashboard and monitor migration, and a guarantee of no monitoring gaps during your cutover.
No credit card required. Migration support included on all paid plans.