Migration Guide

Switch to NotifyHero in about 15 minutes. We import your schedules, escalation policies, and integrations.

---

Before You Start

Gather from your current tool:

• On-call schedules (rotation members, handoff times, timezone)
• Escalation policies (levels, timeouts, targets)
• Integration webhook URLs (which monitoring tools are connected)
• Team structure (who owns which services)
• Notification preferences (per-user channels and rules)

---

Step 1: Create Your Organization

1. Sign up at app.notifyhero.com
2. Set your organization name and timezone
3. Invite your team (bulk CSV upload available)

---

Step 2: Import Schedules

Automatic Import

Go to Settings → Migration → Import Schedules.

Upload a CSV or JSON export from your current tool:

schedule_name,timezone,rotation_type,handoff_time,members
"Backend Primary",America/New_York,weekly,Monday 09:00,"alice@co.com,bob@co.com,carol@co.com"
"Backend Backup",America/New_York,weekly,Monday 09:00,"dave@co.com,eve@co.com"

NotifyHero creates the schedules with all rotation details.

Manual Setup

If you prefer to start fresh, create schedules manually at On-Call → Schedules → New Schedule. See Schedules.

---

Step 3: Import Escalation Policies

Go to Settings → Migration → Import Policies.

Upload your escalation policy configuration:

{
  "policies": [
    {
      "name": "Backend Escalation",
      "levels": [
        {"target": "Backend Primary", "type": "schedule", "timeout_minutes": 5},
        {"target": "Backend Backup", "type": "schedule", "timeout_minutes": 10},
        {"target": "vp-eng@co.com", "type": "user", "timeout_minutes": 15}
      ],
      "repeat": true
    }
  ]
}

---

Step 4: Reconnect Integrations

For each monitoring tool:

1. Create a service in NotifyHero
2. Add the integration (Datadog, CloudWatch, Prometheus, etc.)
3. Copy the new webhook URL
4. Update your monitoring tool to point to the NotifyHero URL

Tip: Run both tools in parallel during migration. Point your monitoring tool at both webhook URLs simultaneously. Remove the old one after you've verified NotifyHero is working correctly.

---

Step 5: Configure Notifications

Each team member sets their notification preferences:

1. Go to Profile → Notification Rules
2. Add contact methods (phone, email, Slack)
3. Configure high-urgency and low-urgency rules
4. Set quiet hours

---

Step 6: Verify

1. Send a test event to each service
2. Confirm notifications arrive on the right channels
3. Verify escalation works (let a test alert go unacknowledged)
4. Check that schedules show the correct on-call person

---

Parallel Running

We recommend running both tools simultaneously for 30 days:

• Both tools receive alerts from your monitoring stack
• Compare: are the same alerts showing up in both?
• Verify escalation behavior matches your expectations
• When confident, remove the old tool's webhooks

Our guarantee: If a single alert is missed during the parallel period, we extend your trial by 90 days.

---

Data You Can Import

Data	Import Method
On-call schedules	CSV, JSON, or API
Escalation policies	JSON or API
Team structure	CSV or SCIM
User preferences	Each user configures individually
Historical incidents	API (for analytics continuity)
Integrations	Re-point webhooks (no data transfer needed)

---

Data You Don't Need to Import

• Monitoring tool configs — these stay in your monitoring tools; only the webhook URL changes
• Runbooks — recreate or link to external docs (Notion, Confluence, wiki)
• Status pages — create fresh pages with your current component list

---

Need Help?

Migration support is available on all plans:

• Free/Team: Email support@notifyhero.com
• Business: Priority support, dedicated migration help
• Enterprise: Dedicated migration engineer, white-glove onboarding