---
schema_version: "1"
id: d68b4a4ff2181ba9d622cf0d463862da4cff32517ae009b659dd9b4e7aa6ba30
title: Restore Environments in ServiceNow
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/platform/264-0-0/br_o_servicenow_restore_environments.md
canonical_url: https://help.salesforce.com/s/articleView?id=platform.br_o_servicenow_restore_environments.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 63470510ccc18d3ce7d7ec0c6e5ee6f1280bb4b728aa3559bd7ad0cae43821df
description: Restore environment data to the same environment for repairing data corruption or loss within an environment. You can also restore to different environments for testing or compliance purposes, such as validating production data in a sub-production instance before moving it back to production.
products:
  - Security
  - Salesforce Platform
release: "264"
---
# Restore Environments in ServiceNow

Restore environment data to the same environment for repairing data corruption or loss within an environment. You can also restore to different environments for testing or compliance purposes, such as validating production data in a sub-production instance before moving it back to production.

## Restoring to the Same Environment

Restoring to the same environment enables restoring of single or multiple tables from an instance to the same instance. This feature is designed for the following use cases:

- Repairing data corruption or loss within an environment to restore any lost records and attachments.

## Restoring Across Different Environments

Restoring to a different environment enables restoring of single or multiple tables from one source instance to a different target instance. This feature is designed for the following use cases:

- Restoring production data into a sub-production instance to thoroughly validate and test the data before restoring or moving the data into a production instance. Restoring directly to production can pose significant challenges due to disabling existing business rules, workflows, and configurations. Restoring to a different sub-prod environment is a flexible and low-risk alternative.
- Restoring historical or archived production data into a sub-production instance to meet compliance regulations or audits. Recover for ServiceNow helps save money by storing regulated data with Own instead of paying for and storing it in a ServiceNow instance. Whenever you need the data to meet legal requirements, restoring it to a sub-production instance instead of production helps you meet legal requirements and minimize disruption to your business.

Restoring to a different environment has the following limitations:

- Restoring to a different environment is only available for data loss.
- Instead of comparing two distinct backups from the source and destination, restore compares two backups from the source instance.
- The table metadata must match between the source and destination tables for a restore to be successful. If not, restore completes with errors. For this reason, it is important to routinely perform production to sub-production clones.