Google Workspace
Microsoft 365
What should an owner verify before canceled SaaS seats affect archive access?
Verify the clock, the person and the policy. The clock is the vendor's documented window after a seat or subscription ends. The person is whoever still holds admin rights during that window. The policy is the company's own retention schedule and any legal hold that overrides the default.
Seat changes are where archives quietly go missing. A department downsizes, finance removes ten licenses at renewal, or a team moves to a new tool and the old subscription runs out. Nobody decides to delete years of tickets or mail; the default does it. For an introducer (an MSP, a fractional CFO, a systems consultant), the moment the client mentions "we are cutting seats" or "we are moving off X" is the moment to ask what happens to the history.
The timing map: documented windows, checked 2026-10-18
Each row comes from the vendor's own documentation. These are defaults. Contract terms, plan type, how the subscription was bought and active holds can lengthen or shorten them, so the owner should confirm the figure for the company's own account.
| System and event | Documented default after the event | What the owner should confirm |
|---|---|---|
| Microsoft 365: license removed from one user (Exchange Online) | 30-day grace for mailbox data; about 60 days if Delicensing Resiliency is turned on | Whether the mailbox is on hold, and who reassigns or preserves it before day 30 |
| Microsoft 365: business subscription ends | Expired 30 days, then Disabled 90 days for most offers (120 days in all); admins only during Disabled | How the subscription was bought, since canceled monthly plans can skip Expired |
| Google Workspace: user deleted | Account and data restorable for up to 20 days | Whether Drive ownership was transferred first, or the user could be suspended or archived instead |
| Slack: workspace on the free plan | Recent 90 days visible; data older than one year may be deleted on a rolling basis | Whether the downgrade has already happened and how much history is past one year |
| Zendesk: account canceled | Reactivation possible within 90 days; automated deletion begins after | Who can request a temporary reactivation to export, and by what date |
| Atlassian cloud: paid subscription deactivated | App data kept 60 days (15 days for free plans) | The deactivation date, which follows the end of the billing period |
| Salesforce: contract terminated or expired | Data made available for export on request made within 30 days | That the request is made in time, in writing, by an authorized contact |
Slack
Zendesk
Atlassian
SalesforceThe pattern matters more than any single number. Seat-level events (one user) tend to run on shorter clocks than subscription-level events (the whole tenant), and the shortest window in the table belongs to a routine offboarding step, not a dramatic cancellation. Two systems have their own walkthroughs: Microsoft 365 after a subscription ends and a Slack downgrade to the free plan.
The owner-approved preservation sequence
Illustrative. A 260-person logistics firm plans to drop its old help desk at the end of the quarter and remove 40 Microsoft 365 licenses from departed staff the same month. The sequence below is what the owner, not the introducer, approves and assigns.
| Step | Owner action | Done by | Deadline anchor |
|---|---|---|---|
| 1 | List every system losing seats or a subscription in the next 90 days | IT lead | Renewal calendar |
| 2 | Record the documented window for each, from vendor docs or the account rep, in writing | IT lead | Before any license is removed |
| 3 | Check legal holds and the company's own retention schedule | Counsel or compliance | Before step 4 |
| 4 | Decide what to keep: reassign, archive license, convert to shared or inactive storage, or export to company-controlled storage | Owner or COO | Inside the shortest window |
| 5 | Confirm the preserved copy opens and is complete | IT lead | Before the vendor clock ends |
| 6 | Only then remove seats or let the subscription lapse | Finance | After step 5 sign-off |
The point of step 6 is order: licenses come off after preservation, not before. Where a firm has already removed seats, step 2 tells it how many days remain.
Why does this timing matter to an introduction?
Because a licensing discussion needs records that still exist and that the company controls. Years of resolved tickets, project histories and account email can be relevant to AI training and evaluation, but only if they survive the tool change. A company whose history disappears at renewal may have little left to discuss; the deleted-archives guide explains why.
Raise it as a records-continuity question first. The owner benefits from a preservation plan whether or not a data license ever follows. If the owner then wants to know whether the preserved history could be licensed, that is when an introduction to SourceX makes sense. System-specific detail is in the Zendesk export guide, the NetSuite project guide and the Confluence guide. MSPs can fold the questions into an offboarding checklist, and the opportunity finder suggests which other conversations to start by role and sector.
NetSuiteCompany qualification questions
Keep discovery at metadata level: what, how much, how long, which system, who owns it.
- Which records exist? Resolved tickets, mailboxes, project or wiki history, CRM activity. Note the system name and rough span, such as "help desk, about eight years".
- Who owns them? The company, or does a customer contract restrict reuse? The answer is a yes, no or unknown, not a copy of the contract.
- Who can authorize a licensing discussion? The CEO, with counsel. An IT lead can preserve data but rarely decides to license it.
- Does the company meet the basics? 50+ full-time employees at peak (contractors excluded), documented operating history, rights to license and an authorized contact. Companies in the U.S., Canada and the EU qualify, as do companies in the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia when at least 70% of the data is in English.
What stays unknown until SourceX reviews it: whether there is dataset demand for those records, the result of the rights review, what preparation is needed, and what the company would be offered. Partners never ask for exports, screenshots or logins.
Limits and unanswered questions
The table shows documented defaults only. It does not cover every product tier, regional cloud, reseller arrangement or hold configuration, and vendors change these pages. It is not legal advice and not a recommendation to keep or delete anything. If a vendor's page and the company's contract disagree, the contract and the vendor's written answer govern.
Two things are separate and should stay separate in any conversation. Company compensation is what SourceX pays the company under its own agreement if a license completes. A referral reward is what SourceX pays the introducer, separately, and it never reduces the company's payout.
Next step
Refer a company. No cap on rewards. Default reward on a company's first qualifying transaction: the greater of $50,000 plus 5% and 15% of Actual Supplier Payout, with no cap; further qualifying transactions first agreed within 12 months of the first Closing pay 15%. Eligibility and payment conditions apply, including the USD 100,000 Minimum Transaction, and a signed Schedule A or addendum can differ. A lead, meeting or signature alone does not trigger payment.
Illustrative: if a company received $120,000 for a qualifying completed handoff, the default reward would be $56,000. If a client's archives are safe and its owner wants to explore licensing them, register as a partner, check the company against who qualifies, and read the program terms before you make the introduction.