Wind-downs and transitions
What happens to company Slack, email and Jira when a startup shuts down?
By SourceX Editorial · Reviewed by Noah Loul ·
Short answer
When a startup shuts down, its Slack workspace, email accounts and Jira projects generally remain company property, but vendors suspend, downgrade or delete them on their own schedules once billing stops. The board should name a records custodian, export and verify each system first, and decide which employee communications stay out of any sale or license.
Key takeaways
- The company, not its founders or employees, generally owns workspace content, subject to vendor terms and privacy obligations.
- Vendor terms, not the shutdown date, decide how long Slack, email and Jira data survive after payments stop.
- Direct messages, private channels and personal mailboxes are usually kept out of any asset sale or data license.
- Jira issues linked to code changes and support tickets are often the most useful records a software startup leaves behind.
- A board resolution naming a records custodian keeps the archive from becoming nobody's job.
Who owns Slack, email and Jira data after a shutdown?#
Slack messages, company email and Jira issues are generally owned by the company, not by the founders or the employees who wrote them. Workspace content is created on company accounts in the course of the business, and the vendor holds it under the company's subscription terms, so it stays a company asset until the company sells, transfers or deletes it as part of the wind-down.
Ownership is not the same as freedom to use. Employment agreements, privacy notices, customer contracts and the vendor's own terms all limit what the company can do with that content. Privacy laws such as the California Consumer Privacy Act may give some employees rights over personal information in work systems, and whether any law applies is assessed with counsel rather than assumed.
Founders often assume they can take a copy for themselves. Unless the board or an asset purchase agreement allows it, a founder's copy of the Slack export is still company property held by an individual, which can cause friction with creditors, investors and former employees.
What happens to each system when payments stop#
When payments stop, each vendor follows its own terms: accounts typically move through suspension, a retention or grace period, and then deletion. The timing differs by vendor and plan, so the subscription agreement and the vendor's current documentation are the only reliable guide for your account.
| System | When billing stops | What is at risk | Decision to make |
|---|---|---|---|
| Slack | Paid features end and the workspace falls back to the free plan, which limits how much message and file history is kept and visible | Older history, private channel and direct message exports, file access | Export before downgrading, and decide whether private channels and direct messages are in or out |
| Google Workspace or Microsoft 365 email | Accounts are suspended, then deleted under the vendor's terms | Mailboxes, shared inboxes, calendars and each user's drive files | Export mailboxes, especially shared inboxes and accounts of departed staff |
| Jira and Confluence | Site access ends, then the vendor deletes site data | Issue history, comments, attachments, links to commits and pages | Export with change history and links intact |
| GitHub or GitLab | Paid organization features end, and access depends on the plan the account falls back to | Code, pull requests, review comments, build history | Mirror repositories and export pull request discussions |
| Help desk | The account closes and data is deleted after the vendor's retention period | Tickets, internal notes, attachments, satisfaction ratings | Export tickets with full comment threads |
A shutdown timeline for company records#
A shutdown timeline for records runs alongside the corporate timeline, and the two drift apart easily. Counsel and the board handle the legal steps of a wind-down, while exports are often left to whoever still has admin access in the final stretch.
Assignments for the benefit of creditors and bankruptcy add another layer, because an assignee or trustee may take control of the records and decide what is preserved. In those cases the board's job is to hand over complete, documented exports rather than half-closed accounts.
| Stage | What happens to records | Who should act |
|---|---|---|
| Board decides to wind down | Systems are still live and fully staffed | Board names a records custodian and orders a freeze on deletions |
| Employee notice and departures | Admins leave, accounts are removed, and files they owned can disappear | Custodian transfers file ownership and keeps departing mailboxes |
| Asset sale, ABC or other disposition | A buyer or assignee may take some systems or records | Counsel defines what transfers and what is excluded |
| Final payments and cancellations | Vendors begin suspension and deletion | Custodian confirms verified exports before each cancellation |
| Dissolution | The entity is dissolved, but retention duties for some records continue | A named person or successor holds the archive under a written plan |
Employee messages and privacy: what boards should exclude#
Employee messages are the most sensitive part of a startup's records, and boards usually exclude direct messages, private channels and personal mailboxes from any sale or license. Those spaces mix work with health updates, family matters, salary talk and complaints, and employees did not write them expecting outsiders to read them.
Public channels, shared inboxes and project tracker comments are different, but not automatically usable. Before any reuse beyond the company's own retention needs, counsel typically reviews what employee notices and handbooks said about monitoring and use, which privacy laws may apply, and whether names and personal details can be removed reliably.
Former employees can raise questions long after a shutdown. A short written policy on what was kept, why, and who can access it makes those questions far easier to answer than an undocumented export sitting in a founder's personal cloud account.
Which records may still have value#
The records most likely to keep their value are the ones that show real work from request to outcome. For a software startup, that usually means Jira issues linked to commits, pull requests and review comments, support tickets linked to the fixes they triggered, and incident channels that record how problems were diagnosed.
Value depends on rights as much as on content. Customer code, customer data inside tickets and third-party material embedded in documents are typically carved out, and what remains is de-identified before anyone outside the company sees it.
- Jira or Linear issues with full change history, linked to commits and releases.
- Pull requests with review comments, including rejected and reworked changes.
- Support tickets with internal notes and resolution outcomes.
- Shared inboxes such as support or sales, rather than individual mailboxes.
- Design documents and postmortems kept in Confluence or Notion.
- Public engineering channels used for incidents and releases.
Illustrative: a startup board settles its records plan#
Illustrative: a fictional accounts-payable automation startup decides to close after its largest customer leaves. It runs on Slack, Google Workspace, Jira, GitHub and Intercom, and several engineers have already gone, taking admin rights with them.
At its final meetings the board passes a resolution naming the former head of operations as records custodian, freezing deletions and setting a cut-off date for exports. The custodian recovers admin access through the identity provider, exports Jira with change history, mirrors GitHub and pulls Intercom conversations with internal notes. Direct messages and private channels are excluded by resolution, and individual mailboxes are kept only for the period counsel advises.
Before cancellation, the board asks whether the engineering and support history could be licensed. A metadata-only review shows several years of linked issue, code and ticket records, so the archive is preserved intact for that assessment instead of being deleted with the subscriptions.
How SourceX approaches shutdown records#
SourceX approaches shutdown records by assessing them before anything is shared or cancelled. The fit check uses metadata only: which systems exist, how much history remains and which record families link to outcomes. The rights review then looks at employee notices, customer contracts and vendor terms for each record family before any scope is proposed.
If records proceed, the SourceX five-step transaction (Supply, Rights, Preparation, Approval, Delivery) keeps the company, or the officer or assignee acting for it, in control of every step. Personal and confidential details are removed during preparation, the company keeps ownership because the records are licensed rather than sold, and a SourceX Evidence Packet captures provenance, licensing rights, permitted use, the privacy record and release authorization.
Frequently asked questions
Can a founder keep a personal copy of the company Slack?
Not without authorization. The workspace content generally belongs to the company, so a personal copy needs board approval or a provision in a sale or wind-down agreement. Even with approval, the copy carries the same privacy and confidentiality obligations as the original, and it should be listed in the records plan.
Do investors have a right to the company's records after a shutdown?
Not usually to the whole archive. Investors may have contractual information rights in their financing documents and, as stockholders, inspection rights under state corporate law, but these generally cover specified books and records rather than every Slack message or mailbox. Requests go through the board, the wind-down officer or, in an insolvency process, the assignee or trustee, and counsel can confirm what applies.
If an acquirer buys the IP, does Slack go with it?
Only if the purchase agreement says so. Asset deals list what transfers, and communications archives are often excluded or transferred only in part because of privacy concerns. Code repositories and issue trackers are more commonly included, since they document the technology being bought.
Can former employees ask for their messages?
Depending on where they live and which laws apply, some former employees may have rights to request access to or deletion of personal information the company holds. Keep a contact point for such requests after the shutdown, and decide with counsel how requests will be handled once the entity is dissolved.
Is it safer to delete everything at shutdown?
Not necessarily. Deleting records that must be kept for tax, employment, litigation or contract reasons can create liability, and deletion also destroys any remaining value. The better path is a written plan: keep what is required, preserve what may be valuable for assessment, and delete the rest on a documented schedule.
Related resources
See if your company qualifies
A short company assessment. No data uploads are needed.