Replacing Shared Drives Without Disrupting Work

Shared drives are everywhere because they are easy. Every IT department in Kenya has spun one up at some point, and every organisation has lived to regret it. Folders within folders within folders. No permissions. No search worth the name. No audit. No way to find the latest version. Backups that nobody has tested in years.

But the shared drive is also where the work happens. You cannot rip it out on a Friday and expect a productive Monday. Here's how customers do this without losing the room.

The four-phase replacement

Phase 1 — Shadow mode (weeks 1-2)

Install the Papyrus Desktop Upload Agent on the file server, pointed at the existing shared drive. It will passively index everything (no movement, no permission changes) and surface what's actually there:

• Total files, by type
• Last-touched distribution (active vs dormant)
• Duplicate detection (90% of shared drives are >40% duplicates)
• Permission analysis (who can access what — usually: everyone can access everything)

This phase produces the migration plan.

Phase 2 — New-file capture (weeks 3-4)

Configure the Desktop Agent to auto-upload anything new placed in the watched folder. Existing files stay where they are. New files automatically appear in Papyrus.

This is the most important phase: it stops the bleeding without forcing user behaviour change. Users keep saving to the shared drive. Papyrus keeps ingesting.

Phase 3 — Hot file migration (weeks 5-8)

Move files touched in the last 12 months to Papyrus folders, preserving the folder structure (initially). Tag them by their original drive location so users can find them. Set up redirect notices on the shared drive subfolders.

Phase 4 — Behaviour shift (weeks 9-16)

Now you talk to humans. Show department heads how Papyrus search outperforms Ctrl+F. Show them version history. Show them the AI-suggested tags that replace folder hierarchies. Most teams convert in 2-3 weeks.

After 16 weeks, the shared drive becomes a cold archive. Some organisations turn it off entirely; others keep it read-only for legacy access.

## What dies first

The first behaviours to disappear:

• "What's the path to that folder again?" — replaced by search
• “Send me the latest version” — replaced by shared links
• "Is this on the X: drive or the Y: drive?" — replaced by the single Papyrus tenant

What survives

What survives:

• Department-level autonomy (each department still owns its own folders)
• The mental model of “this is HR's stuff” (now: HR department in Papyrus)
• Personal favourites and recent files (now: Papyrus pinned + recent lists)

Related reading

• Migrating From File Servers and Shared Drives
• Using the Desktop Upload Agent
• Organising Documents with Folders and Tags