Coming from Opsgenie
Opsgenie shuts down on 5 April 2027, and Atlassian deletes whatever hasn't moved by then. Tissue Mast has an importer that reads your Opsgenie account and builds the same rotations, escalation policies, alert sources and vitals here, with a dry run first that changes nothing. It's in the web app under On call, as Import from Opsgenie, and it's open on every plan. Moving from Opsgenie covers the importer, the quick path for senders and the re-key checklist.
This page is the word list: what Opsgenie calls something, and what it's called here.
The words
| Opsgenie | Tissue Mast | Notes |
|---|---|---|
| Integration | Alert source | Each integration becomes one alert source with its own send URL. The API calls it a channel |
| Integration API key | Send key (mk_…) |
On the quick path it goes in the same GenieKey header |
| Alert | Incident | Opsgenie's "incident" is a heavier object on top of alerts. Here one thing going wrong is one incident, and there's nothing above it |
| Priority P1 to P5 | Level: page, loud, normal, quiet | P1 is page, P2 loud, P3 normal, P4 and P5 quiet. Sends that say P1 keep working. Priority names from other tools |
| (none) | Highest level | Opsgenie has nothing like it. Each alert source has a loudest level it can deliver at, and only a phone can raise that to page |
| Dedup by alias | Dedupe by key |
Send the alias as key. On the quick path Mast reads alias for you |
| Alert log | Timeline | On an incident, who was notified, on which device, and who acknowledged |
| Schedule, rotation | Rotation | A schedule with two layers becomes two rotations |
| Override | Override | Whole days, or a start and end time |
| Escalation | Escalation policy | Steps page a rotation, the next person on it, one person, everyone or another alert source |
| Heartbeat | Vital (heartbeat) | Same interval. An expired heartbeat is a vital that's Down |
| Maintenance policy | Maintenance window | |
| Notification rules, contact methods | Devices | Mast pages a linked phone or watch through push, and calls from a step with Call ticked. There are no per-person rules and no SMS |
| Acknowledge, close | Acknowledge, resolve |
Where it isn't a match
Routing rules. Mast has no rules inside an alert source that send P1 to one policy and the rest to another. Make two alert sources, each with its own policy, and point each kind of alert at its own send URL.
Imported alert sources top out at loud. The importer makes alert sources the way the web app does, so none of them can page until someone raises its highest level from a phone. Do that for the ones your P1 alerts arrive on before the day you switch, then send a test page to check.
Teams. There's no team object. The importer puts the team's name in front of each schedule, escalation and integration it owned, so Platform / Primary is the Platform team's Primary rotation.
Time-restricted rotations. A rotation that's on only during working hours has no equivalent and is kept on around the clock. The dry run flags every one.
Moving from Opsgenie has the full list of what doesn't carry over.