Export Single Record

Target one specific Salesforce record and download every attached file, including child record files.

Export Files from a Single Salesforce Record

The Export Single Record mode lets you pinpoint one specific Salesforce record by name and download every file attached to it in a single operation. Instead of scoping an entire object or list view, you search for the exact record you need and export only its files — making this ideal for targeted extracts, support escalations, or one-off data requests.

You can optionally extend the export to include files from all related child records, traversing the standard Salesforce relationship graph to pull the full file hierarchy in a single run. For example, exporting an Account record can also capture files attached to every Contact, Case, and Opportunity linked to that Account.

Export from a single Salesforce record and its child records — SFDC File Exporter
Single Record export — search by record name, optionally include child record files organised into sub-folders.

How to Use

Follow these six steps to export files from a specific Salesforce record.

1
Select Export Type

Open SFDC File Exporter and navigate to the Export Single Record tab from the main navigation panel. This mode is listed under the Export Methods group.

2
Select the Salesforce Object

Choose the object type that the target record belongs to — for example, Account, Contact, Opportunity, Case, or any custom object available in your org. The app populates the dropdown from your connected Salesforce org automatically.

3
Search for the Record

Type the record name (or part of it) into the search field. Matching records from the selected object appear in the results list as you type. Click the record you want to select it. The record's name and ID are shown as confirmation before you proceed.

4
Include Child Records (Optional)

Toggle Include Child Records to extend the export beyond the selected record itself. When enabled, the app traverses all standard master-detail and lookup relationships defined on the object and pulls files from every related child record — for example, all Contacts, Cases, and Opportunities linked to the selected Account. See the Child Records section below for full details.

5
Choose Folder Grouping

Select how exported files are organised on disk. Choose By Record Name to create sub-folders using the record's display name (e.g., Acme Corp/), or choose By Record ID to use the 18-character Salesforce ID as the folder name (e.g., 001XXXXXXXXXXXXXXX/). When child records are included, each child's files are placed in their own named sub-folder within the export directory.

6
Set Output Folder and Export

Click Browse to choose the destination folder on your machine where the files will be saved. Then click Export. A real-time progress bar tracks the download. When complete, a summary shows the total number of files downloaded and any records skipped (e.g., records with no attached files).

No record ID needed. You search by the record's Name field — the app resolves the Record ID automatically. If multiple records share the same name, all matches are listed so you can pick the correct one.

Child Records

Enabling Include Child Records instructs SFDC File Exporter to traverse the standard Salesforce master-detail and lookup relationships defined on the selected object, and to pull files from every related object that is a child of the selected record.

For example, when you export an Account record with child records enabled, the app automatically queries and downloads files attached to:

Master-Detail Contacts All Contact records whose AccountId field points to the selected Account.
Lookup Cases All Case records associated with the Account via the AccountId lookup field.
Lookup Opportunities All Opportunity records linked to the Account through the AccountId field.
Lookup Custom Objects Any custom object in your org that has a lookup or master-detail relationship back to the selected object.
How Relationship Traversal Works

SFDC File Exporter uses the Salesforce Metadata API to discover the complete set of child relationships for the selected object at runtime — it does not rely on a static, hardcoded list. This means the feature works correctly with custom objects and custom relationships specific to your org.

For each child relationship discovered, the app issues a SOQL query to find all related records, then downloads every ContentDocument (Files) and Attachment associated with those records. Files are saved into sub-folders named after each child record, nested inside the parent export folder.

Example Folder Structure

With Group by Record Name and child records enabled, the exported folder structure for an Account named Acme Corp would look like this:

Acme Corp/
  contract_signed.pdf
  nda_2024.docx
  Contacts/
    John Smith/
      headshot.png
    Jane Doe/
      resume.pdf
  Cases/
    Case-00123/
      screenshot_bug.png
      error_log.txt
  Opportunities/
    Q2 Renewal/
      proposal_final.pptx
Only relationships with files are included. Child records that have no attached files do not create empty folders in the export output — the app skips them automatically to keep the folder structure clean.
Relationship depth. Child record traversal goes one level deep from the selected parent record. For example, files on Contacts of an Account are included, but files on Cases linked to those Contacts are not. For multi-level hierarchies, consider using the Export from CSV mode with a pre-built list of Record IDs.
Relationship Types Supported
Relationship Type Description Included?
Master-Detail Child records whose lifecycle is tied to the parent (e.g., Order Line Items on an Order). Yes
Lookup Child records linked to the parent via a lookup field (e.g., Contacts, Opportunities on an Account). Yes
External Lookup Relationships to external objects via Salesforce Connect. No
Custom relationships are supported. If your org has custom objects with lookup or master-detail relationships back to standard objects (such as Account or Contact), those child records are discovered and included automatically — no configuration required.