Migrate into Datadog with an inventory, field map, pilot import, dual-run week, and validation — so history survives and operators trust the new system.
Migrate into Datadog with an inventory of monitors, dashboards, SLOs, and log indexes, a field map, a pilot import, a dual-run week, and validation with the people who live in the data — so history survives and the team trusts the new system.
Import/data-move surfaces and vendor migration walkthroughs for Datadog when available — unrelated product tour footage is omitted.
Vendor walkthrough of data move / UI migration surfaces. Validate against your own export and mapping checklist.
This video is hosted on YouTube
This content is hosted by YouTube. The player loads only after you allow marketing cookies.
Official vendor video
How Datadog presents the product in an official vendor video.
Verified captures from Datadog's product interface.
Official Datadog Open Graph marketing visual from datadoghq.com — not a SoftwareGlimpse lab screenshot.
Official Datadog marketing UI asset (overview alias)
https://www.datadoghq.com/ · Checked 2026-08-18
Full product screenshots and evidence live on the Datadog research page.
List monitors, dashboards, SLOs, and log indexes. Map required fields and owners. Never invent list prices here — confirm seats, hosts, ingest, and quote terms on /pricing/datadog/. Worked example: Northline Platform (two services in production) discovers duplicate employee IDs in the spreadsheet before the first import — and fixes identity before volume.
Import one site, one role, or one team. Run instrument one service, see a metric, trace, or log, and page or ticket from a real signal on the pilot set. Worked example: Northline Platform (two services in production) will not schedule a cutover until the pilot can an engineer finds a failing trace without a Datadog org admin.
Run old and new in parallel for a week. Spot-check records sceptic users care about, then freeze the legacy source. Worked example: Northline Platform (two services in production) keeps the old export for tickets, repos, or monitors until Datadog matches for seven consecutive days.
Bring these questions to every demo
Ask vendors to show the workflow live, not just describe it.
List users, historical records, templates, and integrations that must survive migration. Mark nice-to-have exports you can leave behind.
Worked example: SRE/platform teams needing unified infra + APM + logs migrates active records only and archives the rest as read-only exports.
Keep the old system read-only until Datadog passes non-admin proof. Name a rollback owner and maximum parallel window.
Worked example: SRE/platform teams needing unified infra + APM + logs caps parallel run at two weeks with daily checkpoint notes.
Reconcile user counts, role permissions, and a sample of migrated records. Research lists Aws, Azure, Google Cloud, and Slack for Datadog. Confirm which are native vs API before go-live.
List users, historical records, templates, and integrations that must survive migration. Mark nice-to-have exports you can leave behind.
Worked example: SRE/platform teams needing unified infra + APM + logs migrates active records only and archives the rest as read-only exports.
Keep the old system read-only until Datadog passes non-admin proof. Name a rollback owner and maximum parallel window.
Worked example: SRE/platform teams needing unified infra + APM + logs caps parallel run at two weeks with daily checkpoint notes.
Reconcile user counts, role permissions, and a sample of migrated records. Research lists Aws, Azure, Google Cloud, and Slack for Datadog. Confirm which are native vs API before go-live.
List users, historical records, templates, and integrations that must survive migration. Mark nice-to-have exports you can leave behind.
Worked example: SRE/platform teams needing unified infra + APM + logs migrates active records only and archives the rest as read-only exports.
Keep the old system read-only until Datadog passes non-admin proof. Name a rollback owner and maximum parallel window.
Worked example: SRE/platform teams needing unified infra + APM + logs caps parallel run at two weeks with daily checkpoint notes.
Reconcile user counts, role permissions, and a sample of migrated records. Research lists Aws, Azure, Google Cloud, and Slack for Datadog. Confirm which are native vs API before go-live.
Confirm the qualifying plan, non-admin proof, and integration owners in writing. Store quotes next to /pricing/datadog/ and the evaluation scorecard so finance can audit the same assumptions at renewal.
Name the job, the qualifying Datadog configuration, and what you are not buying yet. If stakeholders cannot explain why an alternative lost, the trial was not fair.
Only if the dataset is tiny and reversible. Most SMB/mid teams regret skipping a week of parallel use.
Import active records first. Archive messy history as files rather than poisoning the new system of record.
Have more questions? Contact our support team.
Want clearer software shortlists? Get buying guides and comparisons by email.
Newsletter coming soon.