Migrate from Global notification policies to Team notification policies without big bang switch over Edited

[Jonathon Schofield]

We have ~45 Global notification policies and a similar number of teams of which ~25 are active.

We would like to migrate the Global Notification Policies to Team Notification Policies in order make them easier to manage.

However OpsGenie doesn't allow global and team notification policies to both be enabled. When team policies are enabled, the global policies are removed.

So it seems the only way to migrate from global to team notification policies is to create all the team policies and then enabled them (removing global policies). This is high risk because every alert would immediately be effected.

What I would like to do is create team policies for one team and update the global policies to exclude just that one team and then test that alerts are handled properly for that team. This limits the scope of the change and is lower risk.

Does anyone have a suggestion for how to migrate from global notification policies to team notification policies in a way that mitigates the damage caused by any misconfiguration?

[Muhammad Zeeshan · Accepted solution]

Hey @Jonathon Schofield ,

I would suggest creating a Test trial account for Opsgenie and using that to Test the Team Notification Policies flow.

You can either populate that Test account with sample configurations or copy the configurations from your main account to the Test account using our import-export tool: https://github.com/opsgenie/opsgenie-configuration-backup

You can always reach out to us by creating a Support Request here: https://support.atlassian.com/opsgenie/ to help you test the configurations and make sure everything works without any drawbacks.

BR,
Zeeshan from Opsgenie Support

[Jonathon Schofield]

Thanks Zeeshan