What kind of Salesforce data do we capture?
There are three main categories of Salesforce data that we capture when archiving your data.
Standard Objects: eg Accounts, Contacts, Leads, Opportunities, and Cases.
Custom Objects: Any custom objects you have created in Salesforce.
Attachments and Files: Any documents or files associated with records, this includes ContentDocument, and ContentVersion.
Master-detail relationships
We also ensure that the data from any child object in a master-detail relationship is backed up. This preserves related data across your Salesforce environment, and makes sure that no child record is deleted without first being backed up.
Consider the diagram above showing an Account object and its child objects. Gearset would make sure to capture all associated records from the Account, Contact, Case, and EmailMessage objects when archiving an Account.
Attached files (ContentDocumentLink)
The ContentDocumentLink object is a junction object used to attach ContentDocuments to other records. Since a ContentDocument is not directly a child of the record it is attached to, Gearset follows a specific logic to determine if an attached ContentDocument should be archived. This behaviour is further detailed in this document.
Fields we do not save
Although Archiving covers most data, there are specific fields we do not capture directly or whose data we do not save at all.
Compound fields:
What is a compound field?
A compound field is a field that is comprised of other fields. For example the Address field is a combination of the street, city, state, and postal code fields.
How do we handle them?
Instead of backing up the compound field as a whole, we backup the underlying individual field values that constitute the compound field. Compound fields will be reconstructed in any restore process.
CVV (Card Verfication Value) field:
What is a CVV field? The Card Verfication Value (CVV) also known as the Card Sercurity Code (CVC) is a 3 or 4 digit number on a credit or debit card that adds an extra layer of security to purchases made online or over the phone. The CVV field is simply a Salesforce field that stores this number.
Why don't we save this field?
To maintain compliance with security standards and reduce the risk of sensitive data exposure, we don't save any CVV fields.