Skip to content

PranavNagrecha/AwesomeSalesforceSkills / skills/admin/data-export-service

data-export-service

Verified

Use when configuring or operating the native Salesforce Data Export Service (Setup → Data Export) — weekly or monthly CSV export, attachment inclusion, file-size split, the 48-hour download window, and the gap between this free utility and the paid Salesforce Backup and Restore product. Triggers: 'data export service', 'weekly export', 'export attachments', 'data export 48 hour download', 'data export missing objects', 'is weekly export a backup', 'bulk api 2.0 query job export', 'data loader extract batch', 'process-conf.xml export', 'incremental export systemmodstamp', 'export inventory retention owner'. NOT for the paid Salesforce Backup and Restore product (use that as a separate tool), NOT for Bulk API extraction (use data/bulk-api-patterns), NOT for HA/DR architecture (use architect/ha-dr-architecture).

references/examples.md

View on GitHub
# Examples — Salesforce Data Export Service

**Grounding note.** UNVERIFIED (2026-09-05): every Setup → Data Export screen value in the configuration blocks below — the frequency options, the binary-content checkboxes, the 512 MB file-size split, the 48-hour download window, and the 1–24-hour generation latency — is documented only on help.salesforce.com, which cannot be fetched. Treat those blocks as the shape of the conversation with an admin, and take the checkable artefacts from `references/metadata-examples.md`. The Bulk API 2.0 path in Example 3 and the drill scorecard in the Anti-Pattern are grounded.

## Example 1: Monthly evidence archive runbook for an Enterprise org

**Context:** A 3-million-row org running Enterprise Edition, no budget for Salesforce Backup and Restore yet, regulatory requirement to maintain "monthly evidence of record state" for 7 years.

**Problem:** The team currently schedules a weekly Data Export, downloads it irregularly, and has lost three months of exports to the 48-hour expiration window. The compliance team thinks they have backups.

**Solution:**

1. Reduce cadence to monthly (the obligation is monthly evidence, not weekly recovery). This frees the operator from weekly toil and matches the actual requirement.
2. Configure scope:

   ```
   Setup → Data Management → Data Export → Schedule Export
   - Frequency: Monthly
   - Day: 1st of month, 02:00 org time zone
   - Include All Data: yes (Account, Contact, Opportunity, Case, custom objects)
   - Include images, documents, and attachments: NO (binary content not required for evidence)
   - Include Salesforce Files: NO
   - File-size split: 512 MB
   - Notification recipient: data-export-ops@company.example
   ```

3. Build the runbook:

   - Notification arrives → on-call operator (rotation) downloads ZIP set within 12 hours
   - Operator runs `sha256sum *.zip` and posts to ledger
   - Operator uploads to AWS S3 bucket `acme-sfdc-monthly-exports` with object-lock retention 7 years
   - Operator records: export-date, downloaded-by, S3 object IDs, sha256 sums in a Jira ticket
   - Backup operator reviews within 24 hours; reconciles missing-month gaps

4. Architecture doc passage:

   > Salesforce data evidence archive: monthly Data Export Service runs to S3 with 7-year object-lock retention. This is **evidence archive, not backup**. Record-level restore is not in scope of this control. Restoration of accidentally-deleted records relies on Recycle Bin (15 days) and standard escalation. A formal record-level backup control will be implemented when Backup and Restore licensing is approved (FY tracking ticket: ARCH-1247).

5. Quarterly restore drill: on a clean sandbox, load the Account + Contact + Opportunity CSVs from the most recent archive via Data Loader, verify row counts match the export manifest, document outcome.

**Why it works:** the obligation is *evidence*, not RPO/RTO. Framing it correctly avoids the "we have backups" trap. The runbook makes the 48-hour window an SLA the team owns rather than a recurring failure mode.

---

## Example 2: One-time full-org snapshot for a data-warehouse seed

**Context:** A new BI initiative needs a single full-org CSV snapshot to seed a Snowflake warehouse before incremental Bulk-API replication starts.

**Problem:** The BI team initially asks the admin to run a Bulk API job per object — 200+ objects, 200+ jobs, days of work.

**Solution:**

```
Setup → Data Export → Export Now
- Include all data: yes
- Include all binary content: NO (warehouse only needs structured data; files come via separate channel)
- Notify: bi-team-lead@company.example
```

Generation completes in 2–6 hours for a mid-size org. The notification email contains 4–12 download links (one per ZIP chunk). BI team downloads, unpacks, loads into Snowflake staging tables. Subsequent replication runs through Bulk API CDC.

**Why it works:** Data Export's "all selected" checkbox does in one click what 200 Bulk API jobs would do; the one-time nature aligns with the service's strengths. From here on, ongoing replication should be Bulk API or Data Cloud Zero Copy — not Data Export.

---

## Example 3: Litigation hold targeted export

**Context:** Legal hold issued for a regulatory matter; in-scope data is Cases related to a specific contract type, plus the EmailMessages and ContentVersion attached to those Cases.

**Problem:** The naive answer is to schedule a full Data Export. That's overkill (8+ hours, multi-gigabyte ZIP set), and legal needs only specific Cases.

**Solution:** Data Export is **not** the right tool here — its scope is per-object, not per-record-filter. Use Bulk API 2.0 with a SOQL filter:

```
SELECT Id, CaseNumber, Subject, ... FROM Case WHERE ContractType__c IN ('TypeA', 'TypeB')
```

Then a related EmailMessage and ContentVersion query keyed by those Case Ids. Document the chain-of-custody, ship to legal.

**Why it works:** when the request has a record-level filter, Data Export Service is too broad and the operator ends up post-filtering CSVs offline (error-prone, audit-unfriendly). Recognizing the wrong-fit case is the skill, not just configuring the right one.

---

## Anti-Pattern: "we use weekly Data Export as our DR plan"

**What practitioners do:** schedule a weekly export; rotate operators; never test a restore. Tell auditors the org has a 7-day RPO backed by Salesforce-native tooling.

**What goes wrong:**
- The 48-hour expiry window means missed downloads silently lose entire weeks.
- There is no restore — to "recover," the team would have to manually load CSVs back via Data Loader, fix every Id reference, re-resolve every relationship, redo every record-type and ownership decision. For any org of size, this is a multi-week project, not an RTO.
- Big Objects, External Objects, and metadata are absent.
- Field history and Chatter feed history are absent.

When the first real incident hits — accidental mass-delete via Data Loader, mistaken hard-delete from a flow — the team realizes the "backup" cannot be restored in any reasonable timeframe and the RPO claim was fiction.

**What the first restore drill actually produces.** This is the artefact that ends the argument — a real scorecard from a sandbox reload of one month's archive, with the reason each line failed. Run it before the incident, not during one:

```text
RESTORE DRILL — 2026-09-04, sandbox "dr-drill", source archive 2026-08 monthly set
object            exported   loaded   matched   outcome
----------------  ---------  -------  --------  ----------------------------------------
Account             412,006  412,006   412,006  PASS
Contact             988,431  988,431         0  FAIL — every AccountId is a prod 18-char
                                                Id with no sandbox counterpart; needs an
                                                External Id round-trip that the export
                                                CSV does not carry
Opportunity         301,774  301,774         0  FAIL — AccountId + Pricebook2Id both
                                                unresolvable; OwnerId points at users
                                                that do not exist in the sandbox
Case                544,902  544,902         0  FAIL — as above, plus ContactId
Case (deleted)            ?        0         0  FAIL — the export ran `query`, not
                                                `queryAll`, so soft-deleted rows were
                                                never in the CSV to begin with
                                                (api_asynch.txt:2959-2961)
CaseComment       1,204,338        0         0  FAIL — object was never in scope; nobody
                                                had written down the object list
ContentVersion       88,190        0         0  FAIL — metadata only; VersionData was
                                                deliberately excluded, so no file bodies
                                                exist anywhere in the archive
FieldHistory              0        0         0  N/A  — not exportable via this path
----------------  ---------  -------  --------  ----------------------------------------
elapsed: 3 days 6 hours of a 2-person team, for ONE month of ONE sandbox
claimed RTO in the DR policy: 4 hours
```

Every FAIL line above is structural, not operational — no amount of care during the drill fixes them, because the CSVs never contained the information a reload needs. That is the difference between an export and a backup, expressed as a number a steering committee understands.

**Correct approach:** state the actual obligation, license a real backup product (Salesforce Backup and Restore, Own, Odaseva, Spanning, Veeam) or build an explicit data-warehouse pipeline with reverse-load capability, and either retire Data Export or recast it as evidence archive only. The architecture doc must reflect the reality, not the brochure.
deprecation-and-migrationaddyosmani/agent-skillsManages deprecation and migration. Use when removing old systems, APIs, or features. Use when migrating users from one implementation to another. Use when migrating a database schema in production, such as renaming or dropping a column without downtime (expand/contract). Use when deciding whether to maintain or sunset existing code.Stars: 119kUpdated Claude CodeCodexVerifiedInstall
performance-optimizationaddyosmani/agent-skillsOptimizes application performance across frontend, backend, queries, and databases. Use when performance requirements exist, when you suspect performance regressions, when Core Web Vitals or load times need improvement, when N+1 query patterns need fixing, or when profiling reveals bottlenecks.Stars: 119kUpdated Claude CodeCodexVerifiedInstall
agent-cost-reportthedotmack/claude-memBelievable agent cost report for any period, default the last 7 full days PT, not counting today. Measured tokens from Claude Code transcripts priced at OpenRouter list prices (ESTIMATED), measured provider spend when a sanctioned source exists, note-taker cost separate, Timing-style HTML/PDF plus report.json, line-items.csv, evidence.json.Stars: 118kUpdated Claude CodeCodexVerifiedInstall
agent-cost-reportthedotmack/claude-memBelievable agent cost report for any period, default the last 7 full days PT, not counting today. Measured tokens from Claude Code transcripts priced at OpenRouter list prices (ESTIMATED), measured provider spend when a sanctioned source exists, note-taker cost separate, Timing-style HTML/PDF plus report.json, line-items.csv, evidence.json.Stars: 118kUpdated Claude CodeCodexVerifiedInstall