# Introducing records held by former vendors | SourceX

Canonical: https://refer.sourcex.si/guides/how-to-introduce-a-business-with-records-across-former-vendors
Last updated: 2026-11-04

Introduce the company, not its former vendors. When old records sit with several vendors a business no longer uses, the company's CEO, or whoever controls the estate if it has closed, decides whether to talk to SourceX, and each vendor acts on that party's instructions under its own contract. Map each copy at metadata level, note whose instruction its holder follows and when it may be deleted, and give the map to the decider. Nobody gathers, restores or copies anything to make the introduction look complete.

Scattered records are common after a company changes systems, outsources work or winds down. The scattering changes what the decider needs to know before saying yes. It does not change who decides, and it never turns a vendor into a second door.

## Why scattered records change the introduction, not the decider

Each former vendor is a custodian of one copy. Finding storage is not establishing licensable rights, and holding a copy is not deciding about it: the general case is set out in [an archive custodian is not always the licensing decision-maker](/guides/an-archive-custodian-is-not-always-the-licensing-decision-maker). With several custodians, three temptations appear that a single archive never raises.

- **Consolidating "to show SourceX".** Pulling copies into one place before an introduction is a data project with its own rights, privacy and cost questions. It is the company's call, later, if ever.
- **Asking the vendors directly.** A former vendor owes its duties to its customer. Questions about what it holds come from the company or the estate's controller, not from the person introducing the company.
- **Rebuilding the vendor list from what you saw at work.** A restructuring adviser may have seen the accounts-payable ledger or the contract register. That knowledge can prompt one question to the decider; it is not material for the map.

The sample Channel Partner Agreement draws the same line at section 4.2: "This Agreement gives Partner no authority to share a supplier's inventory, records, raw data or personal information, or to access extraction systems."

## Name the decider before listing a single vendor

Name the decider first, with the date you checked.

| Company status | Who decides about licensing | What SourceX's screening page says |
|---|---|---|
| Operating | The CEO | The CEO authorizes a licensing discussion and signs for the company |
| Acquired | The acquirer's CEO; before closing, the target's CEO | After an acquisition the acquirer's CEO decides for the company |
| Wound down, or in a formal process | Whoever controls the estate | The CEO alone may not be enough; a trustee, receiver or assignee may control the assets |

Then record the context the decider can give from memory or the company's own files: which systems were retired and when, which services were outsourced, who held each vendor relationship, and whether any storage contract is still running. The vendor list should come from the decider, not from the introducer. Where a closed company's decider is hard to find, [who can authorize a referral for a closed business](/guides/who-can-authorize-a-referral-for-a-closed-business) and [locating the authorized successor](/guides/how-to-locate-the-authorized-successor-to-a-wound-down-company) cover the search.

## The vendor-custodian contact map

One row per former vendor, filled in by the decider or their team, with every unknown left as unknown. Rows follow the copy, not the vendor's brand.

| Former vendor type | What the copy is, in a phrase | Whose instruction the holder follows | Clock the company knows of | Who would contact the holder | Rights note for review |
|---|---|---|---|---|---|
| Software tenant after the subscription ended | The company's data still inside the vendor's service | The company, as account holder, through today's decider | The vendor's documented post-termination stages, dated | The company's account owner | Usually the company's own records; any customer data inside is a review question |
| Former managed IT provider | Backups made while the provider ran the systems | The company, under the ended service agreement | The provider's backup retention, if known | The company | Same as the systems backed up |
| Offsite records storage | Boxes, tapes or drives held under a storage contract | The account holder named on the contract | Contract end date and any destruction instruction | The account holder | Depends on what the boxes hold; nobody opens them to find out |
| Outsourced service provider | Notes, tickets or files the provider made while serving the company | The company, subject to the services contract | The provider's own retention | The company | Who owns work the provider created is a contract question for review |
| A vendor that was itself sold or closed | Whatever it held, now with a successor | The successor custodian, under its own terms | Unknown until the company asks | The company | As above, plus the change of custodian |

Software clocks are documented by each vendor and differ by contract. Microsoft's page on business subscriptions, for example, describes a subscription passing through "Active > Expired > Disabled > Deleted", says that for most offers the expired stage lasts 30 days and the disabled stage 90, and notes that a new subscription of the same type does not bring back data from a deleted one (paraphrase). The decider dates each row's clock from the company's own contract, not from a general rule.

**Method note.** The columns follow SourceX's screening page and program terms, read on 2026-10-28, plus one vendor's published lifecycle as an example of a software clock. Rows are vendor types, not findings about any vendor. The map has not been tested on real archives; SourceX publishes no figures on how often scattered records lead to a license.

## Preservation and transition constraints across several custodians

Several custodians mean several clocks, and none of them belongs to the introducer.

- **Different end dates.** A storage contract may run for years while a software tenant moves toward deletion within weeks. Tell the decider the earliest documented date; what to keep is the company's decision, made with counsel. The single-contract case is covered in [the archive review before a storage contract ends](/guides/the-archive-review-before-a-storage-contract-ends).
- **Holds that reach some copies.** A litigation hold may cover one vendor's copy and not another's. Counsel sets that scope, and any held copy stays out of the conversation until counsel says otherwise.
- **Nothing kept for SourceX.** No subscription is renewed, no backup restored and no box retrieved for the sake of an introduction.
- **Credit does not wait for vendors.** Under section 2 of the terms, the first valid introduction in the 90-day window is credited once the company submits a verified application. Make the introduction when the decider is ready, not to beat a vendor's clock.

## An introduction with no attachments, or a dated stop

The introduction carries the decider's name and role with the date checked, the company's fit facts in the decider's words, the map's rows as categories with their known clocks, and a line saying nothing has been opened, gathered or sampled. No file, export, screenshot or vendor contact detail travels with it.

Stop, and write a dated note instead, when:

1. Nobody with authority can be named, or the claimed decider's role cannot be confirmed.
2. Every row's documented clock has passed and the decider confirms nothing remains.
3. The decider says no, or does not answer after one follow-up.
4. The only way to describe the records runs through the introducer's own engagement files.

The note records the company, the date, which condition applied and who was told. It is a finished answer, not a failure. For archives nobody can open at all, [a referral summary for an offline business archive](/guides/a-referral-summary-for-an-offline-business-archive) shows how to describe what is known from labels and invoices.

## One company, five former vendors (Illustrative)

Illustrative. An invented company with invented facts; no outcome implied.

A 260-person field-services company has changed systems three times in twelve years. Its CEO, asked by a long-time restructuring adviser whether she would like to hear about SourceX, says yes and asks her IT manager to fill in the map.

| Row | Copy | Clock the company knows of | Status for the introduction |
|---|---|---|---|
| Old helpdesk tenant | Nine years of service tickets | Disabled stage, deletion date in the vendor notice | Listed, with the date |
| Former IT provider | Server backups from 2016 to 2020 | Unknown | Listed as unknown |
| Offsite storage | Job files from before 2014 in boxes | Contract runs to next year | Listed; nothing opened |
| Outsourced call center | Call notes made for the company | Unknown | Listed; rights flagged for review |
| A dispatch-software vendor since acquired | Unknown | Unknown | Left out until the company asks the successor |

The adviser sends a short introduction naming the CEO, the fit facts she gave and the four listed rows. SourceX's review, not the adviser, decides which rows matter and what the company's rights cover.

## Fit, credit and reward once the decider says yes

Scattered storage changes none of the checks: at least 50 full-time employees at the company's peak (contractors aside, and the peak still counts after a wind-down), records it produced itself over years, rights it can actually grant, a CEO or estate controller who wants the conversation, and a fit with a current program. 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.

The introducer signs the Channel Partner Agreement before submitting, and one partner is credited per company. Any reward is the greater of $50,000 plus 5% and 15% of what SourceX actually pays the company, with no cap for the company and its corporate group, paid separately and never taken from the company's payout. Nobody can say in advance what scattered records are worth or when money would arrive.

## Limits of a vendor-by-vendor map

- **The decider's memory is incomplete.** A vendor nobody remembers is missing from the map, and that is acceptable; the map is not an inventory.
- **A clock may already have run.** A row can describe a copy that no longer exists.
- **Rights do not follow custody.** A full row says where a copy sits, never that the company may license it.
- **Vendors' terms change.** A documented lifecycle is accurate on the day it was read.

## 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.

When the decider has filled in the map and wants the conversation, [register](/register) as a partner, hold the map's facts up against [who qualifies](/who-qualifies), and keep the [program terms](/terms) version you read beside the introduction you send, which carries no file.

## Sources

- https://refer.sourcex.si/who-qualifies
- https://refer.sourcex.si/terms
- https://sourcex.si/documents/partner/SourceX_Channel_Partner_Agreement_Sample.pdf
- https://learn.microsoft.com/en-us/microsoft-365/commerce/subscriptions/what-if-my-subscription-expires?view=o365-worldwide
