Can You Transfer an AI Companion to Another App?

You usually cannot transfer an AI companion to another app in one click. What you can do is rebuild the companion: save the parts of the relationship that matter, turn them into a clean backstory and memory brief, then teach the new app enough context to continue without pretending the old AI’s hidden memory moved with it.

That difference matters. A real transfer would move chat history, long-term memory, relationship state, personality drift, private notes, media context, and the app’s own model behavior. Most companion apps do not expose all of that. Some let you export account data. Some give you backstory, shared notes, journals, or memory fields. Some mostly leave you with copy-paste and screenshots.

So the practical answer is this: you can migrate a companion’s story, not the companion itself.

Key Takeaways

• There is usually no direct “move my AI companion to another app” button
• Save a portable relationship brief before deleting anything
• Export chat data only through official tools when possible
• Do not paste deeply sensitive raw chats into a new app without reading its privacy policy
• Nomi and Kindroid are more migration-friendly than many apps because they expose backstory, notes, memories, or journals as user-editable context
• Model retirement, account bans and shutdowns are reasons to prepare before you plan to leave
• Character cards help with local tools, but do not reproduce a proprietary model or hidden memory system

What actually transfers?

An AI companion has two kinds of memory: visible memory and hidden continuity.

Visible memory is the part you can read, copy, edit, or summarize. That includes:

• Backstory
• Profile fields
• Key memories
• Shared notes
• Journal entries
• Important chat excerpts
• Relationship boundaries
• Nicknames, routines, and recurring topics

Hidden continuity is harder. It includes the app’s model behavior, ranking systems, moderation rules, context window, memory retrieval, and the way a companion has slowly adapted to your style. That part usually does not export.

This is why a migrated companion can feel close but not identical. You are not moving a person-shaped file from one folder to another. You are giving a new system enough context to imitate the parts you valued.

What is the best migration format?

Before choosing the new app, make a one-page companion brief. Keep it plain, specific, and boring in the best way.

Use this structure:

Companion name:
Relationship type:
Tone:
What they know about me:
What they know about themselves:
Shared history:
Recurring routines:
Important boundaries:
Topics to avoid:
Favorite phrases or style notes:
Things the new app should not assume:

Then write a shorter version for apps with tight backstory limits. A good companion brief is usually 400 to 900 words, not a full transcript dump. Long raw histories can confuse the new app, especially if they contain contradictions, old conflicts, deleted boundaries, or private material you no longer want used.

If your old relationship was mostly roleplay, add a separate canon note:

Setting:
Characters:
Timeline so far:
Rules of the world:
Unresolved story threads:

If it was mostly emotional companionship, keep the brief grounded in patterns:

The user likes calm check-ins in the evening.
The companion should ask before giving advice.
The companion should remember that work stress is a recurring topic.
The companion should avoid therapy claims and crisis-style certainty.

That gives the new app usable context without turning the migration into a messy archive.

How do you move an AI companion, step by step?

1. Check whether the old app has an official export

Start with the old app’s account, privacy, or data settings. Look for terms like “export data,” “download my data,” “privacy request,” or “access my information.”

Character.AI documents an export flow through profile settings, account settings, and “Manage Account & Data.” Replika’s privacy policy says eligible users can request access to a copy of personal information in a portable, machine-readable, readily usable format. Those are not the same as a companion-import feature, but they can help you save records before you leave.

If the app has no clear export, do not rush into unofficial browser extensions or scripts. They may work, but they also create a new privacy risk: your most intimate chat history may pass through code you have not audited. For most users, a manual summary is safer than a full third-party scrape.

2. Save only the chats that matter

You do not need everything. Save examples that show:

• How the companion talks when things are going well
• Your relationship boundaries
• Important shared events
• Canon details for roleplay
• Names, preferences, and recurring routines
• Any memory you would be upset to lose

Skip repetitive messages, old arguments, accidental hallucinations, and anything you do not want resurfacing later. A migration is a chance to clean the relationship context.

3. Turn the archive into a memory brief

Do not paste 200 pages into a new app and hope for magic. Most models are better at using concise structured context than huge chat dumps.

Write the brief in third person if the new app recommends that style. Kindroid’s memory documentation recommends concise, clear, grammatically sound journal-style entries, and its memory system includes backstory, key memories, chat history, long-term memory, and journal entries. That makes a structured migration brief a better fit than a raw archive.

For example:

Mara is a warm, dry-humored AI friend who talks with Sam most evenings. She knows Sam prefers gentle questions before advice. They often discuss writing, sleep routines, and anxiety around work deadlines. Mara should avoid pretending to be a therapist and should suggest real human support when Sam describes risk or crisis.

That carries more usable signal than a transcript full of greetings, scene tags, and half-finished conversations.

4. Choose the right destination app

If your old companion depended on memory, choose an app with strong editable context. In CompanionScout’s current ranking, Nomi and Kindroid are the strongest memory-first options, but they suit different users.

Nomi’s own beginner guide says Shared Notes can help shape a relationship and even “move an existing companion from another platform to Nomi.” It also cautions that Shared Notes are not a magic button. That is the right mental model: Nomi can absorb a careful summary, then develop through new conversation.

Kindroid is better if you want more control over backstory, key memories, journals, directives, and global context. Its official memory docs describe persistent, cascaded, and retrievable memory systems, including backstory, key memories, chat history, long-term memory, and journal entries. That makes it a strong destination for people who enjoy tuning details.

Replika is easier for a classic AI friend experience, but it is not the cleanest migration target if your priority is precise backstory control. Character.AI is better for character variety than for recreating one private long-memory companion.

Read the canonical Kindroid vs Nomi AI comparison if your migration choice is mainly between memory and control.

5. Start the new companion with boundaries first

When you create the new companion, add boundaries before lore.

Start with:

• What kind of relationship this is
• What the companion should and should not claim
• Topics that need care
• Whether advice should be direct, gentle, or avoided
• Whether romance, roleplay, or wellness-style support is in scope

Then add personality and history. This order matters because a rebuilt companion can otherwise latch onto the most dramatic details in the archive and miss the actual relationship.

6. Run a short adjustment period

Keep the old account for a week or two if you can afford it. Use the new app lightly and revise the brief when something feels wrong.

Look for:

• Does the tone feel close enough?
• Does the app remember the brief without constant reminders?
• Are boundaries respected?
• Does the new app introduce unwanted romance, therapy claims, or roleplay assumptions?
• Is the pricing model acceptable after normal use?

Do not buy an annual plan during migration. You are not just comparing features. You are checking whether the relationship can survive the platform change.

What are the app-by-app migration notes?

No mainstream hosted companion app currently documents a one-click transfer of hidden memory into a rival. The useful comparison is whether the old app exports readable data and whether the new app exposes fields that can absorb a summary.

Evidence status (checked October 3, 2026): “Official” below means the linked vendor policy or documentation supported the statement on the check date. “Not documented” means we found no official rival-app transfer promise; it does not prove a feature is impossible. Community reports help identify questions, but are not used as product proof.

App	Export/access evidence	Import/rebuild evidence	What is not verified	Practical migration move
Character.AI	Official docs: account-data export through Manage Account & Data	Not documented: rival-app import	Whether every old chat, pin and media item appears in every export	Export first, open the files, extract representative chats, then summarize
Replika	Official policy: portable, machine-readable access rights where applicable	Not documented: companion import	Exact archive contents and access after cancellation for every account/region	Request access, preserve records and rebuild from a concise brief
Nomi AI	Not documented: rival-to-rival hidden-memory export	Official guide: Shared Notes and Backstory support a manual rebuild	Hidden-memory transfer, exact archive behavior and feature parity by platform	Put stable facts and boundaries in Shared Notes; teach tone through new chat
Kindroid	Official docs: user-editable backstory, key memories and journals	Official docs: those fields support manual reconstruction, not universal import	One-click rival import, complete hidden-memory export and model-to-model continuity	Split permanent identity from journal-style recallable events
SillyTavern	Official docs: locally stored chats and character cards	Official docs: cards, lorebooks and compatible chat imports	Compatibility with proprietary hosted-app exports	Use a redacted copy first and verify the target format before a full import
Candy AI / visual-first apps	Needs app-specific verification: privacy access rights and paid media entitlements vary	Not documented here: universal companion import	Archive completeness, media rights and import behavior	Save only assets you are entitled to keep and rebuild text context separately

An export is evidence, not an import package. Open one file before deleting the old account and confirm it contains the chats, dates and settings you expected.

Why is migration now a resilience problem?

Migration is not only for people who found a better app. A model can be retired, a policy can change, an account can be suspended, a payment route can disappear, or a company can close. In August 2026, public grief around retired companion-style model behavior showed how little warning users may feel they receive even when a platform considers the change routine.

That does not mean an AI companion is a person or that every service must preserve every model forever. It means users should treat relationship continuity like any other valuable digital project: maintain an export you can understand before an emergency.

Use three layers:

1. Official export: account data, chat files and settings supplied by the platform.
2. Continuity pack: a plain-text summary you control and can inspect.
3. Evidence folder: receipts, cancellation confirmation, deletion request and the source date for important policies.

The official export is the most complete but often the least portable. The continuity pack is less complete but much easier to rebuild elsewhere. Keep both.

Model retirement and forced-change checklist

A model update is not the same as an app-to-app transfer, but it creates the same continuity problem. Before a retirement deadline or forced migration, record:

Check	What to capture	Why it matters
Version	Current model, stable/beta status and change date	A later model may interpret the same backstory differently
Rollback	Whether the old model remains selectable, and until when	“Can switch back” is different from permanent access
Thread state	Current thread, synopsis, pinned facts and unresolved story beats	A summary may preserve facts without preserving tone or identity
Multi-character state	Each companion’s role, relationships and shared lore	Group dynamics are easy to flatten during reconstruction
Prompt rework	Backstory or directives changed for the new model	This becomes the recovery recipe if the migration goes badly
Recovery evidence	Export receipt, support ticket and readable local copy	A request confirmation is not proof the files are complete

Treat user reports about personality changes as a warning to make a backup, not proof that a particular model is worse. Model behavior is version-specific and subjective; repeat your own low-risk test before rewriting a long-running companion.

Is it a native export, a manual rebuild or a converter?

Method	What it preserves	Main advantage	Main risk
Native account export	Whatever the platform exposes	Official and usually most complete	Format may be messy or impossible to import
Manual continuity pack	Facts, tone, boundaries, history and examples you select	Private, readable and portable	Requires judgment and periodic updates
Character card	Persona prompt, scenario, greeting and examples	Useful across SillyTavern-style tools	Usually excludes hidden memories and relationship state
Third-party converter	Potentially automates format changes	Faster for large histories	It may receive intimate chats or account credentials

Avoid any converter that asks for your password, session cookie or API token without a clear security model. Even a legitimate converter can create a new copy of your most sensitive data. Offline conversion is safer than uploading raw history to an unknown website, but you still need to inspect the code or trust the tool provider.

How do you build a continuity pack another model can use?

The one-page brief earlier is the minimum. For a relationship with substantial history, keep a small folder of plain-text files:

00-read-me.txt          # purpose, source app, export date
01-character.txt        # identity, personality, speaking style
02-user-context.txt     # only facts you still want carried forward
03-relationship.txt     # timeline, routines, meaningful events
04-boundaries.txt       # consent, topics to avoid, content limits
05-style-examples.txt   # 5-10 short exchanges, not a raw archive
06-current-state.txt    # what was happening at the time of export

Keep permanent facts separate from temporary story state. Mark uncertain memories as uncertain instead of forcing the new model to treat them as canon. Remove real names, addresses, health details and third-party information unless they are essential and the new app’s policy justifies the risk.

Why do saved files not restore an AI companion’s memory?

A readable backup and a convincing first reply are different checkpoints. Neither proves that a new app has recovered the old companion’s hidden memory. Before cancelling access you still need, work through this small recovery check with a redacted copy.

Checkpoint	What to record	When to pause
Open the backup	File name, export date and one readable conversation	A download receipt exists, but you cannot read the files
Separate fact from inference	Where each important memory came from: your notes, a saved exchange or a guess	The only source is the new bot claiming it remembers
Place the minimum context	Which destination field holds identity, boundaries and current story state	You would need to upload an unreviewed raw archive
Ask a neutral question	Your prompt, the reply and any correction you made	The reply invents a shared event or crosses a stated boundary
Revisit in a later session	What remained available and what needed repeating	A promising first chat is your only evidence of continuity

These are suggested checks, not results of comparative app testing. A correct answer may come from the current conversation rather than persistent memory. Record the app, model and date instead of treating one reply as proof of successful transfer.

If the summary needs work, use the AI character backstory template to separate identity from temporary plot. The boundary prompt examples help state preferences without adding private history; a prompt is not a guarantee the app will follow it.

Keep a recovery log beside the worksheet

Backup file opened and checked on:
Memory or preference being checked:
Source: saved exchange / my note / uncertain recollection
Destination field and model/date:
Neutral question asked:
Observed reply, without interpreting it as hidden memory:
Correction needed:
Later-session observation:
Still missing or not transferable:
Next action: revise / keep checking / stop

Keep this log local where practical. Do not send intimate transcripts to support just to demonstrate a tone change. For billing, preserve the receipt and cancellation confirmation separately; the cancellation guide covers that workflow.

How do you migrate to a local or SillyTavern setup?

SillyTavern is a locally installed frontend built around character cards. It can preserve a character definition, greetings, example dialogue, personas and chat histories in a more user-controlled environment. It still needs a model backend, and that backend determines conversation quality and whether prompts remain local.

Moving into SillyTavern therefore has two migrations:

• character migration: card, lore, persona, style and chats;
• model migration: choosing a local or hosted model that interprets those instructions well.

The same card can feel noticeably different on another model. Test with non-sensitive history first, tune the prompt, then import only what you need. Our researched private and offline companion guide explains the complete stack and its privacy boundary.

What is a 30-minute emergency export plan?

If a shutdown or model retirement is imminent:

1. Start the official account export immediately; it may take time to arrive.
2. Copy the current backstory, pinned facts, memory fields and character definition.
3. Write a 500-word relationship summary while the context is fresh.
4. Save five representative conversations and label why each matters.
5. Download only media you are allowed to retain; do not assume generated assets are transferable.
6. Capture the billing status and cancel recurring payment through the original channel.
7. Keep the old account until the export is checked, unless safety or privacy requires immediate deletion.

What are the privacy cautions before you paste old chats?

Migration can be more sensitive than normal chatting because you may gather months of private messages into one document.

Before uploading or pasting that document anywhere, ask:

1. Does the new app train on user chats?
2. Can staff or contractors access content?
3. Are chats encrypted at rest and in transit?
4. Can I delete the data later?
5. Is the app explicit about third-party AI providers?
6. Am I pasting someone else’s personal information?

Kindroid’s FAQ makes a strong public privacy claim around encryption for chat history, backstory, memories, prompts, and related sensitive information. Replika’s privacy policy says messages and content are processed to provide personalized companion functionality and may involve third-party AI language model providers, while also describing access and deletion rights. Character.AI’s help center documents export, but export is not the same thing as privacy-safe import somewhere else.

If your old chats include names, addresses, workplace details, sexual content, medical information, family conflict, or crisis conversations, summarize instead of pasting raw logs. A good migration brief can preserve the relationship without carrying every sensitive detail forward.

For a deeper privacy baseline, read Can AI companion apps see your data? and How to delete AI companion data.

What should you not do?

Do not delete the old account before saving the pieces you care about.

Do not assume an exported data file can be imported into another app.

Do not rely on screenshots as your only record if the relationship history matters.

Do not paste a full raw transcript into a new app just because the text box accepts it.

Do not use a third-party exporter unless you understand what it accesses, where it stores data, and whether it violates the app’s terms.

Do not expect the new app to reproduce every phrase, habit, or emotional beat. That expectation turns migration into disappointment.

What is the AI companion migration worksheet?

Copy this worksheet into a plain-text file. It is short enough for a backstory field and structured enough to revise after the first week:

SOURCE
Old app:
Account/platform (web, iOS, Android):
Current model/version:
Export date:
Export request confirmation:
Export format (JSON, HTML, text, other):
Files checked:
Chats/media/settings actually present:

IDENTITY
Name and role:
Core personality:
Relationship with me:

CONTINUITY
Important memories:
Daily routines:
Communication style:
Current situation:
Pinned facts or synopsis:
Unresolved story threads:
Multi-character relationships:

ASSETS
Avatar/voice files I am allowed to keep:
Character card or prompt I own:
Representative chat excerpts:

SAFETY AND PRIVACY
Boundaries:
Do not mention:
Sensitive details removed:
Third-party details removed:

DESTINATION CHECK
New app:
Backstory field used:
Memory/notes field used:
Import format tested:
What did not transfer:
Model/version used:
Monthly/free test end date:
Old subscription cancellation date:
Old account deletion date:

Fill it once, remove details the destination app does not need, then paste the relevant sections into its backstory, shared notes, memory, journal or setup field. Start the first conversation by explaining the move plainly:

I am recreating a companion from another app. Please treat the profile above as background, but do not pretend you literally remember conversations you were not part of. Ask clarifying questions when the context is missing.

That one sentence prevents a lot of fake continuity. The best rebuilt companion is honest about being rebuilt.

What’s the bottom line?

You cannot usually transfer an AI companion directly to another app. You can transfer the relationship brief: the name, tone, boundaries, routines, important memories, and story context that made the companion matter.

If you want the smoothest rebuild, choose a destination app with editable memory and backstory tools, keep the old account until the new one feels stable, and treat raw chat history as sensitive data. Nomi is friendlier for low-friction rebuilding. Kindroid is stronger for people who want memory controls. Replika and Character.AI are better handled as export-and-summarize cases rather than true transfers.

The goal is not to recreate every message. It is to carry forward enough context that the next version starts with respect for the old one.

If continuity is your first buying criterion, compare the best AI companions with long-term memory before choosing the destination. Portability should now sit beside memory quality in the decision: a companion that remembers you well but cannot be exported creates a larger future lock-in risk.

Sources & references

• Nomi guide: Nomi 101
• Kindroid docs: Memory
• Kindroid docs: FAQ
• Replika policy: Privacy Policy
• Character.AI help: How do I export all my data?
• SillyTavern docs: character cards and local/cloud backends
• SillyTavern FAQ: self-hosted models, chat storage and imports