> "We migrated from one wiki to another and half the institutional memory did not make the trip — and we are not sure which half." ^pain A collective survivability pain. When the org's holding tool is replaced, the knowledge inside does not transfer cleanly. Some artefacts get lost, others get reformatted, and proprietary block models or schemas die with the vendor. The cost compounds with scale: more artefacts mean more reformatting losses, more departments mean more readers who notice their corner of the old system is gone. ## Discovery questions - "How many times has your team migrated knowledge between tools? What was the experience like?" - "If you were forced off your current wiki tomorrow, what would you lose that you cannot reconstruct?" - "When you adopt a new tool, who is on the hook for moving the history — and how completely do they manage it?" ^discovery-questions ## Examples - Software company described losing Jira issue history links and custom fields during a Jira Server-to-Cloud migration, forcing teams to rebuild reports.[^1] [^1]: https://community.atlassian.com/t5/Jira-Software-questions/issues-after-migration-server-to-cloud/qaq-p/1693867