Skip to content

Commit aa576a4

Browse files
authored
Apply suggestion from @domalessi
1 parent a0c37d9 commit aa576a4

File tree

1 file changed

+3
-1
lines changed

1 file changed

+3
-1
lines changed

content/en/incident_response/on-call/guides/migrating-from-your-current-providers.md

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -72,7 +72,9 @@ Before you start configuring Datadog On-Call, review the concept of [Teams][4].
7272

7373
After reviewing the team model and mapping your existing assets, you're ready to configure Datadog On-Call to reflect your desired structure.
7474

75-
<div class="alert alert-info">If you're migrating from PagerDuty or OpsGenie, Datadog provides dedicated migration tools that can help you selectively import schedules and escalation policies. Use the <a href="/incident_response/on-call/guides/migrate-your-pagerduty-resources-to-on-call">PagerDuty migration tool</a> or the <a href="/incident_response/on-call/guides/migrate-your-opsgenie-resources-to-on-call">OpsGenie migration tool</a> during setup to reduce manual effort and avoid migrating unused configurations.</div>
75+
<div class="alert alert-info">
76+
If you're migrating from PagerDuty or OpsGenie, use the <a href="/incident_response/on-call/guides/migrate-your-pagerduty-resources-to-on-call">PagerDuty migration tool</a> or the <a href="/incident_response/on-call/guides/migrate-your-opsgenie-resources-to-on-call">OpsGenie migration tool</a> during setup to selectively import schedules and escalation policies and avoid migrating unused configurations.
77+
</div>
7678

7779
During setup, be sure to:
7880

0 commit comments

Comments
 (0)