Speedrun to Signals: automated migrations are here

We are making it easier than ever to move off PagerDuty, Opsgenie, or VictorOps and get started on Signals. And it’s open source.

Wilson Husinprofile image

By Wilson Husin on 5/6/2024

When we launched Signals to the world, we were excited to hear how our product resonated with many teams. But with that excitement came an understandable concern: how much time and effort will I have to put in to move from my existing provider to Signals?

We hear you — that’s why we built the Signals Migrator tool. And we’re open sourcing it.

Empowering you to choose

Signals Migrator asks for read-only access to your existing setup and, once run, creates a Terraform configuration with your teams, on-call schedules, and escalation policies. We built this to support any preference you may have in this migration, while providing you with defaults that we think you will appreciate.

Starting anew

Just like any new chapter is a chance to start in a clean state, this migration gives you choices throughout the import process. You are in control of which resources will be imported as new, merged with something existing, or skipped.

Flexibility for teams or services

We proudly designed Signals to be centered around teams, but we recognize that some existing schedules may be grouped by services due to limitations from existing alerting providers. As such, we built flexibility into our migrator to consider import preferences from other alerting provider models.

Infrastructure-as-code

Once the tool understands your import preferences and selections, it will generate a sensible Signals setup for you in Terraform.

We understand that building reliable infrastructure is a long path and we would like to support you wherever you are in your journey:

  • Already on Terraform? Now all you need is to copy it to your configuration repository.

  • Looking for a forcing function to get started on Infrastructure-as-Code? Let this be your sign!

  • Don’t care about it? Run terraform apply and leave them behind, or let us do it for you.

Building compatibility with everyone

Signals is already being used by various teams in production, including Greenlight, Auditboad, and Qlik.

Ultimately, we built this to meet you wherever you are. Today, the tool supports importing from PagerDuty, Opsgenie, and VictorOps / Splunk On-call. 

We know you’ll like Signals, and we want to make it as easy as possible for you to get things started. Please give it a try and let us know what you think! We look forward to making your on-call shift a more pleasant experience.

See FireHydrant in action

See how service catalog, incident management, and incident communications come together in a live demo.

Get a demo