A knowledge base is not a document pile
Load everything at once and you get a system that can cite anything, including the wrong thing. The first step is not importing; it is deciding which sources are authoritative, which are reference, and which should never be in there.
Every fact must be traceable
Which document, reviewed by whom, updated when. If those three questions have no answer, that fact should not be answering customers. Traceability is not a compliance chore — it is the only way to repair a wrong answer.
Knowledge you cannot trace is knowledge you cannot fix.
Treat proven scripts as knowledge
The few passages that close best deserve to be recorded, reused and revised exactly like a product specification. They usually live in two salespeople's chat histories and have never been written down.
Maintenance matters more than the build
Prices, stock and policies change monthly. Without an update path, a knowledge base starts stating last quarter's facts with complete confidence, and nobody notices immediately.