How do you consolidate company knowledge scattered across Google Docs and Slack?
Consolidate scattered knowledge by first auditing where information lives, then migrating the most-used documents into a single platform like Notion or Confluence. Don't try to move everything — focus on active processes and frequently referenced docs. Archive the rest. Set a deadline to stop using the old locations.
Why does knowledge end up scattered?
Knowledge fragments across tools because each one is convenient for a different moment:
- Google Docs — Easy to create and share, but no structure or discoverability
- Slack messages — Fast answers to quick questions, but impossible to search months later
- Email threads — Critical decisions buried in reply chains
- Personal bookmarks — The employee who "knows where everything is" has their own system
- Meeting recordings — Valuable context locked inside hour-long Zoom calls
Nobody planned this. It happened naturally because each tool solved an immediate need without considering long-term retrieval.
How do you run a consolidation project?
Follow a phased approach to avoid overwhelming the team:
| Phase | Action | Timeline |
|---|---|---|
| 1. Audit | Survey each team — where do you go to find process information? | Week 1 |
| 2. Triage | Categorize documents: Active, Archive, Duplicate, Missing | Week 2 |
| 3. Migrate | Move active documents to the chosen platform | Weeks 3-4 |
| 4. Fill gaps | Record undocumented processes using tools like Glyde | Weeks 4-6 |
| 5. Redirect | Set old Google Docs to read-only with a link to the new location | Week 6 |
| 6. Enforce | New documents must be created in the central platform | Ongoing |
The critical mistake to avoid: migrating everything. Most scattered knowledge is outdated, duplicated, or no longer relevant. Moving garbage into a new platform just creates organized garbage. Be ruthless about archiving.
For Slack knowledge, the fix is cultural. When someone answers a process question in Slack, the answer should be added to the knowledge base and the Slack thread should link to it. Over time, this redirects questions from Slack to the wiki.
This answer is part of our guide to capturing and preserving team knowledge.