Systems and records
What happens to your Salesforce data when the contract ends?
By SourceX Editorial · Reviewed by Noah Loul ·
Short answer
When a Salesforce contract ends, your agreement typically allows a limited window to request your data back, after which Salesforce deletes it under its terms. The window's length, the return format, any fee and the deletion timing are set by the version you signed and your order forms. Read those terms early, and export data and metadata yourself first.
Key takeaways
- The return-of-data terms in the agreement you signed, not today's website version, govern your exit.
- Order forms and the data processing agreement can change the defaults, so read all three together.
- Vendor-returned data tends to arrive as raw files; your own export should also capture metadata, files and history.
- In a wind-down or insolvency, confirm early who has authority to request data and whether unpaid fees could trigger suspension.
- A litigation hold overrides normal deletion plans, so check with counsel before any purge.
What happens to Salesforce data when the contract ends#
When a Salesforce contract ends, users lose access to the org and the data then follows the return and deletion terms of your agreement. Enterprise SaaS agreements, Salesforce's included, commonly provide a limited period after termination during which the customer can ask for its data, followed by deletion under the vendor's processes.
The details that matter are written down, not assumed. How long the window is, how a request must be made, what format the data comes back in, whether a fee applies and when backups are purged are all set in the master agreement version you signed, your order forms and the data processing agreement. Find those clauses before giving notice or letting a renewal lapse.
A Salesforce org holds more than records. Configuration, automation, field history and files sit in different places, and a request for return of data may not cover all of them in the form your team needs. That gap is why the contract checklist and your own export both matter.
Read-your-contract checklist#
A read-your-contract checklist turns a long agreement into a handful of answers the CFO and general counsel can act on. Fill it in with clause references and quoted wording, not summaries, so the answers survive staff changes during a wind-down.
Two dates drive everything else: the notice deadline for non-renewal and the last day of any return window. Put both in the wind-down calendar, and set the date your own export must be finished well before the first of them.
| Term | Where to look | Question to answer |
|---|---|---|
| Return window | Master agreement, termination and return of data section | How long after termination can we request our data, and how? |
| Request mechanics | The same section and the notices clause | Who must make the request, in what form and to whom? |
| Format | Return of data section or documentation it references | What file format comes back, and does it include files and attachments? |
| Fees | Order form and return of data section | Is return included, or charged as a separate service? |
| Deletion timing | Termination section and data processing agreement | When is data deleted from production and from backups? |
| Deletion confirmation | Data processing agreement | Can we get written confirmation or certification of deletion? |
| Suspension for non-payment | Fees and payment terms | Can access be suspended before termination if invoices are unpaid? |
| Related services | Separate order forms and product terms | Do other clouds, add-ons or acquired products have their own exit terms? |
Which document controls: master agreement, order form, DPA or online terms?#
The document that controls is set by the order-of-precedence clause, which usually ranks the order form, the main agreement, the data processing agreement and any product-specific terms. Read that clause first, because an order form negotiated years ago may override defaults that the current online version describes differently.
Online terms incorporated by link change over time. Find the version in effect when you signed or last renewed, save a dated copy, and ask your account executive to confirm in writing which version applies. Products that Salesforce acquired, such as Slack or Tableau, may carry their own terms and their own exit processes.
Where the data processing agreement sets stricter return or deletion obligations for personal data, it often prevails for that data. Ask counsel how the documents interact in your situation before relying on any single one.
What to export yourself before the end date#
Your own export before the end date is the only copy you fully control, so treat the vendor's return process as a backstop. A raw return of records may lack the configuration, history and relationships your team needs to read them later.
Use the built-in data export, reports, API-based tools or a backup product, and check row counts against the org. Store the archive outside Salesforce with access controls and a note of what each file contains.
- Every standard and custom object, with record IDs and lookup fields intact.
- Field history and any history tracking you rely on, which may cover only part of the org's life.
- Files, attachments, content documents and email messages linked to records.
- Activities, Chatter posts and case comments.
- Metadata such as objects, fields, picklists, validation rules, flows and page layouts, so the data can be interpreted.
- Report and dashboard definitions, plus exported results for key periods.
- User and role lists, so owner and author IDs can be read.
Wind-downs, receiverships and the authority to ask#
In a wind-down, assignment for the benefit of creditors, receivership or bankruptcy, the first question is who has authority to ask Salesforce for data. The person who used to administer the org may no longer be an officer, and the vendor will want to deal with someone who can bind the customer entity.
Unpaid invoices complicate exits. Many agreements allow suspension for non-payment before termination, which can cut off exports at the worst moment. A trustee, assignee or wind-down officer should contact the vendor early, document their authority and agree on access for an orderly export.
Whether customer data can be transferred or sold as part of an estate is a separate legal question for counsel and, in some cases, the court. Privacy promises made to customers can travel with the data and limit what a buyer may do.
Illustrative: an assignee closes a freight brokerage's Salesforce org#
Illustrative: a fictional regional freight brokerage has made an assignment for the benefit of creditors. The assignee finds a Salesforce org holding years of shipper accounts, load cases and carrier notes, two unpaid invoices from the vendor, and no administrator, because the last one left weeks earlier.
The assignee's counsel pulls the original master agreement, the later order forms and the data processing agreement, and builds the checklist with clause references. The payment terms allow suspension for unpaid fees, so the assignee sends the vendor the assignment document showing its authority and agrees to pay for a short extension to finish an orderly export.
A contractor exports every object, files, field history and metadata, and the assignee requests the vendor's return of data within the contractual window as a backstop. Before any buyer is offered the customer records, counsel reviews the brokerage's shipper contracts and privacy notice. Once both copies are checked, counsel requests written confirmation of deletion and files it with the estate records.
How SourceX looks at a Salesforce archive#
SourceX assesses a Salesforce archive on what it records about real work: cases with resolutions, opportunity histories with stage changes and reasons, and activity tied to outcomes. Contact lists alone are mostly personal data and rarely a licensing fit.
SourceX runs any licensing through the SourceX five-step transaction, Supply, Rights, Preparation, Approval and Delivery, beginning with a metadata-only fit check. Customer contracts, vendor terms and privacy obligations are reviewed in the Rights step, and the SourceX Evidence Packet records the result, including the company's release authorization.
Frequently asked questions
Can we extend access past the contract end date?
Often, by negotiation. A short renewal, a reduced edition or a limited extension can keep the org readable while exports finish. Ask before the notice deadline, while you still have leverage as a renewing customer, and get the extension in a signed order form rather than an email.
Does Salesforce delete backups at the same time as production data?
Backups are often purged on a separate schedule from production data. The agreement or data processing agreement usually describes when backup copies are overwritten or removed. Ask for the timeline in writing if your privacy commitments or a client contract require you to confirm complete deletion.
What about data held in AppExchange apps and integrations?
Data held by third-party apps and integrations may sit outside Salesforce's infrastructure and under that vendor's own terms. List every connected app, check where it stores data, and export or delete with each vendor separately. Ending the Salesforce contract does not end those agreements.
How does a litigation hold affect the exit?
A litigation hold or regulatory preservation duty overrides normal deletion. If any matter is pending or reasonably expected, counsel should define what must be preserved before data is returned, exported or deleted. Keep a defensible copy and document each step taken.
Should the CFO or the general counsel own the exit?
Both have a part. The general counsel owns the contract reading, notices and preservation questions; the CFO owns renewal timing, payment status and any extension cost. Name one of them as the accountable lead and give IT a written scope, so exports, requests and deletion happen in the right order.
Related resources
See if your company qualifies
A short company assessment. No data uploads are needed.