Migrate from Grafana OnCall OSS

Rotations and escalation steps here can only name people on your team, and the importer matches OnCall users to them by email. Invite your responders first. The preview lists anyone it could not match, so nobody is silently dropped from a rotation.

In Grafana OnCall, open Settings, copy the API URL and create an API token. A Grafana service account token works too, with your Grafana URL in the extra field. The importer reads users, schedules, shifts, escalation chains and escalation policies, writes nothing to OnCall, and uses the token only for the import, so you are asked for it again on the import step. Your OnCall server has to be reachable from the public internet for the import to read it.

In your dashboard, open Import from another service and use Import from Grafana OnCall. Each daily or weekly rolling shift becomes a rotation, starting from the person OnCall would start from, with its handoff time and time zone. Each escalation chain becomes an escalation policy: waits fold into the step before them, a step that notifies whoever is on call from a schedule pages that rotation, and a repeat step repeats the policy five times, as OnCall does. On-call starts on Pro, so the import runs on Pro and Business, by an owner or admin. Monitors are separate and free for 10.

OnCall received your Grafana alerts; here an inbound alert URL does. Create one under Account settings, Integrations, and add it to Grafana as a webhook contact point. A firing alert opens an incident on your status page, and the resolved notification closes it. Monitor's own checks page the escalation policy you attach to them. The steps are in opening incidents from alerting tools.