Why content migration fails when you treat it like a technology project

Content migration projects consistently fail for one critical reason. Organizations approach them as purely technical exercises when they’re fundamentally about changing human behavior.

Shannon Ford from Microsoft (was at Advania UK during time of recording) has seen this pattern repeatedly. “I think for me, obviously, when you’re having an initial conversation, it’s usually coming from one person or one part of the business whether that’s the IT team or someone else,” Shannon said. “And I think they have a vision of, okay, we can just lift everything over or we can just take this.

This oversimplification creates immediate problems. IT teams typically view migration as a straightforward data transfer. Copy files from System A to System B. Check the box. Move on.

The reality proves far more complex. Success requires conversations with content owners across the organization. These discussions reveal workflows, dependencies, and usage patterns that IT teams never considered.

Zoe Bennett, also a Solutions Consultant at Advania UK, emphasized this disconnect. “It’s easy for, I guess, people at a high level with IT to sort of oversimplify and think we can just lift all the content over here and to, you know, SharePoint Online, but there’s a lot of complexities once you talk to actual users of that content.”

The technical migration represents just the beginning. The real challenge starts when users must adopt new behaviors. Shannon described a recent project where the technical implementation succeeded perfectly, but users continued saving files locally because the new system felt too foreign.

Organizations often discover their content problems during migration planning. Twenty-year-old documents nobody remembers. Christmas party photos from 2009. Multiple versions of the same file with cryptic naming conventions. These issues compound when everything transfers to the new system without cleanup.

The solution requires treating migration as a change management initiative first and a technical project second. Start with internal communications before engaging vendors. Help teams understand why change is necessary and what benefits they’ll receive.

Get content owners involved early. Run workshops with different departments. Ask people to review and clean their existing content before migration begins. This groundwork prevents panic conversations later when users suddenly realize their data is moving.

Consider metadata strategy from day one. Modern systems like SharePoint work differently than file shares. Deep folder structures become unnecessary when robust search and metadata enable better content discovery. But users need training and support to adopt these new approaches.

The permission model requires similar attention. Legacy systems often create complex permission structures that don’t translate well to modern platforms. With AI tools like Copilot analyzing content, proper security trimming becomes even more critical.

Organizations that succeed treat migration as the first step in a broader digital strategy. They understand that moving to the cloud enables future capabilities but only if the foundation is properly established.

To hear the full conversation, listen to the complete episode of Fresh Perspectives from Fresh Intranet.

Catch the full episode of Fresh Perspectives to hear all the details.

Listen to the full episode here