# Salesforce Data Export Service: a weekly backup a five-person team can trust https://salesbond.app/blog/salesforce-data-export-service-weekly-backup-small-team/ Published: 2026-10-22 · Updated: 2026-10-22 Salesforce’s built-in Data Export Service saves your records and attached files as a zip of CSV files, on demand or on a schedule. The download link lasts 48 hours, and the archive holds no metadata. So the minimum backup for a five-person team with no admin is: one named owner, a scheduled export, a download inside the window, a count of opportunities against the pipeline report, and a copy stored outside Salesforce. Restoring is a separate job, and we treat it as one. (Limits per [Spin.AI](https://spin.ai/blog/salesforce-data-export-options-a-complete-guide/) and [Gearset](https://gearset.com/blog/dont-use-data-export-for-salesforce-backups-and-disaster-recovery/); both sell backup tools, so weigh their conclusions accordingly.) ## What Data Export Service gives you (and what it does not) In Setup, type Data Export in the Quick Find box. The page offers two buttons, Export Now and Schedule Export ( [Hevo: automate Salesforce data export](https://hevodata.com/learn/automate-salesforce-data-export/)). Both produce one CSV per object, plus attached files if you tick that option, packed into a zip. Salesforce emails a link when it is ready, and the file is deleted 48 hours after that email (Hevo, link above). Three limits set the rest of this article: - The Recycle Bin is not in the archive. A deal a rep deleted on Thursday is not in Saturday’s export. - Metadata is not in the archive. Custom fields on Opportunity come out as columns of data; the field definitions, page layouts and validation rules are not saved. - The person who runs or schedules the export needs the Weekly Data Export permission. The cadence depends on your edition: every 7 days on Enterprise, Performance and Unlimited, every 29 days on the others, Professional included (Spin.AI; Gearset says the same about Professional: no more than once a month). ## The 48-hour trap: schedule it, then verify the download Here is the failure we see most. Someone set Schedule Export a year ago and felt covered. Nobody downloaded a single archive, every link expired, and the team’s backup is a settings page. A scheduled export is a reminder to download. It is not a backup. So the routine has two halves, and the second one is the one that counts: 1. Schedule Export for a night when nobody works, say Saturday. Tick the files option if reps attach proposals to deals. 2. Put a recurring thirty-minute block in the owner’s calendar for Monday morning. No email yet? Look again on Tuesday: Salesforce queues exports and does not promise a completion time (Hevo). 3. Download every zip in the email. Large exports are split into several files, so one link is not always the whole archive. Rename them with the date: `sf-export-2026-10-26-1.zip`. 4. Move them off Salesforce and off the owner’s laptop, to a shared-drive folder only the owner and the business owner can write to. 5. Run the five-minute check below and write one line in a shared sheet: date, file names, opportunity count, where they live. On Professional Edition the same steps run every 29 days instead of weekly. ![Weekly routine: Saturday export, Monday download inside 48 hours, count check, storage; without the download the link expires](https://salesbond.app/wp-content/uploads/2026/10/salesforce-data-export-service-weekly-backup-small-team-2.png) Steps 3 to 5 take less time than reading this section. They get skipped because nobody owns them. ## Who owns it: one person, one calendar slot A five-person sales team usually has no Salesforce admin. It has a manager who got the System Administrator profile because somebody had to. Name that person and give them the permission and the Monday block. Not “the team”. A chore with a deadline and no name expires quietly, and here that is literal. We would make it the manager, because the manager already looks at the pipeline report on Monday and the check in the next section is a comparison against that report. The second person with the permission is the business owner, for the week the manager is on holiday. The owner’s whole output is the log line. A year of those lines also answers an auditor who asks whether the company keeps its CRM data. We wrote the Pipedrive version of this in [a monthly export routine for a small Pipedrive team](https://salesbond.app/blog/pipedrive-data-export-backup-routine/), and the owner rule is the part that carried over unchanged. ## The five-minute check: does the zip match your pipeline report? An archive nobody has opened is a guess. The check is deliberately crude. Find `Opportunity.csv` (in a split export, not necessarily in the first zip) and open it in a spreadsheet. Row count minus the header row is the number of opportunities in the export. Now run an opportunity report with no filters: all opportunities, all time, closed included ( [the three reports a sales manager needs](https://salesbond.app/blog/salesforce-reports-sales-manager-weekly/) covers building one). The two counts should match, give or take deals created or deleted since Saturday. Write both numbers in the log. Then one spot check. Find last week’s most-discussed deal by name and read across: `StageName`, `Amount`, `CloseDate`, `OwnerId`, your custom fields. If the columns are there and filled in, the export carries what you would need. Far apart? The usual cause is a report scoped to “My opportunities” or to this fiscal year. If the export is low and the report is right, remember the Recycle Bin: a rep’s cleanup on Wednesday is a gap on Monday. The check tells you the data is there, not that its right. A disclosure: we build SalesBond, a sales management layer on top of the CRM a team already uses; we started with Pipedrive, and it works with Pipedrive, HubSpot, Salesforce and Zoho CRM. It does not do backups. It reads the same opportunities daily and flags those with no next step, a past close date or no activity, so the report you compare against is one you trust. If that list is what you are missing, [check your CRM with SalesBond](https://salesbond.app/). The export routine stands on its own either way. ## Is a Salesforce data export a backup? Metadata and restore time Partly. Backup and restore are two jobs, and the export only does the first half of one. Say the bad day arrives. A bulk update overwrote the stage on three hundred opportunities, or a departing rep deleted their accounts on the way out. (For the first case, [field history tracking on Opportunity](https://salesbond.app/blog/salesforce-field-history-tracking-opportunity-audit/) tells you what the old values were and who changed them.) You have last Monday’s zip. What happens next is not a restore button, because there is none. It is a person loading `Opportunity.csv` back with Data Loader, matching on `Id`, object by object, so contacts find their accounts and deals find their contacts. That is an afternoon, provided the fields the CSV refers to still exist. That proviso is the metadata problem, and it is Gearset’s whole argument: restoring data without a metadata backup means recreating the metadata first, which delays the recovery (link above). If what you lost is a field, a layout or a flow, the CSV has the values and not the container. You rebuild the container by hand, then load the data. So we draw the line like this. For a small team, the export covers the cases that actually happen: a bad import, a rep’s deletions, a question from finance about last year’s deals. It does not cover losing the org or losing metadata. Whether that risk is worth a paid Salesforce backup tool is the business owner’s call, not the manager’s, and the question to ask any vendor is plain: does it restore metadata, and how long does one object take? Pair the export with [a monthly CRM data-cleansing routine](https://salesbond.app/blog/crm-data-cleansing-monthly-routine-small-team/), because an archive of duplicates is a backup of duplicates. ## FAQ **Export Now is greyed out. Why?** It is one of the most-asked Data Export questions on the [Trailblazer Community](https://trailhead.salesforce.com/trailblazer-community/feed/0D54V00007T4CpKSAV). Export Now only becomes available once enough time has passed since the last export (Hevo, link above), so check the date of the last run, then check that the user has the Weekly Data Export permission. If a scheduled export is set up, the grey button changes nothing: the archive still arrives, and the download is what matters. **Can we export on Professional Edition?** Yes. The service is available on Professional, and the question that has sat on the [Trailblazer Community](https://trailhead.salesforce.com/trailblazer-community/feed/0D54S00000A7SISSA3) for years is really about frequency. On Professional the shortest interval is 29 days, against 7 days on Enterprise and Unlimited (Spin.AI, link above). Editions compared: [Salesforce pricing for a five-person team](https://salesbond.app/blog/salesforce-pricing-five-person-sales-team-editions/). **Should we use Data Loader instead?** Not for the routine. Data Loader exports on demand, with no schedule, from one person’s machine, which makes it the tool for a targeted extract or for loading a CSV back in on the bad day. Spin.AI’s comparison is fair on that split. Use both: the service for the copy, Data Loader for the the restore.