How do you consolidate two different knowledge bases during a company merger or acquisition?
Consolidate knowledge bases during a merger by auditing both systems, keeping the better-maintained platform as the primary, migrating active documents from the secondary, and archiving everything else. Don't try to merge everything on day one. Phase the consolidation over 60-90 days, prioritizing customer-facing and operations documentation first.
What are the common challenges?
Merging knowledge bases involves more than copying files. The real challenges are:
- Different terminology — Company A calls it "onboarding," Company B calls it "new hire ramp"
- Different tools — One uses Notion, the other Confluence
- Duplicate processes — Both companies have a refund process, but they work differently
- Outdated content — Neither company maintained their docs well before the merger
- Cultural resistance — Each team prefers their own system
What is the phased approach?
| Phase | Timeline | Focus |
|---|---|---|
| 1. Audit | Week 1-2 | Inventory both knowledge bases. Count active vs. stale documents. |
| 2. Choose primary | Week 2 | Select the better-maintained platform. Factor in cost, features, and team preference. |
| 3. Priority migration | Week 3-6 | Migrate customer-facing SOPs, operations processes, and shared workflows first. |
| 4. Re-document | Week 4-8 | For processes that differ, record the unified process using tools like Glyde rather than merging two written versions. |
| 5. Archive | Week 8-12 | Make old platforms read-only. Set a hard cutoff date for the old system. |
| 6. Unify naming | Ongoing | Standardize terminology, folder structure, and page naming conventions. |
The biggest mistake: maintaining two systems indefinitely "until we figure it out." Set a deadline. Every week with two active knowledge bases creates more confusion about which version is authoritative. Make the old system read-only within 60 days.
This answer is part of our guide to capturing and preserving team knowledge.