Migration checklist
Validate an Opsgenie migration before changing the production route
This guide does not reproduce changing Opsgenie prices, features or lifecycle dates. Confirm those facts with Atlassian, then use the checklist below to test whether the documented MonoDuty Webhook and response model cover your requirements.
Content reviewed:
- Opsgenie payloads must be transformed to MonoDuty fields
- Manual mapping
- Recommended before changing the primary route
- Parallel test
- Automatic configuration or history transfer is not offered
- No importer
Side by side
A qualified comparison
Plan names do not imply identical scope. The context column calls out differences that a headline checkmark would hide.
| Criterion | MonoDuty | Opsgenie | Decision context |
|---|---|---|---|
| Current vendor status | Free signup and the Pro trial are available; paid activation is sales-assisted. | Check the current Opsgenie documentation; this guide does not reproduce a price or feature claim that may change. | Use Atlassian’s current written guidance to set any migration deadline. |
| Payload compatibility | Send the documented MonoDuty JSON fields to the service-specific mndty.com Webhook URL. | Check the current Opsgenie documentation; this guide does not reproduce a price or feature claim that may change. | MonoDuty is not a drop-in Opsgenie Alert API endpoint. Transform and test every event class. |
| Configuration transfer | Teams, schedules, overrides, escalation policies and sources are recreated explicitly; no automatic importer is offered. | Check the current Opsgenie documentation; this guide does not reproduce a price or feature claim that may change. | Treat the source configuration as an inventory, not as proof that the target behaves identically. |
| Notification channels | The release-gated channels are email, SMS and voice. Native Slack, Discord and Microsoft Teams delivery is not generally available. | Check the current Opsgenie documentation; this guide does not reproduce a price or feature claim that may change. | Identify every destination in use and test the supported replacement path. |
| Historical data | MonoDuty does not import Opsgenie incident history. | Check the current Opsgenie documentation; this guide does not reproduce a price or feature claim that may change. | Retain any source export you are entitled to keep under your own retention and legal policy. |
An endpoint change is not a migration
Inventory alert sources, routing rules, team ownership, schedules, overrides, escalation timing, destinations and deduplication keys. Assign an owner and acceptance test to every item.
MonoDuty accepts its documented native Webhook contract. Existing Opsgenie payloads require an explicit transformation, and every create, retry and recovery path must be validated.
Define a reversible cutover
Use non-production alerts first. If your source supports duplicate destinations, run both routes for a bounded validation window and compare outcomes before changing the primary destination.
- Confirm schedule time zones, rotations and overrides.
- Confirm severity, context and deduplication field mapping.
- Test email, SMS and voice destinations that your target plan includes.
- Record gaps and a rollback condition before each production batch.
Controlled migration
Five steps for a controlled migration test
- 01
Inventory the source account
List sources, teams, schedules, policies, destinations, event formats and any history you need to retain.
- 02
Recreate responsibility in MonoDuty
Build services, team ownership, schedules, overrides and escalation policies; verify each configuration with its owner.
- 03
Transform representative payloads
Map source events to the documented MonoDuty fields and test validation, idempotent retry and recovery behavior.
- 04
Run a bounded parallel test
Where the sender allows it, duplicate safe events to both routes and compare incident ownership and notifications.
- 05
Cut over in reversible batches
Move sources in small groups, observe the agreed acceptance criteria and roll back any batch that fails them.
Test the workflow with your own alerts
A comparison table cannot replace a real incident drill. Start free, route representative alerts and verify the complete acknowledgement path.