Skip to content

Convert from PagerDuty

You do not have to rebuild your setup by hand. Noci AI reads PagerDuty, plans your setup in Noci, and shows you the plan as one change. You confirm it, and you can undo it.

Noci only reads from PagerDuty. It never changes anything there. Your PagerDuty setup stays as it is until you switch your alerts over.

  1. Make a read-only key in PagerDuty. An admin or the account owner makes a general access REST API key, and sets it to read-only.
  2. Connect PagerDuty in Noci. Tell your assistant you want to convert from PagerDuty. It gives you a link with setup_handoff. Paste the key into that page, not into the chat.
  3. Ask for the conversion. Your assistant starts the import with import_start. Noci reads PagerDuty. It takes a minute or two.
  4. Check on it. Your assistant asks with import_status until the plan is ready.
  5. Review and confirm. Your assistant gives you a link. The plan waits there with what could not be brought over listed beside it. Confirm it in Noci.

You can ask for only some parts, such as teams and schedules first.

  • People, matched to the people already in your workspace by email address, with the phone numbers the old tool shares
  • Teams and who is on them
  • On-call schedules and their layers
  • Overrides in the next 30 days, as covers
  • Escalation policies
  • Services, each with its team

People are matched to the people already in Noci by email address, case ignored. Two people with the same address are never matched to anyone.

Overrides become covers. Noci brings the ones in the next 30 days.

Noci lists everything it could not bring over, with the reason, before you confirm. These are the reasons that can come up from PagerDuty:

Not in Noci yet
Someone the old tool lists is not a person in your Noci workspace. Invite them, then ask for the import again.
More than one match
Two people share this address. Fix one of them and ask again.
Team name already in Noci
A team with that name already exists. Rename one of the two teams, then ask for the import again.
Paged a person directly
An escalation step paged one person instead of a schedule. Add a step for the role you want.
Extra schedules
A team has more schedules than Noci uses for it. Add the other schedules by hand.
Hours Noci cannot copy
A layer is limited to certain hours in a way Noci does not copy. Add this layer by hand.
Rules Noci cannot copy
A rule from the old tool has no match in Noci. Add it by hand.
Phone number not shared
The old tool did not share this person's number. The person adds it in Noci.
No phone number
The old tool has no number for this person. The person adds a number in Noci.
On-call hours differ
For the next two weeks, the hours somebody is on call differ between the old tool and what Noci will set up. Check them before you confirm.
Not allowed to read
The key you gave Noci cannot read this part. Give Noci read access to it and ask again.
Only part was read
Noci read only part of this list. Add the rest by hand.

Your assistant tells you how many of each there are. The names and addresses behind them you see in Noci, never in the chat.

Noci does not create people. Anyone in PagerDuty who is not in your Noci workspace is listed as “Not in Noci yet”. Your assistant gives you a link to invite them in one click. See People and invitations. When they have joined, the waiting change does not include them. Withdraw the waiting change, then ask for the import again. Asking again while the first change still waits is refused.

When Noci can see who PagerDuty has on call, it compares the next two weeks with what Noci would have on call once you confirm. If the hours differ for a schedule, it says how many hours are on call before and after, and how many are held by a different person. Check these before you confirm.

Phone numbers PagerDuty shares come over when you confirm. They page from day one, and nobody has to confirm them. A person’s own number, or one from your identity provider, wins over an imported one. See People and invitations.

  • Undo. The conversion is one change. Undo it from the Changes page and Noci is back as it was, including the numbers it brought over.
  • Test it. Send a test alert and a test page. See Go live.
  • Switch your alerts over when you are ready. Point your monitoring tools at Noci, then choose which teams go live.