# Backup vendor switch archive checklist | SourceX

Canonical: https://refer.sourcex.si/resources/backup-vendor-switch-archive-context-checklist
Last updated: 2026-11-04

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.

This checklist is part of the [backup vendor switch guide for backup service providers](/guides/moment-backup-vendor-switch-backup-service-providers). To walk the owner through it in one sitting, use the timed [backup vendor switch meeting agenda](/resources/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.

| Milestone | Where the date comes from | Who confirms it |
| --- | --- | --- |
| Switch announced to the business | The migration plan | IT lead |
| Cutover to the new vendor | The migration plan and the new vendor's onboarding schedule | IT lead and the new vendor |
| Old vendor contract ends | The old backup contract or its termination notice | Procurement 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.

| Confirm | Owner | If skipped |
| --- | --- | --- |
| Which systems hold the longest case or project histories: service desk, field service, finance, mail, file shares | IT lead | The switch is scoped by volume alone and nobody knows where the history lives |
| From which year each system's history runs, and rough case counts | IT lead | The owner cannot weigh what is at stake |
| Whether historical restore points will move to the new vendor or stay with the old one | IT lead and the old vendor | Some history silently ends up reachable only through the old contract |
| Which executive owns those records | IT lead, then the owner | Decisions 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](/resources/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.

| Confirm | Owner | If skipped |
| --- | --- | --- |
| Has the company verified that archived records can be restored with their links? Restore one older case and open each link | IT lead | Files come back but the case cannot be followed from ticket to email, approval and invoice |
| Where a restore lands: original location or a new one | IT lead | Links to the original path fail without anyone noticing |
| Which links failed, by type: identity, file path, record ID | IT lead | Gaps are discovered years later, when nobody remembers why |
| Whether failed links are fixable from another system | IT lead and the system owner | A 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.

| Confirm | Owner | If skipped |
| --- | --- | --- |
| Which systems, if any, will exist only in the old backups after the end date | IT lead | History disappears with the contract by default |
| The owner's decision for that history: keep a copy, let it go, or explore a licensing review | Executive who owns the records | Nobody chooses, and the default wins |
| Whether client contracts limit reuse of the records | Counsel or the contract owner | Records are discussed without knowing their limits |
| Whether the owner wants an introduction, after your referral interest is disclosed | Executive who owns the records | A willing owner is never asked, or an introduction goes ahead without informed consent |
| The decision and its date are logged with the migration records | IT lead | The 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.

## Why the link check is reasonable, and who qualifies

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](/compare/data-archiving-vs-backup) and the [email archive versus backup page](/systems/email-archive-vs-backup) explain why backups alone may not keep records readable for years, and the [IT due diligence request list](/resources/it-due-diligence-checklist-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](/register), confirm the company on [who qualifies](/who-qualifies), and read the [program terms](/terms) before you make the introduction.

## Sources

- https://nvlpubs.nist.gov/nistpubs/legacy/sp/nistspecialpublication800-34r1.pdf
- https://www.cisa.gov/stopransomware/ransomware-guide
- https://learn.microsoft.com/en-us/microsoft-365/backup/backup-restore-data?view=o365-worldwide
- https://refer.sourcex.si/terms
