Has the company verified that archived records can be restored with their links?
A routine restore test shows that files come back. It does not always show that relationships come back: the reference from a support ticket to an email thread, from a purchase order to its approval, from a project folder to the client record. That second test is the one that matters for a data introduction, because linked records describe how work was done, not just what was stored.
Public guidance already expects a company to prove its copies work. NIST's contingency planning guide (SP 800-34) calls for testing backup media on a schedule so that files come back without errors, and CISA advises checking that backups are both available and intact as part of disaster recovery. A vendor switch forces that proof onto the project plan. One extra question about links rides along at no cost.
Where things land after recovery also varies. In Microsoft 365 Backup, OneDrive and SharePoint content may come back at a fresh URL or site, and Exchange items return into the existing mailbox under a new folder. A link written against the old location may or may not follow; only the client's own test can say.
The link-survival check (evidence asset)
Illustrative. A 240-person facilities services firm is moving from one backup vendor to another. Before the old contract ends, its IT lead restores a sample case and checks each link. The partner records only the answers, never the records.
| Link in the restored case | What the IT lead checks | Survived? | Who can answer |
|---|---|---|---|
| Ticket to original customer email | The thread opens from the ticket after restore | Yes | Service desk lead |
| Ticket to technician dispatch record | Dispatch ID resolves in the field service tool | Yes | Operations manager |
| Change approval to approver identity | Approver still maps to a named role, not a deleted account | No, account removed | IT lead |
| Invoice to ticket reference | Finance system still carries the ticket number | Yes | Controller |
| Shared folder link inside ticket notes | Link opens the restored folder, not a dead path | No, restored to new location | IT lead |
What this tells you: three of five links survived, so the company holds multi-system case histories, and two gaps are known and fixable. That is enough to raise the possibility of an introduction with the owner. It is not a judgment on value; SourceX decides fit after its own review.
Why restorable workflow context is easy to overlook
Backup projects are scoped by volume, recovery point and recovery time. Nobody owns the question of whether a 2019 case still makes sense when restored. The archive versus backup comparison explains why backups are built to bring systems back, not to keep records readable for years, and the email archive versus backup page shows where long-lived mail usually sits. The workflow context guide covers why linked histories beat isolated files.
Which four metadata questions follow the restore test?
Once the client has answered the link question, four follow-ups tell you whether an introduction makes sense. Raise them only after the migration plan is signed off, so they never compete with the technical work, and keep only the answers.
| Dimension | What you are trying to learn | Answer that moves things forward (Illustrative) |
|---|---|---|
| Scope | Which systems carry the deepest case or project history: service desk, field service, finance, mail | "Service desk and finance; mail is mostly noise" |
| Depth and volume | The first year on record and a rough count of cases or jobs | "Since 2016, about 90,000 work orders" |
| The surviving copy | Whether old restore points travel to the new vendor, or some systems will live only in the outgoing vendor's storage | "Anything older than 12 months stays behind" |
| Ownership and limits | The executive accountable for those records, and any client contract that restricts reuse | "The COO; a few national accounts have terms we would need to read" |
"Contract terms unknown" is a perfectly good answer in the last row. The meeting agenda turns these into a timed script; here the point is what each answer tells you.
If historical restore points will not move and the old contract has a confirmed end date, that is a documented access event, and the owner may want to decide about an introduction before it. If they will move, there is no reason to hurry.
How do you disclose the reward and ask for permission?
Disclosure comes before any introduction, in your own words. The owner should hear three facts from you: you are a SourceX referral partner; SourceX licenses approved business data directly from companies for AI training and evaluation; and you could earn a reward if a qualifying license completes, paid by SourceX on its own account and never taken from the company's share. Only then ask whether an introduction is wanted at all.
A no changes nothing about the migration. A yes means the introduction is addressed to whoever can authorize a licensing discussion, copies the IT lead only if they ask, and states that no records have changed hands.
Does the company qualify, and who can authorize the conversation?
The company needs 50+ full-time employees at peak (contractors excluded), a documented operating history, rights to license the records, 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.
- Records that exist: the systems and years the owner named, at metadata level.
- Who owns them: the company, subject to any client contract limits the owner flags.
- Who can authorize: the CEO, who in an owner-run company is usually the owner. Your IT contact can join but usually cannot approve.
- What stays unknown until SourceX reviews it: SourceX's current data needs for those records, the rights review outcome, scope, price and any reward.
Before submitting, sign the Channel Partner Agreement. The first valid introduction within the 90-day window is credited when the company submits a verified application, one partner per company. The MSP partner page covers disclosure in client relationships, and the network opportunity finder helps you list other clients mid-migration. Reward mechanics are on /rewards; other partner types are on the partner hub.
Go deeper on the backup vendor switch
- Backup vendor switch meeting agenda: a timed 15-minute agenda for the owner conversation.
- Backup vendor switch archive context checklist: a tick-box checklist to complete before the old vendor stops holding the data.
- Backup vendor switch introduction email: a ready-to-edit email for introducing the owner to SourceX.
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 the owner opted in after the link-survival check, register as a partner, confirm the company against who qualifies, and read the program terms before you make the introduction.