Archive conversations start in the middle of other work: a migration leaves the old system read-only, a vendor announces a sunset, a cost review cuts the archive tier. The client turns to the person who knows the system and asks the obvious question, "is it safe to do anything with this?" Reassurance feels helpful. It is also the moment a partner can make a promise nobody can keep.
When archive access becomes the topic
The events below put an archive on the table. Each comes with something you can verify yourself and someone else who decides.
| Event | What you can verify as custodian | Proof to point to | Who decides what happens next |
|---|---|---|---|
| A migration leaves the old system read-only | The date range the old system holds | The cutover plan | The client's CEO |
| The archive vendor announces end of support | The date in the notice | The vendor's written notice | The client's CEO |
| A license downgrade removes archive search | Which features stop, per the vendor's documents | The renewal quote and product terms | The client's CEO, often prompted by the CFO |
| A shorter retention rule is proposed | Which records the rule would delete | The change request | The client's CEO, with the records owner |
| An acquired company's archive is being folded in | Which entity's records these are | The integration plan | Before closing the target's CEO; after closing the acquirer's CEO |
Whoever owns the archive budget, usually an IT director, COO or controller, is a natural internal sponsor. The CEO authorizes any licensing discussion. A deadline is real urgency only when a dated document backs it; the archive deadline verification log shows how to check one, and the software rationalization guide covers cost reviews that switch archives off.
The access claim verification checklist
Eleven sentences a partner is tempted to say during an archive conversation. For each: who can verify it, what the published record actually supports, and what to say instead. SourceX's lines come from its trust center as read on 2026-10-27.
| # | Tempting sentence | Who can verify it | What the record supports | Say this instead |
|---|---|---|---|---|
| 1 | "Your archive is complete back to 2009." | You, for the dates; nobody, for "complete," without a check | The dates the system shows | "The archive holds records dated from 2009; whether anything is missing would need checking." |
| 2 | "Access ends on 31 March." | The archive vendor | A dated written notice, if one exists | "The vendor's notice dated [date] says read access ends on 31 March." |
| 3 | "SourceX holds the usual security certifications." | SourceX's trust center | It lists its certification work as in progress, with no report or certificate issued yet | "SourceX's trust center shows where its certification work stands; here is the page." |
| 4 | "Your data will be anonymized." | SourceX's trust center | It says SourceX de-identifies data through approved processing routes before use or sharing, that no method is perfect, and that the supplier agreement records that re-identification may still be possible | "SourceX describes how it de-identifies data, and the limits, on its trust page." |
| 5 | "Your files never leave your servers." | SourceX, deal by deal | It says large datasets can stay in the supplier's own storage or ship on encrypted drives | "Large datasets can stay in your storage or travel on encrypted drives; the route is agreed with SourceX." |
| 6 | "You decide what goes in." | SourceX's trust center | It says the supplier decides which systems, records and date ranges are in scope | Fine to say, with the link |
| 7 | "Nothing moves until you sign." | SourceX's trust center | It says nothing is delivered until the supplier signs the Master agreement and the deal's Dataset Deal Confirmation and SourceX gives the go-ahead | Fine to say, with the link |
| 8 | "I'll pull the export for you." | Nobody: it is not yours to offer | The partner agreement gives a partner no authority to share a company's records or access extraction systems | "I won't touch the archive for this; SourceX arranges any preparation with you directly." |
| 9 | "Nobody else will ever see it." | The agreement the company would sign | It says SourceX authorizes its customers' access to deidentified datasets for each delivery and, at Closing, may use, sublicense and distribute the deidentified dataset as the agreement allows | "Who receives what is set in the agreement you would sign; the trust center describes it." |
| 10 | "If anything went wrong, you'd be covered." | SourceX | It says affected access links can be revoked and affected suppliers notified, with the full incident process shared on request | "Ask SourceX for its incident escalation process; it shares it on request." |
| 11 | "SourceX will answer our security questionnaire." | SourceX | It says questionnaire responses, a business continuity overview and a DPA where applicable are shared privately after review | "SourceX shares procurement material after review; ask it directly." |
Rows 6 and 7 are the only SourceX sentences safe to say in your own voice, and even those go out with the link. Rows 3, 4 and 9 cause the most trouble. Row 3 because a certification is easy to assume, and SourceX states plainly that none of the three it is working toward has been issued. Row 4 because "anonymized" sounds absolute, and neither SourceX nor NIST treats it that way: NIST's report on de-identifying personal information says the technique can reduce privacy risk and that de-identified data can sometimes be re-identified (paraphrase of its abstract). Row 9 because the honest answer depends on a contract the client has not seen yet. Certification questions get a fuller treatment in discussing audit status without overstating certifications, and security questions raised before anyone is introduced in when security questions arrive first.
Method. The eleven sentences are the claims that come up when a client asks an IT partner about archive security. Each was checked on 2026-10-27 against the page that can verify it: SourceX's trust center for SourceX's controls, the partner agreement for what a partner may do, and NIST's de-identification report for the general point about re-identification. The checklist reports what SourceX publishes; it does not test or rate those controls. The trust center lists dedicated data rooms, independent security assessments and direct connectors as planned, so never describe them as current.
Three voices in one archive conversation
An archive conversation needs three voices, and a partner who speaks in all three has overstepped.
| Voice | Speaks about | Where its authority comes from | Never speaks about |
|---|---|---|---|
| The custodian (you, if you run the system) | What the system holds, its dates, its access deadlines | The service agreement, and the client's agreement to share the facts | SourceX's controls, or whether to license |
| The owner (the client's CEO) | Whether to talk to SourceX, what is in scope, who acts for the company | Owning the company and its records | SourceX's controls |
| SourceX | Its own process, controls and terms | Its published pages and, later, its signed agreements with the company | The client's systems before the client describes them |
The partner agreement backs the line between the first and third rows. A partner is not SourceX's agent and cannot commit it to prices, licenses, payouts or other obligations (7.1), and a promise about SourceX's security is exactly that kind of commitment. The same agreement gives a partner no authority to share a company's records or reach into extraction systems (4.2), and bars collecting or keeping dataset copies through the program without separate written authorization (4.4). For the client's side of an export, should the company go ahead, the live guide on MSP client data licensing security covers the questions to settle, and the encrypted drive versus cloud transfer comparison covers delivery routes.
A script for the archive meeting, and an introduction with no attachments
In the meeting, three sentences carry the whole position: "I can tell you what the archive holds and when access ends, because I run it. Whether any of it is licensed is your call, and SourceX publishes how it handles data on its own trust page; I won't speak for it. If you'd like a conversation, I'll introduce you and step out."
If the CEO says yes, the introduction email holds four things:
- Who you are: the company's IT partner for the archive system, with a note that you may receive a referral reward if the company goes ahead.
- What the CEO said: the records she wants to discuss, in her own words.
- The dated event, if one exists, and the document behind it.
- A link, not an attachment: SourceX's trust center, so the CEO reads SourceX's claims from SourceX.
Then step back. SourceX may deal with the company directly without affecting valid attribution, and it answers security questions itself; the trust center gives hello@sourcex.si as its security contact and says requests are answered within two business days. Before you introduce anyone, check the basics on who qualifies: 50 or more full-time employees at peak with contractors left out, records the company created itself, rights to license them and a CEO who agrees.
Walking back a promise you should not have made
If one of the tempting sentences already slipped out, correct it before the client relies on it.
- Write to the CEO the same day. Quote the trust center line that replaces what you said, and give the link.
- Tell SourceX in the introduction. One sentence on what was said, so SourceX can answer the point directly.
- Do not soften it with a new promise. "I'm sure it's fine" is the same mistake twice.
The list of privacy promises partners should never make covers the wider set beyond archives.
Before you quote anything
- The trust center changes. Re-read it before each conversation and quote the date you read it. A line accurate in October may not be in March.
- Planned is not done. Items the trust center lists as planned are not controls in place.
- Your service agreement comes first. It may limit what you may say about a client's systems, and to whom.
- Rights are not yours to judge. Whether the archive holds material that belongs to the company's clients, which SourceX's screening guidance treats as usually not a fit, is settled in SourceX's review.
- The archive's own facts can be wrong. A system that shows records from 2009 may have gaps; say "dated from," not "complete."
What happens to custody and access when a company closes altogether is covered on the main site in who controls company data after a shutdown.
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 a client's archive is about to go dark and its CEO wants to talk, send the trust center link instead of reassurance and make a four-line introduction; register as a partner before you do, confirm the company against who qualifies and read the program terms. The managed service provider overview and the guides hub carry the rest of the partner playbook.