Switch to Gab AI
Bring your chat history to Gab AI.
Keep useful conversations close as you move to Gab AI. Import supported ChatGPT, Claude, Grok or Gab AI history, review what arrived and continue the work in one workspace.
Sign in to open your import settings.
Bring your conversations.
Import supported ChatGPT, Claude, Grok or Gab AI history.
Choose your providerKeep useful history.
Keep supported titles, dates and readable text together. Check what arrived before you continue.
See what transfers
Continue with more models.
Open an imported chat, choose a model and ask a useful follow-up.
See what comes nextHow to import ChatGPT, Claude or Grok chats.
Keep the original conversation export, choose its provider in Settings → Import and select the supported JSON or ZIP files.
From ChatGPT
Request your export
In ChatGPT, open Settings → Data controls → Export data and confirm the export request.
Keep the complete download
Download the ZIP when it is ready. Keep the original archive and check that it contains the conversations you need.
Choose ChatGPT in Gab
Open Settings → Import. Upload the ZIP, or select all relevant conversations.json / conversations-*.json files together with available project or folder metadata. Review imported, skipped and error counts.
Self-service export depends on the account or workspace. Business, Enterprise and Healthcare workspaces use organization-managed data access; eligible Edu exports depend on workspace settings.
From Claude
Request your export
In Claude on the web or desktop, open Settings → Privacy → Export data.
Download your history
Open the emailed download link while signed in to the account that requested it. Keep the complete archive.
Choose Claude in Gab
Upload the export ZIP, or select conversations.json together with any projects.json file. Review the results and check a few imported conversations.
Claude’s export control is on web and desktop, rather than iPhone or Android. Team and Enterprise member exports depend on organization permissions.
From Grok
Request your account data
In Grok on the web or mobile, open Settings → Data Controls and request a download of your data.
Keep your export
Save the full archive. Gab’s Grok parser recognizes conversation records in prod-grok-backend.json, including when that file is inside the ZIP.
Choose Grok in Gab
Upload the full export ZIP or its supported conversation JSON. Review imported, skipped and error counts, then open a small sample of chats.
These instructions describe Grok.com and Grok’s own apps. Grok on X has separate account controls; an arbitrary X archive is not a supported import promise.
From Gab AI
Export from the source account
In the Gab AI account you are moving from, open Settings → Download your data and request an export.
Keep the original archive
Save the ZIP or JSON export. The full export can include collection information when it is available.
Choose Gab AI in Import
Sign in to the destination account. Upload the full export ZIP or JSON, or select conversations.json together with collections.json. Review the results and check a few chats.
Importing supported chat history is separate from restoring memories, credentials, settings or original file contents.
Review the full import checklist
Obtain the provider’s conversation export
Use the source account’s current export controls. Keep its original archive and select the conversation files, not only a profile or summary index.
Open Gab’s Import settings
Sign in and open Settings → Import. Choose the matching provider, select its supported JSON or ZIP conversation files, and read the parsed/imported/skipped results.
Check a small sample, then continue
Verify titles, dates and text in actual imported chats. Check missing files, memories and settings separately; future AI requests use their own model, plan and credit conditions.
What transfers, and what needs separate setup.
Supported conversation history
The current file-import flow recognizes Gab AI, ChatGPT, Claude and Grok export structures. Confirm that the archive contains readable messages.
Memory is a separate step
Review useful preferences and add them deliberately using Memory. A chat import does not automatically transfer another assistant’s saved memories or all personalization.
Check omissions and errors
Branches, tool records, images, attachments and settings can differ or be omitted. Review parsed counts, imported/skipped results and a few actual conversations.
What to review after a transfer
| Content | Current scope |
|---|---|
| Titles and readable text | Supported provider records can preserve these. Review the actual imported chats. |
| Dates and current branch | Supported timestamps and the selected ChatGPT branch are parsed; unsupported or missing source data cannot be reconstructed. |
| Collections and folders | Recognized source/project metadata can organize supported chats. Missing or unsupported metadata requires separate setup. |
| Images, files and tool results | Do not assume original attachments, binary files or tool state transfer with text history. |
| Saved memories and settings | Review and configure separately. A chat import is not automatic memory or account-setting migration. |
| Duplicates and errors | Stable source IDs and fingerprints help avoid duplicate chats. Inspect imported/skipped/error counts and resolve incomplete source records. |
Missing messages? Return to the full export.
A file can list a conversation without containing its messages. Use the full provider export to recover missing history, then check the importer’s saved, skipped and error counts.
The import guide walks through a import example: supplying the complete messages recovered a missing chat, while stable source IDs let the importer skip records already saved.
Follow the import and recovery stepsReview what the next request shares.
Imported text can contain identifying information. Check the content and enabled context before sending a new request to another model.
Provider-account routing
Gab sends relevant content through its provider accounts. Identifying information inside imported messages is not automatically anonymous.
Review reusable context
History, saved memories and instructions are separate. Choose which context to use, and review the selected model’s handling before sending sensitive material.
Separate retention and export
Export, deletion and cancellation are different actions. Check available account controls and the privacy policy rather than assuming a transfer erases another service’s copy.
Pick up a conversation and move it forward.
Open an imported chat, choose a model and ask a useful follow-up. Or bring fresh notes into a new conversation and shape the next draft.
Enlarge preview
Continue a useful conversation
Conversation preview · Continue with the history you imported.
Import questions
Can I import ChatGPT or Claude chats?
Use the matching provider option in Import settings with a supported export containing readable messages. Grok and Gab AI exports also have current parsers. Check actual results; a file name alone does not prove every conversation is complete.
Can I import Gemini or any other AI service?
Do not assume universal support. The current file-import flow recognizes Gab AI, ChatGPT, Claude and Grok structures. Use only a supported path and review its current guide.
Does importing chat history transfer memories?
No automatic transfer of another assistant’s saved memory is established by a chat import. Review useful context and add it separately in Memory, then check the next conversation.
What if only some conversations import?
Review parsing errors and the source archive. Summary-only records can lack the message tree; select complete conversation files or the original full archive. After resolving the source, review the next imported/skipped/error counts rather than repeatedly sending the same incomplete file.
Does importing create new AI answers or charge a model?
The import path stores supported history rather than generating a new model answer. Subsequent Chat, Work or media requests follow their access and credit rules.
Can I take my Gab data with me later?
Use the account export controls and inspect supported records, counts and truncation. File metadata is different from complete binary files, and exported records are not a universal restore of every setting.
Bring your conversations. Keep building.
Import supported history, check the messages and continue with the ideas worth keeping.