Cloud migration and legacy data: what to do with the archives left on-prem

What happens to legacy data in a cloud migration?

Active data moves; old shares, databases, tape and backup sets usually stay behind. Migration plans are scoped around what users need on day one, so history that nobody opens is quietly retired with the hardware. The consultant's window to raise it is the retire-or-archive decision, before the on-prem servers are powered off.

For a client with 50+ full-time employees at peak (contractors excluded), those leftovers can be the longest record of how the business actually ran. Flag them to the owner before the decommission date, so keeping or assessing them is a choice rather than an accident.

Why does legacy data get left behind?

Common cloud migration frameworks sort each workload into outcomes such as rehost, replatform, repurchase, refactor, retain and retire. "Retire" is where data loses out: an application with no active users is switched off, and its database is not part of anyone's scope. Four patterns repeat:

• Departmental file shares that were never mapped to a SharePoint or storage design.
• Old line-of-business databases kept alive for the occasional lookup.
• Backup sets and tape that only the previous IT lead understood.
• Mail archives and exports tied to hardware that is due for disposal.

Trigger timeline: what to do before hardware is retired

The week counts above are a planning suggestion, not a program rule. Adjust them to your project calendar.

Who should you talk to?

Start with the project sponsor, usually the CFO, COO or owner, since a retire decision changes what the business can do later. Pull in the IT lead for where stores live and the records or legal contact if one exists. SourceX needs an authorized sponsor (owner, CEO, CFO or authorized representative) to take any licensing conversation forward.

The 5-store sweep

Run this sweep on every migration scoped above a handful of servers.

• File shares: which folders hold more than five years of project, finance or operations documents?
• Databases: which retired applications hold transaction or case history, and can they still be exported? The legacy export guide explains the options.
• Mail archives: are there PST or journaling archives on the old environment? See what to do with old PST files.
• Backups: do backups hold the only copy of an older system?
• SaaS history: are CRM, ERP or ticket histories being trimmed in the move, as covered in the Salesforce archiving guide and the QuickBooks to NetSuite guide?

If three or more stores show multi-year history and the company created the records, it is worth a conversation.

What to say to the sponsor

Keep the offer neutral. Archiving and moving on is a valid answer.

What you do and do not touch

You make the introduction and give basic fit facts: headcount, years in operation, number of systems and rough history depth. You never export, upload or describe confidential records. SourceX qualifies the company, the company completes a data inventory, and price and terms are agreed before buyers review. Redaction rules are settled with the company before work begins, and delivery only follows an executed agreement. Your vCIO roadmap is the right place to carry the disposition column forward.

What to preserve before the decommission date

Preservation is cheap compared with regret. For each undecided store, confirm these before anyone wipes a disk:

1. A complete, restorable copy exists on storage that is separate from the hardware being retired.
2. The copy includes the database files, configuration and any keys or credentials needed to read it, held by a named person.
3. Permissions and access are recorded, so the owner can later say who could see what.
4. The disposition sheet names the owner and the date the decision was made.

Do not compress, convert or "clean" the data while preserving it. The goal is to keep the option open, and a transformed copy may not match what the original system held.

Illustrative scenario

Illustrative and fictional: a mid-sized engineering services firm is moving from two file servers and an old project database to cloud storage. The consultant's sweep finds eleven years of project folders on one server and a retired time-and-billing database that nobody has opened in two years. He records both as undecided, asks the CFO for a decision before the cutover date, and keeps both servers powered but isolated until the CFO answers. The CFO decides to ask about a licensing assessment for the project folders and archive the billing database.

How the reward works for IT consultants

Partners earn 25% of the eligible platform fees SourceX actually collects from the referred company's licensing deals, capped at $100,000 per referred company. The reward is paid only after the buyer pays and SourceX receives its fee; an introduction, meeting or signed agreement alone does not trigger payment, and no reward is guaranteed. Disclose the relationship to the client and check your own contracts for conflicts with referral arrangements. The broader managed service provider page explains how introductions fit alongside your other services.

When to skip it

• Hardware is already gone and the archives were deleted.
• The data is mainly a client's customers' records and they have not consented.
• The stores hold mostly consumer personal data or protected health information without a basis to license.
• A court, trustee or assignee controls the assets.
• Nobody can export the data.

Next step

Add the 5-store sweep to your next migration assessment. When a qualifying client shows deep history, register as a partner, check who qualifies and use the network opportunity finder to see which other clients are mid-migration. The MSP revenue guide puts this in context.