This timeline is part of email archive vs backup for a client data inventory, which explains why backups are a poor long-term copy of records and where restore-test evidence lives. This page treats the migration as a clock: what to note, in which order, before each record type runs out.
Five dates that set the clock
A backup vendor migration is a sequence, not a day. Ask the client, or its MSP, for five dates from its own contracts and project plan:
- Notice date: when notice was given, or will be given, on the outgoing backup contract.
- Parallel start: when the new platform begins taking backups alongside the old one.
- Cutover: when the old platform stops taking new backups.
- Last restore point: the date after which the old platform's backups are no longer kept for recovery.
- Decommission: when the old server, appliance or tenant, and its database, is switched off.
The restore validation history lives mostly between dates 1 and 5. If no one can name date 5, that is the first finding: it means the console's history has no planned end, which in practice often means it ends without notice when hardware is reclaimed.
How long each restore validation record tends to last
Retention depends on product, configuration and the client's policy. The table gives the pattern and what to ask; it is not a statement about any one platform.
| Record type | Where it usually lives | What ends it | Tends to last |
|---|---|---|---|
| Console session history (job runs, restore tests) | Old backup server database | Retention setting, then decommission | Weeks to a year, set per installation |
| Verification and test job reports | Old console, sometimes emailed | Same as sessions; emailed copies follow mail retention | Varies; emailed copies often longest |
| Failed-test tickets | Service desk or PSA | Service desk retention policy | Usually years |
| Change records for the fix | Service desk or change log | Same as tickets, if linked | Usually years |
| Signed client sign-offs | Document store | Document retention policy | Usually years |
| Restore test plans and schedules | Shared drive or wiki | Overwritten by new versions | Current version only, unless versioned |
Session history is set per installation. In Veeam Backup & Replication, for example, session history retention can keep all sessions or keep only a set number of weeks, with outdated sessions removed by a background process. Where Veeam Backup Enterprise Manager is used, its retention values override the backup server's, and session data can be kept for between 1 and 53 weeks. Other platforms behave differently, so the right question is the actual setting, read from the console by the administrator.
What disappears first
Three things tend to go before anyone notices.
- Detail older than the retention window. If sessions are kept for 13 weeks, a company with five years of quarterly restore tests holds detailed console evidence for about one of them. The rest exists only where someone copied it out.
- The link between a test and its ticket. A failed restore test raises a ticket; the ticket often names the job but not the session. When the session is gone, the join depends on dates and job names typed by hand.
- Superseded test plans. The plan that defined what a successful restore meant three years ago is overwritten by this year's version unless the document store keeps versions.
What survives is still worth describing. NIST's contingency planning guide expects backup media to be tested regularly and exercises to include recovery from backup media; a client that followed that practice for years holds a structured record of tests, exceptions and fixes, even if only the ticket and sign-off halves remain.
Illustrative timeline: one migration
A fictional 310-person regional accounting firm moves backups to a new platform. Its MSP has run quarterly restore tests since 2020.
| Date | Event | Record types affected | Who acts |
|---|---|---|---|
| Month 0 | Notice given on the old backup contract | None yet; inventory begins | IT director |
| Month 1 | Inventory complete: record types, years, owners, settings | All, described at metadata level | MSP account manager with IT director |
| Month 2 | Parallel running starts | None lost | MSP engineers |
| Month 3 | Cutover; new tests run on the new platform | Old console stops gaining history | IT director |
| Month 6 | Last restore point on the old platform expires | Old backups no longer recoverable | IT director |
| Month 7 | Old server decommissioned | Console session history and test reports end unless exported | IT director, with the client's approval |
The firm's console kept 26 weeks of sessions, so detailed results reach back only to the start of the year. Tickets and signed sign-offs cover all five years. Month 1 is the step that matters: it gives the owners six months to decide, under their own policy, whether anything should be kept.
Who must approve keeping each record
Keeping a record past its normal life is the client's decision, made by the owner of that record and within its retention policy, contracts and privacy obligations.
| Record type | Who can approve keeping it | Check first |
|---|---|---|
| Console session history and job reports | IT director or infrastructure head | Client contracts covering hosted data |
| Failed-test tickets and change records | IT director, with the service desk owner | Personal data in ticket text |
| Signed client sign-offs | The client's own records owner | Document retention schedule |
| Test plans | IT director | Usually none |
An MSP holding records for a client never decides this alone. The decision tree in who can license backup restore validation records shows who can say yes to a licensing discussion once the records are kept.
What the partner writes down
Answers, not records: the five dates, the session retention setting, which record types exist, the years each covers and who owns each one. The system map shows which keys join one restore test across the console, tickets and sign-offs, and the restore validation referral brief turns the notes into an introduction. For general advice on legacy exports, see exporting data from a legacy system and archiving versus backup; for the CIO's wider agenda in a sponsor-backed company, see the CIO of a private equity backed company.
The introduced company needs 50+ full-time employees at peak (contractors excluded), documented operating history, rights to license 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. Whether any restore history can be licensed stays unknown until SourceX reviews it.
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 a client has given notice on its backup platform and its decommission date is known, register as a partner, check the company against who qualifies and read the program terms before the old console is switched off.