Overview

Follow this migration workflow to rebuild your OpsGenie on-call structure in Datadog, team by team. Datadog uses your existing OpsGenie schedules and escalation policies as building blocks, and you can review, map, and customize each resource before it goes live.

By importing only current, relevant OpsGenie data, you avoid bringing outdated or unused configurations into Datadog and start with a concise, maintainable setup.

Note: This is not a bulk migration tool. You select and map individual teams, escalation policies, schedules, and users through a wizard-style workflow.

Prerequisites

1. Configure the OpsGenie integration in Datadog and connect a valid account.
2. Confirm that your Datadog user account has on_call_write and teams_manage permissions.

What gets migrated

The following table shows how OpsGenie resources map to Datadog On-Call resources:

Migration steps

The migration follows a six-step wizard-style process in Datadog. Complete all steps in order within the same migration wizard.

Step 1: Select team to migrate

1. Go to the On-Call Teams list and select Add Team to On-Call > Import team from OpsGenie.
2. If you have multiple regions configured, select your OpsGenie account’s region from the dropdown.
3. Datadog loads all your OpsGenie teams in a searchable, paginated list. Select the team to migrate, then select Next. A preview pane shows the team’s members and settings.

Note: If a team was previously imported, Datadog indicates this.

Step 2: Map the team

1. Choose one of the following mapping options:

   • Map to the Datadog team with the same name.
   • Map to a different Datadog team that you select.
   • Create a new team. Enter a team name to create a Datadog team based on the structure and members of the OpsGenie team.

2. When the mapping is correct, select Next.

Step 3: Select escalation policy to migrate

1. Browse your OpsGenie escalation policies. You can filter policies by team.
2. Select an escalation policy to import. The wizard displays the full policy details, including rules, recipients, and schedules.

Step 4: Map users

Datadog automatically matches OpsGenie users to Datadog users by email address. For unmapped users, take one of the following actions:

• Map them to an existing Datadog user
• Invite them to Datadog (the migration wizard sends an email invitation)
• Exclude them if they no longer need access

Note: You cannot save the escalation policy until all users are mapped, invited, or explicitly excluded.

Step 5: Review migrated schedules

If the escalation policy references OpsGenie schedules, Datadog automatically migrates them to Datadog On-Call. The migration includes:

• Rotations: Converted to Datadog schedule layers in reverse order.
• Participants: Automatically matched to Datadog users.
• Time restrictions: time-of-day and weekday-and-time-of-day restrictions are preserved.
• Time zones: Time zone configuration is preserved.

Step 6: Review and save

1. Review the migrated escalation policy. You can modify the following fields:

   • Escalation step delays
   • Notification targets (users, teams, and schedules)
   • Retry behavior
   • Auto-resolution settings

2. When all fields are complete and all users, teams, and schedules are mapped, select Save. Datadog creates the escalation policy under your On-Call team.

Known limitations

• Escalation conditions: Only if-not-acked escalation conditions are supported. The if-not-closed condition is not supported and is not migrated.
• Rotation participants: Only user-type rotation participants are supported. Team-type and escalation-type participants are not migrated.

Validation and testing

Before relying on migrated resources for production incidents:

• Verify schedule coverage: Check that all migrated schedules have proper coverage with no gaps. Go to On-Call Schedules and review each schedule’s timeline.
• Test escalation policies: Use the Manual Page feature to send a test page and verify that escalation policies escalate correctly and notify the right people.
• Check user mappings: Verify that all users are correctly mapped and can receive notifications through their preferred channels (email, SMS, push, voice).
• Review team ownership: Confirm that each escalation policy is owned by the correct Datadog team.
• Validate time restrictions: If your schedules use time restrictions, verify that they apply correctly by checking on-call coverage during restricted and unrestricted periods.

Troubleshooting

OpsGenie integration not appearing

If the OpsGenie import option does not appear during team setup:

1. Verify that the OpsGenie integration is configured in Datadog.
2. Verify that at least one account is configured in the integration tile.
3. Confirm you have the required on_call_write and teams_manage permissions.

Users not matching automatically

If OpsGenie users are not automatically matched to Datadog users:

1. Verify that email addresses match exactly between OpsGenie and Datadog.
2. Confirm that the Datadog users are active.
3. If automatic matching still fails, add users manually or invite them to Datadog.

Schedule rotations not matching

If migrated schedule rotations do not match your OpsGenie schedules:

1. Check that all rotation participants are user-type (not team-type or escalation-type).
2. Verify that time zones are correctly configured in both OpsGenie and Datadog.
3. Review time restrictions to confirm they were migrated correctly.

Escalation policy not saving

If the escalation policy fails to save:

1. Confirm all users are mapped or excluded (no pending invites).
2. Verify all referenced schedules were created successfully.
3. Check that all escalation step delays meet the minimum requirement (one minute).
4. Confirm you have the on_call_write and teams_manage permissions.

Further reading

お役に立つドキュメント、リンクや記事:

On-Call DocumentationDOCUMENTATION OpsGenie IntegrationDOCUMENTATION