HowlOps
FeaturesHow it worksPricingIntegrationsDocsChangelogContactLog inStart free
DOCS

Migrate from Opsgenie

One-click import of your Opsgenie heartbeats, on-call schedules and escalation policies into HowlOps.

Overview

HowlOps imports your Opsgenie setup directly over the Opsgenie API — no CSV, no hand-recreating. Point it at a read-only key, review what maps to what, and import. Nothing in Opsgenie is ever modified; the import only reads.

Time: a few minutes Prerequisites: an Opsgenie API key (read access) and a HowlOps account

What gets imported

OpsgenieHowlOps equivalentNotes
HeartbeatHeartbeatInterval converted to seconds (minutes/hours/days)
Schedule + rotationsOn-call schedule + layersEach rotation becomes a layer
Escalation policyEscalation policyEach rule becomes a step
User / team(used only to resolve names)Never created — see below

What is not imported, and why

  • Uptime monitors — Opsgenie does not have them.
  • People who aren't in your HowlOps workspace. A rotation participant or escalation recipient is matched to a HowlOps user by email. If there's no match, that participant is skipped (with a reason in the report) — the import never creates users. Invite your team to HowlOps first, then re-run the import to fill in the on-call members.
  • Whole-team escalation rules (notify: users / admins / all) and any recipient type other than an individual user or a schedule. Those rules are skipped with a reason.
  • Hourly rotations — HowlOps rotations are daily or weekly, so an hourly rotation is imported as weekly (noted in the report).

Step 1: Create a read-only Opsgenie API key

In Opsgenie: Settings → API key management → Add new API integration (or use an existing API key). A read-only key is enough — the import only reads.

Note your region: Opsgenie runs a US stack (api.opsgenie.com) and an EU stack (api.eu.opsgenie.com). You'll pick the matching region in HowlOps.

Step 2: Run the import

  1. In HowlOps, go to Settings → Import (or start it from the onboarding wizard: "Already using Opsgenie or UptimeRobot? Import instead").
  2. Choose Opsgenie, select your region, and paste your API key.
  3. Click Load items. HowlOps fetches your heartbeats, schedules and escalation policies and shows a preview table: what each object is, and what it maps to. Rows that can't be imported are shown in yellow with the reason.
  4. Tick the items you want, then click Import. A progress bar shows Importing 12/40…; a problem with one item never stops the rest.
  5. When it finishes you get a summary — 37 imported, 3 skipped — and a Download report button (a CSV of every item and its outcome).

Step 3: Fill in on-call members

If some rotation participants were skipped because they weren't in your workspace yet:

  1. Invite them under Settings → Members & roles.
  2. Re-run the import. It's idempotent — already-imported schedules and policies are skipped, and only the newly resolvable members are added. You never get duplicates.

Re-running is always safe

Every import is idempotent. HowlOps records which Opsgenie object created which HowlOps resource, so a second run updates or skips rather than duplicating. If the import is interrupted (for example a deploy restarts the service mid-run), just run it again — items already imported are skipped.

What's next

Was this page helpful?