Limitations of Salesforce Data restore
Following are the limitations of the Salesforce data restore for the current release:
:
Restores fail if the target schema differs from the schema at the time of the backup.
Note:
If the schema in the target organization is an extension of the schema at the time of backup and remains compatible, the restore will function.
See Guidelines for Schema changes in Salesforce organization to prevent restore failures.
:
Emails with attachments uploaded via the Salesforce Lightning portal to the Account object are restored to draft status, including their attachments.
For more information, refer to the following link:
The Public URL and password of files in Salesforce cannot be restored.
The and fields are stored in the table and are not updatable.
You must recreate the Public URL and assign a new password after restoring the document (if the document was publicly distributed).
The image in the ContentNote cannot be backed up.
ContentNote is a non-restorable object. To restore it, you must restore it via ContentDocument.
The restore from the End-User portal is not supported.
The restore can fail if the target schema is incompatible with the schema captured at the time of the backup. You must update the target schema before initiating a data restore.
If the Record type functionality is enabled for any object, older records with a Record type equal to Null cannot be restored.
If the Export location is configured by the , the Private Library Documents of the non- are not restored to their own library. Instead, these documents are restored in the Private Library.
Some Salesforce fields, such as , are internally stored as Double data types. As a result, these values are rounded off when backed up.
A few objects are not supported for the backup and restore. Refer to the following topics to know to get the list: