Backup vendor switch archive context checklist: what to confirm before the old vendor lets go

Short answer

Only if someone has restored an older record and opened its links, and a backup vendor switch is the natural moment to do that. A routine restore test shows that files come back; this checklist adds the question of whether the links between records come back too, and puts it on a timeline: before the switch is announced, before cutover, and before the old vendor contract ends. Each item names who owns it and what happens if it is skipped. The dates come from the company's own contracts and migration plan.

Visual briefFull-size diagram
A vertical countdown from top to bottom with three milestones (switch announced, cutover, old contract ends) and checklist items ticking off beside each, finishing at a marker where the old vendor's restore points are no longer reachable.
Illustrative sequence. The real dates come from the company's backup contracts and migration plan.

This checklist is part of the backup vendor switch guide for backup service providers. To walk the owner through it in one sitting, use the timed backup vendor switch meeting agenda.

Fix the three dates first

Every item below hangs off three dates. Write them at the top of the worksheet before anything else.

MilestoneWhere the date comes fromWho confirms it
Switch announced to the businessThe migration planIT lead
Cutover to the new vendorThe migration plan and the new vendor's onboarding scheduleIT lead and the new vendor
Old vendor contract endsThe old backup contract or its termination noticeProcurement or the contract owner

If the old contract end date is not known, finding it is the first item, because it decides whether there is any time pressure at all. If historical restore points will all move to the new vendor, there is no access event and no reason to hurry.

Before the switch is announced

At this stage only the IT team knows. That makes it the cheapest time to ask about history, because nobody is defending a schedule yet.

ConfirmOwnerIf skipped
Which systems hold the longest case or project histories: service desk, field service, finance, mail, file sharesIT leadThe switch is scoped by volume alone and nobody knows where the history lives
From which year each system's history runs, and rough case countsIT leadThe owner cannot weigh what is at stake
Whether historical restore points will move to the new vendor or stay with the old oneIT lead and the old vendorSome history silently ends up reachable only through the old contract
Which executive owns those recordsIT lead, then the ownerDecisions about history land with someone who cannot make them

Record only the answers. Never request exports, sample cases, admin access or screenshots. If records are scattered, the guide on how to find old company data archives helps the IT lead list them.

Before cutover

Cutover week already includes a recovery drill on the new platform. Bolting one extra check onto it, opening every link inside one older case, adds minutes, not days.

ConfirmOwnerIf skipped
Has the company verified that archived records can be restored with their links? Restore one older case and open each linkIT leadFiles come back but the case cannot be followed from ticket to email, approval and invoice
Where a restore lands: original location or a new oneIT leadLinks to the original path fail without anyone noticing
Which links failed, by type: identity, file path, record IDIT leadGaps are discovered years later, when nobody remembers why
Whether failed links are fixable from another systemIT lead and the system ownerA fixable gap is treated as permanent, or the reverse

Before the old vendor contract ends

After this date, anything that existed only in the old vendor's restore points may no longer be reachable. The checklist closes out the decision.

ConfirmOwnerIf skipped
Which systems, if any, will exist only in the old backups after the end dateIT leadHistory disappears with the contract by default
The owner's decision for that history: keep a copy, let it go, or explore a licensing reviewExecutive who owns the recordsNobody chooses, and the default wins
Whether client contracts limit reuse of the recordsCounsel or the contract ownerRecords are discussed without knowing their limits
Whether the owner wants an introduction, after your referral interest is disclosedExecutive who owns the recordsA willing owner is never asked, or an introduction goes ahead without informed consent
The decision and its date are logged with the migration recordsIT leadThe next switch repeats the same discovery

The disclosure is plain: SourceX licenses approved business data directly from companies for AI training and evaluation; you are a SourceX referral partner and may receive a reward if a qualifying license completes; SourceX pays it separately and it never reduces what the company receives. Many owners will simply keep a copy and move on, which is a good outcome for the switch.

Illustrative. A 240-person facilities services firm fixes its dates: switch announced in March, cutover in May, old contract ending in August. Before the announcement, the IT lead lists service desk history from 2016. Before cutover, a test restore shows ticket-to-email links survive but shared folder links break because files restored to a new location. Before August, the chief executive decides to keep a copy of the oldest restore points and asks for an introduction.

The check rests on established practice. NIST's contingency planning guide says backup media should be tested regularly so files can be retrieved without errors, and CISA recommends regularly testing the availability and integrity of backups. Microsoft documents that OneDrive and SharePoint content can be restored to a new URL or new site, while Exchange mailbox items restore to the current mailbox in a new folder, so whether an old link still resolves after such a recovery is something only the company's own test can show.

The company needs 50+ full-time employees at peak (contractors excluded), 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.

What stays unknown until SourceX reviews it: whether the histories fit a dataset need, the rights review, scope, preparation and any offer. Sign the Channel Partner Agreement before submitting; attribution goes to the first valid introduction within the 90-day window, credited when the company submits a verified application. The archive versus backup comparison and the email archive versus backup page explain why backups alone may not keep records readable for years, and the IT due diligence request list covers the same systems when a switch follows an acquisition.

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 chooses to explore a licensing review before the old contract ends, register as a partner, confirm the company on who qualifies, and read the program terms before you make the introduction.

  1. Step 1Share your linkSend your personal link to a company you know.
  2. Step 2Company appliesThe company applies itself at /apply.
  3. Step 3Company signs and is paidThe company signs, delivers its data and is paid by SourceX under its agreement.
  4. Step 4You get your rewardthe greater of $50,000 plus 5% and 15% of the actual supplier payout, with no cap. A reward becomes payable after SourceX has paid the referred company under its signed agreement and the payout conditions in the program terms are met, including finance approval and your tax and payment details.

Common questions

Who should hold this checklist, the provider or the client?

The client's IT lead holds it, because every item is about the client's own systems and contracts. The backup provider prepares it, walks through it at each milestone and records the answers at metadata level.

What if the old vendor's restore points will all move to the new vendor?

Then the third stage is short: confirm the move completed and that a restore from the oldest point works with its links. There is no access event, so there is no reason to hurry any introduction.

Does a failed link check stop the switch?

No. The switch goes ahead on its own plan. A failed link check simply tells the owner where context lives and which system holds the authoritative copy, which they may want to decide about before the old contract ends.

Sources

  1. nvlpubs.nist.gov/nistpubs/legacy/sp/nistspecialpublication800…
  2. cisa.gov/stopransomware/ransomware-guide
  3. learn.microsoft.com/en-us/microsoft-365/backup/backup-restore-data
  4. refer.sourcex.si/terms

Free resources

Know a company with valuable proprietary data?

Become a referral partner, get your link and introduce the company’s CEO (in an owner-run company, usually the owner). Referral partners can join from most countries. We can't work with partners in countries or regions under U.S. sanctions or on U.S. restricted-party lists. The companies you introduce should be based in the U.S., Canada and the EU, or in the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia with at least 70% of their data in English.

Refer a company →

I own a business

Explore licensing your company's data directly to SourceX for AI training and evaluation. Start a short assessment; no uploads needed.

Start an assessment