Threads Import

By default, the importer targets the Enterprise Intelligence project selected when you created the app with the CopilotKit CLI. If that is the project that should receive the imported threads, continue to the dry run.

To target a different cloud-hosted project, select it before the dry run:

```bash title="Terminal"
npx copilotkit@latest project select
```

The command updates the project selected for the current directory and writes its project-scoped runtime key to the app's generated `.env`.

A dry run reads the source, discovers source agent keys, counts conversations, reports skips, and estimates upload size without opening an import batch. It does not need an Enterprise Intelligence URL or API key.

<Tabs groupId="thread_import_source" items={['ADK', 'LangGraph']}>
  <Tab value="ADK">
    ```bash
    npx copilotkit@latest import --source adk --dry-run
    ```
  </Tab>
  <Tab value="LangGraph">
    ```bash
    npx copilotkit@latest import --source langgraph --dry-run
    ```
  </Tab>
</Tabs>

The importer maps each source agent key to the `agentId` your live CopilotKit runtime uses. Keeping those labels aligned prevents imported history and future native traffic from splitting across different agent IDs.

For scripted imports, put the mapping in a JSON file:

```json title="agent-map.json"
{
  "support-agent": "support-agent",
  "sales-agent": "sales-agent"
}
```

A real import needs the destination app-api URL and project-scoped runtime key. A CLI-created starter writes them to `.env`, but the importer reads the current process environment and does not load `.env` or `.copilotkit/project.json` automatically.

Copy the generated values into your shell before importing:

```bash title="Terminal"
export INTELLIGENCE_API_URL="https://..."
export INTELLIGENCE_API_KEY="cpk_..."
```

`COPILOTKIT_API_KEY` is also accepted for the key. You can pass the same values directly with `--api-url` and `--api-key` instead.

Run the source-specific import after the dry run looks right:

- [Synchronize ADK threads](/google-adk/threads-import)
- [Synchronize LangGraph threads](/langgraph-python/threads-import)

Re-running the same import is safe: already-imported conversations are skipped. Use `--replace` when you intentionally want to refresh previously imported threads.

Open the Threads Drawer, select an imported conversation, and confirm that its history appears in the chat.

Your CLI-created app sends future CopilotKit conversations to Enterprise Intelligence. Reopen a conversation with the same CopilotKit `threadId` so its Rich Thread history stays continuous. If the agent remains wired to its durable native persistence mechanism, the future run continues there as well.

- **Threads Drawer:** already included in CLI-created starters. Use the [Threads Drawer guide](/prebuilt-components/copilot-threads-drawer) to customize its ready-made thread UI.
- **Headless Threads:** use the [Headless Threads guide](/headless-threads) only when you need a custom UI. Select a thread with `useThreads`, store its `thread.id`, and pass that value to your chat component as `threadId`.

Create one new conversation through CopilotKit, then confirm that it appears in Enterprise Intelligence and in the native persistence store that remains connected to your agent.

For the underlying persistence and replay model, see [Threads & Persistence Architecture](/premium/threads-explained).