The New Signals Migrator Is Here: Migrate Your PagerDuty or Opsgenie Config in Minutes

Modern incident management shouldn't require a migration project. The new Signals Migrator makes moving from PagerDuty or Opsgenie faster, simpler, and entirely on your timeline.

|
Copied

On-call and incident response shouldn’t be separate platforms. If you’re responsible for keeping systems running 24/7, you should be able to schedule, page, and escalate incidents in a single browser tab.

Migrating from one tool to another is daunting. That’s why we built the new Signals Migrator — an in-app, no-code experience that allows you to bring over your PagerDuty or Opsgenie config in just minutes (literally), review in a staged migration state, and set it live on your own timeline.

Organizations like Qlik, Backblaze, and Optro have already made the move from legacy on-call tools to FireHydrant, bringing on-call, incident response, and post-incident learning together into a single platform. Now we’re making it even easier to get there.

Here's how it works#heres-how-it-works

The entire flow lives in-app — no terminal, no scripts, nothing outside of FireHydrant. You connect your PagerDuty or Opsgenie account, and FireHydrant reads your existing configuration and surfaces your teams, schedules, escalation policies, and support hours automatically. From there you choose what you want to bring over — everything at once, or just the teams you want to start with. You can always come back and import more later.

Selected teams land in a staged migration state before anything goes live. You can review everything that came over, see anything that needs attention, and take as long as you need. Your existing on-call setup keeps running the whole time.

When you're confident everything looks right, you activate the team and it's live in Signals, available for incident assignment, Runbooks, and the rest of your FireHydrant setup.

That's really it. The flow is designed to get out of your way and let you migrate at whatever pace makes sense for your team.

Read our documentation to learn more.

A note for Opsgenie customers#a-note-for-opsgenie-customers

If your team is on Opsgenie, the timeline is worth paying attention to. New purchases ended in June 2025 and data deletion is scheduled for April 2027. The new Signals Migrator is the lowest-risk path to move while you still have time to do it on your own terms, rather than under deadline pressure.

What's on the other side#whats-on-the-other-side

Once your teams are live, you've got real on-call infrastructure behind them — team-based scheduling, escalation policies built for how teams actually work, and alerting that understands service ownership instead of just working down a list. And it all lives in the same platform as incident response, automation, and retrospectives. No stitching together a paging tool, a Slack workflow, and a separate retro process.

And with FireHydrant now part of Freshworks, organizations can connect engineering response in FireHydrant with service operations in Freshservice, helping IT and engineering teams stay aligned when incidents occur.

The new Signals Migrator is available now. Start with one team. See how it feels. Go from there.

Third party logos and trademarks are the property of their respective owners. Use does not imply affiliation, endorsement, or sponsorship between respective trademark holders and Freshworks. © Freshworks Inc. All Rights Reserved

See FireHydrant in action

See how our end-to-end incident management platform can help your team respond to incidents faster and more effectively.