Migrate from Datadog

Complete guide for migrating your Datadog setup to groundcover.

Prerequisites

Access required:

• Admin role in groundcover

• Datadog API key and application key with read permissions

Datadog application key scopes:

• dashboards_read - List and retrieve dashboards

• monitors_read - View monitors

• metrics_read - Query timeseries data

• integrations_read - View AWS, GCP, Azure integrations

Create a migration project

Navigate to Migrations from the main page.

1. Click Start on the Datadog card

2. Enter a project name (e.g., "Production Migration", "US5 Migration")

3. Click Create

Tip: Use descriptive names. You can run multiple migration projects for different environments or teams.

Fetch assets from Datadog

Provide your Datadog credentials:

Datadog site

The domain of your Datadog console. The options are:

• US1 - app.datadoghq.com

• US3 - us3.datadoghq.com

• US5 - us5.datadoghq.com

• EU1 - app.datadoghq.eu

• AP1 - ap1.datadoghq.com

You can find your Datadog site by looking at your console's URL.

API key

A regular Datadog API key. Find this under Organization Settings → API Keys.

Application key

Create one under Organization Settings → Application Keys with the required scopes listed above.

Important: groundcover does not store these keys. Assets are fetched, then the keys are discarded.

Click Fetch Assets. This typically takes 10 seconds depending on the number of assets.

Review migration summary

Once fetched, you see:

• Progress overview: Total assets discovered and their support status

• Asset cards: Monitors, Dashboards, Data Sources, etc

• Support breakdown: How many assets are fully supported, partial, or unsupported

The overview shows everything we found in your Datadog account and what we'll bring over.

Migrate data sources

Start with adding missing data sources to ensure relevant data is in place and ease the evaluation process of monitors and dashboards.

What we detect

Based on the full set of metrics in use by your dashboards and monitors, we map the list of data sources that should be added.

For each, we show the number of monitors and dashboards that rely on this data source.

Clicking on any data source will show the list of monitors and dashboards to provide more context for users.

Clicking on connect data source will show a wizard explaining how to connect a data source. Users will need to provide the connection details for the data source. Whenever data mapping is required, it will already be populated. For example, in case there is a need to connect cloudwatch, only the user AWS namespaces will be selected by default.

Migrate monitors

Once data sources are ready, migrate your monitors.

Monitor status indicators

• ✓ Supported: Fully compatible. Migrate as-is.

• ⚠ Partial: Migrates with warnings. Review before installing.

• ✗ Unsupported: Requires manual attention.

Review warnings

For monitors with warnings, click View Warnings:

• See what adjustments were made

• Understand query translations

• Get recommendations for post-migration verification

Warnings don't block migration — they inform you of changes so you can verify behavior.

Migrate monitors

Single monitor:

1. Preview the monitor

2. Click Migrate

3. Monitor installs immediately

Bulk migrate:

1. Select multiple monitors using checkboxes

2. Click Migrate Selected

3. All install in parallel

Migrated monitors appear instantly in Monitors → Monitor List.

Migrate dashboards

Dashboards preserve:

• Layout and widget positions

• Query logic and filters

• Time ranges and visualization settings

• Colors and formatting

Check out the dashboard preview to confirm the migration worked and that all your assets came through successfully.

Migrate dashboards

Click Migrate to install. Dashboards appear under Dashboards immediately.

Tip: Migrate critical dashboards first. Verify queries return expected data before bulk migrating.