This page is for the restructuring professional advising that controller and for the archive custodian (a records-storage firm, hosting provider or IT firm) holding media on someone else's instructions. Neither renews, retrieves or copies anything for SourceX, nobody gathers drives, tapes or boxes to show what exists, and nothing here is legal advice or an estimate of what an archive is worth or when money could arrive.
Three names on one storage contract
In an operating company one name usually fills every role. In a restructuring the roles drift apart, and the archive review starts by writing each one down with the date it was checked.
| Role | Who it can be by now | What the role lets that party do | What it does not settle |
|---|---|---|---|
| Account holder of record | The operating company, a parent, an acquirer, or an entity that has since dissolved | Instruct the vendor under the contract | Which entity created the records, or who controls that entity today |
| Custodian | The storage firm, hosting provider or IT firm | Hold the media, bill for it and follow the account holder's instructions | Anything on the company's behalf, including a licensing conversation |
| Controller | Per SourceX's screening page, whoever directs the entity now: its board and CEO, an acquirer, or a trustee, receiver or assignee in a formal process | Decide whether the company discusses licensing, and direct the company's own affairs | Who holds which powers in a given process, which is for counsel |
| Counsel | The company's or the estate's lawyer | Say what must be preserved, for how long and for whom | The licensing question itself |
SourceX's screening page is the only authority rule used here: in an assignment for the benefit of creditors, a receivership or a bankruptcy case, another party may hold the assets, so the CEO's word may not suffice. For a company that has wound down, its matrix sends the question to whoever controls the estate, with counsel, and names archives deleted as the company closed as the usual failure. A storage contract's end date is one way that deletion arrives on schedule.
The storage-deadline escalation checklist
Start as soon as anyone learns that a storage contract holding company records is ending. Each line has one owner; a partner owns only the last two, and no line asks the vendor to do anything.
| # | Check | Who answers | If the answer is missing or no |
|---|---|---|---|
| 1 | The first date that matters: a notice deadline, any suspension the contract sets for unpaid invoices, or the end date, whichever falls first | The account holder's contract file and the vendor's own notices | Carry that earliest date to the controller now rather than waiting for the end date |
| 2 | Whose name is on the contract | The account holder of record | If a dissolved entity or one person holds it, the controller and counsel work out who acts; the vendor follows its contract |
| 3 | Whose records are in storage: which entity created them, which years, which systems | The controller, from what the company already knows about itself | If they are mostly clients' records, stop: the screening page lists client-owned material as usually not a fit |
| 4 | Who controls that entity today, and since when | The controller's counsel | If nobody can be named, stop |
| 5 | What must be preserved, for how long and for whom | Counsel | If a hold, order or retention duty reaches the archive, counsel sets what may be discussed; the licensing line waits |
| 6 | Renew, extend or let the contract end, decided for the company's or the estate's own reasons | The controller | Every choice is legitimate, and licensing is never the reason for one |
| 7 | Whether the controller wants to hear about SourceX at all | The controller, asked once by someone who already advises or serves them | A no, or silence past the date in line 1, ends it |
| 8 | A dated introduction, or a dated stop record | The partner, if registered and signed | Never a reminder to the vendor, a request to restore or a second ask |
The escalation runs one way: custodian to account holder, account holder to controller, with counsel beside the controller, and never sideways to SourceX or an introducer. A custodian that notices an unpaid invoice on a long archive tells its customer the date, and tells nobody what the boxes or buckets hold.
The end date is not the deletion date, and neither belongs to you
Line 1 asks for the contract's own dates because the clocks differ by provider, service and contract. Google's documentation for deleting a Google Cloud project says: "The project remains in a DELETE_REQUESTED state for 30 days. During this period, project owners can restore the project." It continues: "After 30 days, the project and all its resources are permanently deleted and can't be recovered." The same page notes, in paraphrase, that some services, Cloud Storage among them, may delete data sooner than that. Microsoft's page on canceling an Azure subscription says, in our paraphrase, that Microsoft waits 30 to 90 days before permanently deleting the data and that a canceled subscription can be deleted earlier, once a short waiting period has passed.
Both point the same way: the window belongs to the account holder. Google gives restore power to project owners, and Microsoft's outer limit is no promise, because deletion can come sooner. For boxes or tapes at an offsite records firm, the dates sit in that firm's contract and the customer's account file; this page describes no provider's terms. A partner who learns of a window uses it only to know when asking stops making sense. A single Salesforce org reaching renewal is covered in what happens to Salesforce data when a contract ends.
What outranks the end date
Each of these sits above any licensing question, and none is the introducer's to resolve.
- Preservation duties. Holds, retention periods and orders are the controller's to handle with counsel; a licensing conversation never loosens an obligation to keep or to destroy.
- The estate's control and personal data. The screening page's rights check for a closed company names both; what may lawfully be licensed is settled in SourceX's rights review, not guessed while a contract runs down.
- The custodian's own interest. A storage firm earns fees while an archive stays, and SourceX's sample agreement names the partner as "[an individual, or entity type and jurisdiction]", so the firm could also register and be paid if a license followed. It discloses both interests to the controller in writing and asks its own counsel whether to hold a partner seat at all.
- No copies "just in case". No export, sample, restore or spare drive is made for SourceX's sake, before or after the end date.
A no-copy escalation note, or a dated stop
When the controller wants to hear it, the note carries dates and roles, never data:
Illustrative. To [controller], copied to [counsel]: the storage contract for [entity]'s archive at [vendor] reaches its first deadline, the [notice, suspension or end] date, on [date]. The account holder of record is [name]. Renewing, extending or letting it end is your decision with counsel, and nothing here asks you to keep, copy or move anything. Separately, if useful: SourceX licenses business records directly from companies for AI training and evaluation, and the company can apply itself. I am a registered SourceX partner and could be paid if a license followed; that would not reduce what the company receives.
The last clause rests on section 4 of the terms: "The referral reward is paid separately by SourceX and is never deducted from the supplier's agreed compensation."
When the answer cannot come in time, a stop record replaces the note. It holds the date, the line of the checklist where the file stopped, who made the call and one reason: the first deadline passed before a controller was named; the controller let the contract end; counsel's preservation scope rules the discussion out; the records belong to clients; peak headcount stayed below 50 full-time employees; or the company already had contact with SourceX, which makes it a duplicate under section 3. It describes none of the archive's contents.
Two storage contracts, two endings (Illustrative)
Illustrative. Generic companies with invented facts; no outcome, value or timing is implied.
A cloud account in a parent's name. A freight brokerage that peaked at about 240 full-time employees, and now has 12, enters an assignment for the benefit of creditors. Its history sits in a cloud storage account in its parent's name, with a non-renewal notice due in three weeks. The restructuring professional advising the assignee runs the checklist. Line 2 points to the parent; line 4, by the assignee's counsel's account, puts the brokerage's records under the assignee's control. Counsel wants the archive kept for claims work, so the assignee renews for that reason alone. Asked once, it wants to hear more and applies for the company.
A vault with nobody behind it. An offsite vault holds tapes and boxes for an engineering consultancy that peaked at about 90 full-time employees. Invoices stopped a year ago. The vault's account manager, who is also a registered SourceX partner, calls the last account contact, a former office manager, who says the company was dissolved and cannot say who acts for it now. Line 4 fails. The account manager records a stop with that reason and date, the vault follows its own contract, and nobody asks former staff for tapes, drives or passwords. A longer search, when a rights holder might exist, is in who can authorize a referral for a closed business.
Fit, credit and reward once the controller says yes
For a closing company the screening page reads size at the full-time headcount's peak (50 or more, contractors excluded), not today's, and the decision-maker may be the estate's controller rather than the CEO; the company still needs years of its own records and the rights to license them. 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.
Credit follows section 2: "The first valid introduction of a new company within the 90-day attribution window receives credit when that company submits a verified application." Dated records decide it, never a link click, and an introduction made before the controller has decided lapses if the company applies more than 90 days later. Whoever submits must already have signed the Channel Partner Agreement. Under section 5 nothing is payable before a license is accepted and paid, and no page can say what a closing company's records might bring.
Where a deadline checklist can mislead
- Processes differ. Assignments, receiverships and bankruptcy cases move control at different moments; counsel says which applies.
- Provider clocks vary and change. The Google Cloud and Azure examples were read on 2026-10-28 and are examples, not rules for other services or contracts.
- Letting go is often right. Renewal costs money the estate may not have, and a record of a deliberate end is a complete outcome.
- The custodian may never learn who controls. Silence after line 1 is a stop, not a reason to look harder through former staff.
- Neighbors have their own pages. Every system switched off together: the guide to timing a question before systems go offline. Whether holding a copy confers a say: the holder-versus-decider checklist. Value talk: how to refer a business in restructuring without promising recovery value. A vendor contract ending at a trading company: the referral questions after a long-term vendor contract ends.
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.
If line 7 brings a yes before the first deadline, register as a partner and sign before submitting, test the company once more against who qualifies, and keep the program terms with your file.