How to recover deleted data from ServiceNow instanceInstructions If the data is deleted or missing from ServiceNow; there are lots of if and buts in recovering the data. This depends on How/When it was deleted to determine HOW/IF the data can be retrieved. Instance backup and recovery More information on Backups and Retention is covered in this white paper: Delivering Performance, Scalability, and Availability on The Servicenow Cloud Deleted records module This module has some limitations. Only tables that are audited will be tracked in deleted records module.So if there are reference fields on table A from table B/table C and table A is configured for Audit and table B/C is not configured, then table B/C data can never be retrieved from the deleted records module. References will be gone.More details on Use the Deleted Records module to restore a deleted record If the data is removed from Deleted records table(sys_audit_delete); the data can never be retrieved. Record Deletes/Updates, how to track, find and troubleshoot these issues. Rollback context We also have rollback contexts which are enabled by default when we delete the data using a script from Background Scripts. This context is kept only for 10 days and then it is purged. Rollback context keeps track of all INSERT DELETE and UPDATE statements with that script and will recover the entire data by undoing the SQL statements. But this can be done only for 10 days from the deletion and if configured for Rollback—more details on this doco. There are rollback context expiration properties that will cleanse the table by creating a scheduled job "Clean Expired Rollback Contexts" Rollback context properties Roll back and delete recoveryUse the Delete Recovery module to restore a deleted recordUse the Script Execution History module to roll back a Scripts-Background execution How to Enable Rollback context for Fix Script Execution Mass-Deletion and Excess Data Management Recommendations Manual Data recovery by ServiceNow Support If there is an unforeseen event of data deletion on a PROD; ServiceNow can recover most of the data if this is reported within 4 days(as of this writing) from the actual event as the DB Transaction/BIN logs are kept for 4 days and the data can be recovered. We have standard operating procedures to recover the data by analysing individual cases. We have daily backups and if the data deletion happens at 10 AM and the daily backup is dated 6 AM; data logged between 10 AM and 6 AM is lost. But if we have the BINLOGS ( which is kept for 4 days as of this writing); we can spin up a temp instance by playing the binlogs till 10 AM after restoring the 6 AM backup and we can recover most of the data. More details of this process are covered in the below KB Restoring a Production Instance from Backup Backup Request for a Production instance Data recovery from an upgrade perspective If in case, the dataloss is observed after 4 days; we should still be able to recover some data using the 14-28 day( retention period opted for your organization) backups. In case of any data deletion/data corruption on the PROD instance; it is very important to create a case to ServiceNow Support as early as possible to utilise the BINLOGS for data retrieval. Manual Data recovery is not an option for any SUB PROD environment and the options for recovery are on this KB Dataloss on sub production or non production instances