chatgpt-import
The chatgpt-import skill automates migrating conversation history from ChatGPT into Vellum by processing exported data archives. Use this when users want to preserve their ChatGPT conversations and maintain continuity switching to Vellum, accepting only ZIP files from ChatGPT's export feature and deduplicating conversations while preserving original timestamps for searchable memory.
git clone --depth 1 https://github.com/vellum-ai/vellum-assistant /tmp/chatgpt-import && cp -r /tmp/chatgpt-import/skills/chatgpt-import ~/.claude/skills/chatgpt-importSKILL.md
Import ChatGPT conversation history into Vellum so users can keep their conversation context and memory when switching from ChatGPT.
## How to guide the user
When a user wants to import their ChatGPT conversations:
1. **Tell the user how to export.** They need to go to ChatGPT Settings > Data controls > Export data. ChatGPT will email them a ZIP file.
2. **Ask the user to upload the ZIP file.** Use whatever file upload tools or skills are available to receive the ZIP.
3. **Run the import.** Once you have the ZIP file path, run:
```bash
bun run scripts/parse-export.ts --file "$ZIP_PATH" | assistant conversations import --json
```
The `parse-export.ts` script parses the ChatGPT ZIP and converts it to the standard import format. The `assistant conversations import` command reads the JSON from stdin and creates the conversations.
The command returns JSON:
```json
{ "ok": true, "imported": 12, "skipped": 0, "messages": 347 }
```
Report the results — how many conversations and messages were imported, and any skipped duplicates.
## Notes
- Only ZIP files are accepted (the full export archive from ChatGPT).
- Conversations are deduplicated — re-importing the same file will skip already-imported conversations.
- Only user and assistant messages are imported (system prompts and tool calls are filtered out).
- Original timestamps from ChatGPT are preserved.
- Imported conversations are automatically indexed for memory search.>
>
>
>
Check Vellum Assistant architecture and package boundaries. Use when editing imports, moving code, adding endpoints, touching assistant/gateway/client/skill boundaries, or reviewing architecture-sensitive changes.
Review Vellum Assistant code changes for correctness, repo-specific quality rules, security risks, and missing validation. Use when reviewing diffs, preparing a PR, finishing implementation work, or when the user asks for a code review, quality pass, or pre-merge check in this repository.
Guide Vellum Assistant feature flag changes and rollout hygiene. Use when adding, editing, reviewing, or documenting assistant feature flags, rollout-gated behavior, or platform flag follow-up work.
Validate Vellum Assistant database and workspace migrations. Use when adding, editing, reviewing, or testing migrations, release-note migrations, persisted schemas, workspace file formats, or data backfills.