Incident handover records
Move incident records without losing the live incident's owner
Tool changes need a clear authoritative record and working links. Preserve ongoing response state before migrating historical documents.
In this article
Inventory active and historical records separately
Identify live incidents, unresolved follow-up tasks and archived reviews. A historical document can tolerate a scheduled migration window that an active response cannot.
Map identifiers, links, attachments, permissions and timestamps into the new system. Preserve the distinction between original event time and migration time.
Decide which system is authoritative during the transition. Two editable current summaries can diverge quickly when responders use different bookmarks.
Rehearse with a realistic record
Use a synthetic incident containing active mitigations, uncertain business outcomes, timeline entries and a pending handover. Migrate it and ask another responder to continue from the new record.
Verify links to dashboards and restricted evidence under the recipient's actual access. A link that works for the migration administrator may fail for the on-call team.
Check that comments or attachments containing decisions are not dropped. Some tools store important history outside the main document body.
Transition active work deliberately
Choose a controlled point to move each live incident, update its working channel and record the new authoritative location. Have the incident owner acknowledge the transfer.
Keep the old record readable or redirected according to policy, with a clear notice that updates belong in the new location. Avoid silent duplication.
Preserve external stakeholder references where they exist. A status update linking to a vanished record can create confusion even if internal responders have the new URL.
Verify retention and rollback
Check the new system's access, export and retention settings with the responsible owners. Incident records may contain sensitive operational or customer information.
Define rollback for edits made after migration. Returning to an old snapshot can discard current decisions and ownership, so reconcile new entries before any reversal.
After the move, sample historical records and test active handover again. The migration is successful when the next responder can find current state and evidence, not merely when a document count matches.
Primary sources
Google SRE: managing incidentsReferences checked 11 September 2026.