✦ Deep dive / Source check · 2026-10-20
Can you move an AI companion to another app?
A realistic migration checklist: what you can copy, what may be lost, and how to protect privacy.
Independent research ✧ Source-linked feature claims ✧ No fabricated hands-on tests
Moving an AI companion usually means rebuilding a fictional persona—not transferring the original model’s learned state. A saved chat transcript, a character definition and an internal memory index are different assets. The current first-party materials do not establish a universal cross-service memory export/import feature.
What may be portable?
| Asset | Often possible in principle? | Limitation |
|---|---|---|
| Character name and brief | Yes, as text you write yourself | Other platforms interpret instructions differently |
| Backstory and pinned facts | Can often be manually copied | Fields and length limits differ |
| Chat transcript | Depends on export options and terms | A readable archive is not an importable memory model |
| Generated portrait | Only with appropriate rights and platform permissions | Do not assume ownership or reuse rights |
| Learned long-term state | No cross-platform guarantee | May rely on proprietary embeddings, summaries or hidden data |
A practical migration worksheet
- Record a fictional character name, speech style and three unchanging facts.
- Write a 100–200-word neutral backstory without platform-specific controls.
- List at most five important plot events and note their current versions.
- Review the old service’s export, privacy and deletion information.
- Create a new fictional character with the portable brief and verify each fact manually.
- Keep subscription cancellation separate from account deletion.
Provider-specific cautions
- Nomi: the team has described Identity Core and long-term memories as difficult to copy wholesale, even between Nomis.
- Kindroid: journal and memory controls can help you build a fresh structured personality, but are not a general import of another provider’s private memory system.
- Character.AI: Story Memory pins are a feature of its own chat environment.
- Nectar: its documented reset and archive controls affect the current conversation’s memories; do not assume cross-chat portability.
What to avoid
Do not upload a sensitive private chat log to a second vendor merely to avoid rewriting a fictional biography. Prefer your own summary and redact personal information. See the privacy guide and the account deletion checklist.
Example: move a character without moving a private chat log
Suppose your character is a fictional botanist who speaks in short sentences and remembers a made-up garden project. Exporting a transcript may carry hundreds of personal details that the new provider does not need. Instead, write a clean two-paragraph persona summary and five invented plot facts. Then manually set the new app’s personality fields and pin only the durable information. This is easier to audit and less likely to expose unrelated private conversations.
A post-migration quality check
Ask five neutral questions about the fictional character brief. If it invents details, amend the brief once and retry. Do not expect writing style or humor to transfer perfectly: those are partly produced by the underlying model rather than just saved notes. Cancel the old subscription only after checking its deletion and export terms, and do not assume subscription cancellation closes the account.
Want to verify something? See how we research or submit a correction.