How to replace Microsoft Teams with a truly private collaboration tool

Start with the confidential surface, not the whole company The mistake is announcing a platform migration. The better move is to identify the five to ten workstreams where a leak would actually hurt — client matters, M&A, patient data, incident response, unreleased product — and move those first. You get the security benefit in week one and the political cost stays small.

Step 1 — Map who must not be able to read what Write two columns: the people who need access, and the parties currently able to read the content (platform staff, tenant administrators, integrations, backup operators). The gap between those columns is your actual exposure.

Step 2 — Decide the recovery model before the first message Client-side encryption means nobody can reset your way back in. Decide now: - Every member generates and stores a recovery kit offline. - Shared workstreams live in Team Drive folders with keys sealed to several members, so no single departure orphans data. - Admins hold organisational continuity, not content keys.

Write this down. It is the first question your risk committee will ask.

Step 3 — Set up the workspace Create channels that mirror the workstreams you selected, not the whole Teams org chart. Fewer, better-scoped channels make key rotation and access review meaningful.

Step 4 — Bring the history you actually need Most teams need far less history than they think. Export the threads and files that matter, import them through the universal importer, and archive the rest in place. History that nobody reads is a liability, not an asset.

Step 5 — Move files with the conversations Conversations without files push people back to the old tool. Drag folders into My Drive or a Team Drive, or point Live Clone at a local folder so it mirrors continuously — encrypted before anything leaves the machine.

Step 6 — Rewire external sharing Replace long-lived share links with passphrase-gated links that expire within 24 hours at most. Short-lived links are the single cheapest reduction in accidental exposure, and they change behaviour: people send what is needed, when it is needed.

Step 7 — Rehearse offboarding Remove a test member. Confirm that folder and room keys rotate, that the audit log records the event, and that the removed account can no longer decrypt anything new. Offboarding that only flips a flag is not offboarding.

Step 8 — Brief legal and compliance honestly Tell them what they gain (disclosure becomes technically impossible for content) and what they lose (no server-side content export, no provider-side DLP). Where a tenant-wide retention obligation applies, keep that workload in the governed platform. Split by obligation, not by preference.

Step 9 — Run a two-week pilot with a real team Not a sandbox. Real deadlines, real files, real calls. Collect friction, fix it, then expand.

Step 10 — Review access quarterly Membership *is* the access control when keys are per-member. A quarterly review of who holds which room and folder keys is the whole security programme in one meeting.