# Migrating an Existing Knowledge Base



<a id="section-goal"></a>

If you already have a knowledge base — an LLM Wiki, a set of Skills, a documentation folder — you do not have to start from nothing. Create a Context knowledge workspace, describe the existing base to the Agent, and let it plan the migration up to the work-start report, where you review the approach and decide the batches.


<a id="section-prompt"></a>

## The migration prompt

Once the workspace exists, start with:

```text
Research what Context can do, then migrate the current knowledge base:

- Location, content and document scope of the current knowledge base:
- How it is produced today (scripts, prompts, and so on):
- Desired published structure and form: keep it as is, or new requirements
- Historical Q&A or an evaluation question set, to show how the knowledge base is used

Turn this into a research report, continue up to the work-start report and pause.
I will review the approach and plan the batches.
```

The last item matters most: real questions tell the Agent what the knowledge base is *for*, and they become your evaluation set later.


<a id="section-sources"></a>

## Bringing the existing material in

Existing material can be connected in different ways, depending on whether it should become a source of new articles or stay where it is:

- **Document directories** — register a folder of existing documents as a source so its contents are captured and cited. See [Document Directories](</context/llms/pages/8c2b49b432214167855ee9d7e2888616.txt>).
- **Same-repository docs and Skills** — documents and authored Skills already kept in the same repository are registered as an entrance; the originals stay where they are and remain the only place to edit them. See [Same-Repository Docs](</context/llms/pages/3f921b4529b91c86c7acd8db0f76f291.txt>).
- **External entrances** — content elsewhere that pages should link to, declared in `imports.yaml` without downloading or capturing it. See [External Entrances](</context/llms/pages/3c35b84bd6846bd03f010004a29bf565.txt>).


<a id="section-validate"></a>

## Switch over after you have measured

Keep the old knowledge base running until the new one is proven. Run the same question set against both and compare quality, time and tool calls, as described in [Evaluating Your Knowledge Base](</context/llms/pages/bd9cc4f9beb5c6aba346e47ba2c12049.txt>).

---

## Sources

- note:20261012/usage-practices.md · usage-practices.md L47–L60
- [context/packages/context/docs/guides/imports.md L1–L7 · 3b0ce0a](<https://github.com/context4ai/context/blob/3b0ce0a0a1761f5fceb3bb48fb9dc29b54c0786b/packages/context/docs/guides/imports.md#L1-L7>)
- [context/packages/context/docs/guides/repo-content.md L1–L5 · 3b0ce0a](<https://github.com/context4ai/context/blob/3b0ce0a0a1761f5fceb3bb48fb9dc29b54c0786b/packages/context/docs/guides/repo-content.md#L1-L5>)
- note:20261012/usage-practices.md · usage-practices.md L73–L75