Repair Data Loss to Restore Records in Salesforce

Restore deleted Salesforce records and their associated child records and attachments to maintain accurate and reliable data. By quickly restoring normal operations, you minimize downtime, support business continuity, and meet compliance requirements.

Important When data loss occurs in a production service/instance, Own recommends the following best practice: First perform a repair data loss to a sandbox/sub-prod instance, verify that the restored data is complete and correct, and only then perform a repair data loss to the affected production service/instance.

1. You can restore the selected, source service’s data to:
   • The same service - meaning to itself (source service <AbC>). This is the default option. The enabled Restore to a different service link displays below the Source field.
   • A different, active service of the same provider (source service <AbC> → destination service <xYz>). The enabled Restore to the same service link displays below the Source field.
     

     Important Before restoring lost data to a different, active service of the same provider, apply the following best practices:

     • Make sure that the destination’s object/table schema matches that of the source. Doing so prevents processing errors
     • Include referenced records by selecting their associated object/table in the Objects/Tables field or, alternatively, make sure that their associated object/table exists in the destination organization

   When restore to the same (source) service is the current treatment, you can change to restore to a different service by doing the following:

   1. Click Restore to a different service. The Destination field appears, in addition to the Source field.
   2. From the Destination field drop-down menu, select the (destination) service that will receive the restored data of the source service.

   When restore to a different (destination) service is the current treatment, you can change to restore to the same (source) service by doing the following:

   1. Click Restore to the same service.
      The Destination field disappears and only the Source field remains displayed.
2. Click in the Objects/Tables field and select from the drop-down menu the specific objects/tables whose lost data you want restored.
3. In the Object/Table level depth slider, select how many levels deep of data you want restored for the objects/tables that are entered in the Objects/Tables field. By default, the data depth is 3 levels deep.
   

   Warning A depth greater than 6 may increase the processing time of the restore task.
4. In the Backups field:
   1. From the CORRECT field drop-down menu, select a backup of source service <AbC> that was produced prior to the date of the data loss and that you know to contain the correct and complete data.
   2. From the DAMAGED field drop-down menu, select the backup of source service <AbC> that was produced on or after the date of the data loss and that you know/speculate experienced data loss.
5. Click Preview Restore.
   The application launches a restore job in which it performs a comparison between the CORRECT backup of source service <AbC> and the DAMAGED backup of source service <AbC> to identify lost data. During comparison processing, the UI transfers the user to the Jobs tab > Restore Pre-Process finished page of the restore job (Job ID #<nnnnn>) and presents the job’s initial processing results.