EBS: Backing up Notification History Data in Everbridge Suite

2026-04-28 13:30:08 UTC

Topic

How to back up Notification History data in Everbridge Suite.

Description

In the event the details of a notification need to be reviewed, the information will be readily available. Everbridge recommends generating a Notification History report monthly as part of a backup routine.

Follow the steps below to generate a Notification History report as a backup:

NOTE: Everbridge stores Notifications for 18 months. Notifications and associated incident communications older than 18 months are purged in accordance with Everbridge’s data retention policy and are no longer available in the system, so they cannot be retrieved by users or Everbridge Technical Support.

  1. Log in to the Manager Portal and select the appropriate Organization from the upper right-hand corner.
  2. Click on the Reports tab from the top of the page.
  3. Click on the Create Report button.
  4. Select the "Notifications" report type from the Report type dropdown menu.
  5. Drag and drop the desired data to retrieve into the DATA pane.
  6. Drag and drop any filters (if necessary) into the FILTERS pane.
  7. In the Search In pane, select the radio button for From and enter the appropriate start and end dates. Because report queries use your local time window (for example, 12:00 AM on the start date to 12:00 AM on the next date), you may want to slightly expand the time range before and after your target date to ensure all notifications sent on that date are included.
  8. Choose Preview Report to preview the results of the report.
  9. Choose PDF or CSV to export the report in the desired format.

To further streamline the backup routine, name and Save this report for future use.

Important: To archive a full year's worth of sent notifications and incidents, you'll need to run two separate reports. The Everbridge reporting tool only allows exporting data for a 6-month period at a time. To get a complete annual record:

  1. Run one report covering the first 6 months of the year.
  2. Run a second report covering the remaining 6 months.

This approach ensures you have a comprehensive backup of all your sent notifications and incidents for the entire year.

Long-term Data Preservation: By running these custom reports monthly and saving them in PDF or CSV format, you can maintain a record of your organization's alert history even after the standard 18-month data storage period expires. These reports can include critical information such as who was alerted and when, allowing you to preserve your notification history indefinitely. Historical notifications that have already been delivered cannot be deleted from the system during the 18‑month retention period, as they are part of the audit trail and reporting functionality.

Multi-Year Historical Data Access: For organizations needing to access and analyze multi-year historical event data, Everbridge offers Resilience Insights with advanced reporting capabilities. This feature provides access to Risk Events Analysis and Alert Analysis reports. Users can set custom date ranges under the 'Effective Date' option and export the data. With advanced reporting, users can typically access up to 3 years of historical risk event data.

Printing / Exporting Individual Incident Notifications: If you need a hard copy of a specific incident notification for your backup records, you can either print the notification page directly from your browser (for example, using Ctrl + P) or download the notification details from the notification’s details page and then open and print the downloaded file.

Full Account-Level Exports: If you require a comprehensive export of templates, variables, and notifications for one or more Everbridge accounts as part of your backup strategy, you can request that Everbridge Technical Support or Engineering run a full report/export on your behalf. In your request, specify which account(s) should be included and explicitly grant permission for engineers to access those accounts. Your Account Manager may be involved to run or approve this type of request.

Was this article helpful?
0 out of 0 found this helpful