# Single vs multiple knowledge bases A question that people often ask is whether they should keep everything in one place, or split things up, for instance separating work notes and personal notes. Here's my take on this topic. My recommendation is to start with a single knowledge base, and to only split when you have a compelling reason to do so. The main advantage of keeping it all in one place is that you'll have a single place to search if you need to find something. You'll also be able to connect all your ideas together. In my case, there's a lot of overlap between my work and personal notes, and it wouldn't make sense for me to keep those separate. Having multiple knowledge bases imply context switching, and makes backup and recovery more complicated. But it sometimes make sense, for instance for sensitive information (e.g., data confidentiality rules at work) or for cases where other people need to collaborate with you on the knowledge base.