A Salesforce collection is easier to understand when you separate current object records from activities, changes and related files. Start with the work you want to describe and preserve the original record IDs. A CSV backup can contain many objects without automatically giving you a complete, connected account of every deal or support process.
The documented backup route
Salesforce’s Data Export service produces CSV backup files, with weekly or monthly availability depending on edition. Images, attachments and Salesforce Files have separate inclusion selections. Record the selected scope instead of assuming files accompany every object export.
Sources: Salesforce
Draw the object relationship before joining rows
For a fictional sales collection, opportunity D-41 belongs to account AC-8. Activity A-14 refers to D-41, and quote Q-44 refers to the same opportunity. Keep each object’s own ID and the field establishing the association.
Account name is not a safe replacement for account ID: names can change or be reused. An account-level activity may not concern every deal at that account. The inventory should preserve the association level rather than copying the activity onto all opportunities.
| Group | Identity to preserve | Relationship to inspect |
|---|---|---|
| Account | Account ID | Organization context |
| Opportunity | Opportunity ID | Account and quote relationship |
| Activity | Activity ID | Which record it concerns |
| History | Event and record reference | Property or stage changed |
| Files | File/content identity | Record association and version |
Separate current properties from changes
The current stage and amount describe the snapshot. A history record describes a saved change. A task or email describes an interaction. Inventory these separately and state which are actually present in the selected output. Do not infer the earlier state of a field from the current value.
Test a multi-deal account
Choose an account with two deals and inspect one activity associated with only one of them. Then inspect a deal that moved backward or changed amount. Those examples can reveal false joins and missing history faster than inspecting a large random spreadsheet.
For files, check whether the content and relevant version are included. A record-to-file association can survive while the actual file content is absent. Preserve that distinction and keep any local sample inspection tied to the export settings used.
Keep custom relationships explicit
A business may store a project or order reference in a custom field. Record the actual field and its observed meaning rather than assuming a standard relationship from its display label.
Describe the scope in object terms
Use a collection name such as selected opportunities with linked activities and checked file associations. Add the observed dates and fields you inspected. Use the provider matrix to find relevant CRM interests, then name the objects in your proposed collection.
- Object names and original IDs
- Explicit association fields
- Current values versus saved changes
- Activity-to-record relationship level
- File selections and content availability
- Observed period and migration references
Questions about this comparison
Can account name replace the original account ID?
Avoid that assumption. Names can change or identify more than one record. Preserve original IDs and relationships.
Does every account activity belong to every deal?
No. Inspect the actual association level.
Are attachments automatically part of every Data Export?
The official guidance describes separate inclusion selections. Record what was selected and inspect the output.
Sources
- Export Backup Data from SalesforceSalesforce · Checked 2026-10-06