The Data Migration Trap: Why You Can't Just 'Move and Delete'

I was working with a client recently who was moving from their on-prem file server to SharePoint. They saw it as straightforward: copy the files, set up the new structure, turn off the old server. No problem.

Then we started asking questions about their old data, stale data, and backups. That’s when the complexity surfaced—complexity they hadn’t anticipated.

”Can’t We Just Delete the Old Stuff?”

They asked the logical question: why can’t we just delete what we don’t need anymore?

We walked them through why we, as an organization, want to make sure clients understand what “delete” actually means before proceeding. Deletion is permanent, and uninformed decisions about what to keep and what to discard can haunt organizations later—whether it’s a compliance audit, a legal discovery request, or simply the realization that critical institutional knowledge walked out the door with a departing employee.

Retention periods matter. Industry requirements matter. Legal hold considerations matter. Most SMBs haven’t fully worked through this. They assume “cloud = backed up” without realizing their old backup strategy doesn’t automatically transfer to the new environment, and that backups serve a different purpose than long-term retention.

The Backup Disconnect

The backups for their on-prem server weren’t something that could magically work with SharePoint. Different architecture, different retention models, different recovery procedures.

They wanted to know: “How long do we keep the cloud backup of the files?”

A great question—but they didn’t yet have the governance framework to answer it. No retention policy. No data classification. Just… however long feels right? That’s a risky foundation.

The Interlinked Reality

This is what many SMBs miss when planning a migration: data decisions aren’t isolated. Moving tools means reconsidering the whole picture:

1. Retention requirements — What does your industry actually mandate? (See our Data Retention Policy guide)
2. Backup architecture — Your old backups won’t restore to your new environment, and backups serve disaster recovery—not long-term compliance (Backup Retention Concepts)
3. Governance — Who decides what stays, what goes, and for how long?
4. Cost tradeoffs — Long retention costs money, but short retention creates compliance and operational risk

You can’t answer any of these in isolation. They’re all connected, and getting one wrong affects the others.

Why We Ask Hard Questions

This is why we dig deep into projects that seem “simple” on the surface. A file migration isn’t just moving bits from A to B. It’s an opportunity to get your data governance right—before you’re staring at a compliance audit wondering why you kept everything forever (or deleted something you shouldn’t have).

The 30,000-foot view: technology serves the business, but only when the pieces fit together and you’ve made informed decisions. Retention, backups, governance, cost—none of these work in silos, and none should be decided under pressure without understanding the implications.

We’d rather ask the hard questions upfront than see clients face problems later. That’s the partnership. :)