Skip to content

Wind-downs and transitions

Before you sign a shutdown service agreement: questions about data rights

By SourceX Editorial · Updated

Short answer

Before you sign a shutdown service agreement, ask who controls company records during the wind-down, which systems the provider will close and when, whether the agreement gives the provider any rights in your data, and how a separate data license would fit. The rule: no system is cancelled and no record deleted until it has been exported and assessed.

Key takeaways

  • A shutdown service agreement should name who holds admin access to every system that contains company records.
  • Deletion should be a decision the company approves system by system, not a default step in the provider's checklist.
  • Look for any clause that gives the provider a license, an aggregation right or a fee on company data, and decide whether you accept it.
  • If the provider also runs asset sales, ask how it handles operational records that need rights review and privacy preparation.

Why data rights belong in a shutdown service agreement#

Data rights belong in a shutdown service agreement because the provider will touch every system that holds company records. Shutdown services typically coordinate state filings, tax returns, employee matters, vendor terminations and asset sales, and many of those tasks end with an account being closed.

Most agreements describe the work as tasks rather than records. That leaves open who decides when a help desk is cancelled, whether a departing employee's Google Workspace account is deleted or transferred, and whether anyone looked at the records first. A few specific questions before signing turn those gaps into written commitments.

Questions about control and access#

Control questions establish that the company, not the provider, decides what happens to its records. Ask them first, because the answers shape every later clause.

  • Which of our systems will you need admin access to, and will you add your own accounts or use ours?
  • Who keeps at least one company-controlled admin account on each system until the wind-down ends?
  • Will you copy any records to your own storage, and if so, where, under what security and for how long?
  • Who approves cancelling each subscription, and how is that approval recorded?
  • How will you handle multi-factor devices and recovery codes held by departing employees?
  1. 01Your work records
  2. 02Personal details removed
  3. 03You approve the release
  4. 04Licensed to AI developers
How it works with SourceX: Your work records → Personal details removed → You approve the release → Licensed to AI developers.Illustrative

Questions about deletion and retention#

Deletion and retention questions decide whether records survive long enough to be assessed. A provider that deletes on a fixed schedule may be efficient, but the company still has to keep what the law requires and may want to assess other records before they go.

Questions about deletion and retention
QuestionAnswer you wantRed flag
Do you follow our retention schedule or your own?Ours, approved by our counsel and accountantOne standard schedule applied to every client
Do you delete user accounts or transfer their data first?Transfer or export before any deletionAccounts deleted as part of offboarding
Who holds required records after dissolution?A named custodian with written access termsNo answer, or the provider by default with no terms
Can deletion be paused for a records assessment?Yes, by written instructionDeletion bundled into a fixed-fee step
Do you confirm deletion in writing?Yes, listing each system and dateVerbal confirmation only

Questions about asset sales and data licensing#

Asset sale questions matter most when the provider also runs a marketplace or buyer network. The goal is to learn which assets the provider will market, on what terms, and how operational records are treated differently from domains or equipment. This is a live question: Forbes reported in April 2026 on a closed company whose remaining internal chat, project-tracking tickets and emails became items for sale to AI developers after a wind-down firm handled its closure.

Exclusivity is the clause to read twice. An agreement that gives the provider exclusive rights to sell all company assets can block a separate data license, even one the board would otherwise approve.

  • Do you market company data or workspace records, and as a sale or a license?
  • Who performs a rights review on records before a buyer sees them?
  • Who removes personal and confidential information, and who checks the result?
  • Do you take a fee or share of proceeds on data transactions, and is that right exclusive?
  • Can we license records through another party while you handle the rest of the wind-down?

Clauses to look for in the agreement itself#

The clauses to look for are the ones that give the provider rights rather than duties. Standard-form service agreements sometimes carry data provisions written for the provider's software platform, which read differently when applied to an entire company's records.

Clauses to look for in the agreement itself
ClauseWhat to check
License or use grantWhether the provider may use company data beyond performing the services
Aggregated or anonymized dataWhether the provider may keep or use de-identified company data after the engagement
ExclusivityWhether every asset sale, including data, must run through the provider
Fees on proceedsWhich asset types carry a fee and how proceeds are defined
Return and deletionWhat the provider deletes or returns at the end, and on whose instruction
AuthorityWho signs for the company after officers resign or the company dissolves

Questions about the people who know the systems#

People questions matter because records lose much of their usefulness when nobody can explain them. A provider that streamlines offboarding may end the employment of the only engineer who knows how the help desk links to the issue tracker, or the dispatcher who knows what each job status code means.

Ask the provider to plan around that knowledge rather than assume it can be rebuilt later. A short consulting arrangement for one systems person is often the cheapest protection the wind-down can buy.

  • Which employees hold admin rights or unwritten knowledge about our systems, and when does each one leave?
  • Will you capture field definitions, status codes and system links in writing before those people go?
  • Can a former employee be retained on a short consulting contract to support exports and questions?

Illustrative: a maintenance contractor protects its visit history#

Illustrative: a fictional commercial HVAC contractor is closing after its owner retires without a successor. Its field service system holds years of maintenance agreement records: recurring visit logs, equipment make and age, condition notes, refrigerant readings and repair recommendations, all tied to service locations.

The shutdown provider's draft agreement includes closing all software subscriptions within the engagement and deleting user accounts during offboarding. The owner's counsel adds a pause: no system is cancelled until its records are exported and assessed, and the company keeps an admin account until a records custodian takes over.

The assessment finds that the maintenance histories form a long, consistent record of equipment condition over time, the kind of longitudinal record that equipment makers, insurers and AI developers study. The company licenses a de-identified version with customer names and site addresses removed, keeps required financial records with the custodian, and lets the provider close everything else.

How SourceX works alongside a shutdown provider#

SourceX works alongside a shutdown provider on the operational records track only. The company stays the supplier, the SourceX five-step transaction (Supply, Rights, Preparation, Approval, Delivery) runs in parallel with the provider's checklist, and the company's signer approves every step.

The practical coordination point is timing. For any system that holds licensable records, the provider's cancellation date should come after the Supply and Preparation steps are complete.

The SourceX scope covers only the record families the company chooses to put forward, so it can run alongside a provider that handles domains, equipment, contracts and filings.

Frequently asked questions

What if I already signed the shutdown service agreement?

Read it for exclusivity, data use and deletion clauses, then send written instructions on what must be preserved and who approves cancellations. Many providers will accept a records pause if asked early. If a clause gives the provider rights you did not intend, raise it with counsel before any data moves.

Do these questions apply to an assignee in an assignment for the benefit of creditors?

Most of them do, but the roles change. In an ABC, the assignee takes control of company assets, including records, and decides on sales for the benefit of creditors. Ask the assignee the same control, deletion and licensing questions, knowing that the final decision sits with them.

Should the data license be signed before the shutdown service agreement?

Not necessarily. What matters is that the service agreement leaves room for a license: no exclusivity over data, no deletion before assessment and an admin account kept. The two agreements can then be signed in whatever order the wind-down needs.

Can the shutdown provider help prepare the data?

Possibly, for exports and inventories. Rights review and privacy preparation for an AI data license are specialized steps, so the company should know who performs them and how the work is checked, whichever party does it.

Who should negotiate these clauses?

The founder or CEO usually leads, with company counsel reviewing the data clauses. If a board member or investor is guiding the wind-down, share the answers with them, since exclusivity and fees on proceeds affect what creditors and stockholders ultimately receive.

Sources

  • Forbes reported on April 16, 2026 that a former CEO used wind-down firm SimpleClosure to close her company, after which its remaining digital records (internal chat, project-tracking tickets and emails) became items for sale to AI developers. Source

Related resources

See if your company qualifies

A short company assessment. No data uploads are needed.

See if your company qualifies