Switching AI companion apps can feel simple until you realize how much relationship context has accumulated. Conversations, long-term memories, character settings, generated photos and subscription history may all live in different parts of the service. A good backup is not only a copy of the chat transcript; it is a record of the information needed to understand or rebuild the experience later.

Export conversations first

If the service supports export, download conversations before closing the old account. HTML or PDF is convenient for reading, while JSON or CSV is more useful for future processing.

Open the export once to confirm it contains the full history rather than only recent chats.

Save long-term memories separately. Many companions maintain a memory list that is not identical to chat history. Preferences, names, relationship facts and recurring goals may be stored as summaries.

Copy or export these items if the platform allows it.

Record character settings

Personality prompts, speaking style, relationship mode and custom instructions may be difficult to recreate from memory. Save screenshots or text copies of the configuration.

This is particularly important for user-created characters.

Download generated photos and videos. Media libraries may not be included in a conversation export. Save important images, videos and voice clips to your device before deleting anything.

Keep original resolution when possible.

Check voice assets

If you uploaded a voice sample or created a cloned voice, review whether the file can be exported and whether the service allows the derived voice model to move elsewhere.

Licensing restrictions may prevent direct portability even when the original recording belongs to you.

Save important dates and relationship milestones. A long relationship may include anniversaries, shared goals or recurring routines that are not obvious from a raw transcript. A short summary of these milestones can help if you rebuild the character manually.

Record account and billing details

Note which email or login provider is connected, when the subscription renews and whether unused credits remain. Cancel billing separately if the service requires it.

Backup and cancellation are different tasks.

Review what cannot be moved. Some relationship levels, platform-specific badges, recommendation history or proprietary memories may not be exportable. Understanding these limits helps set realistic expectations for migration.

Protect the backup itself

Conversation archives can contain highly personal information. Store them in a private location rather than a public cloud folder or shared computer.

Encryption may be appropriate for sensitive histories.

Create a concise migration summary. Besides the full archive, write a one-page summary of the companion: core personality, user preferences, important memories, boundaries and current relationship state. This can be more useful for rebuilding than thousands of raw messages.

Test the new service before deleting the old one

Move a small amount of context first and see whether the new companion behaves acceptably. Keep the old account active until you confirm that critical information has been saved.

Our AI Companion Account Deletion Checklist covers the final cleanup step.

Keep the backup format independent from one app. When possible, store important information in formats that can be opened without the original service. Plain text, JSON, CSV, standard image files and common audio formats are safer long-term than a proprietary archive that only one app understands.

It is also useful to keep the one-page migration summary in a simple document outside the companion platform. If the service becomes unavailable unexpectedly, that summary can preserve the essentials needed to rebuild elsewhere. A backup strategy is strongest when it does not depend on the same provider that created the data in the first place.

Backups should include a restore test

A backup is only useful if you can actually use it later. Open the exported files, search for a known conversation, confirm that images are readable and check whether dates and speaker labels are preserved. For important relationships, keep the one-page migration summary next to the full archive so you can rebuild the essential context without processing thousands of messages. Testing the backup once before deleting the old account is far easier than discovering a broken or incomplete export after access is gone.

Keep a human-readable relationship summary. A full transcript may contain thousands of messages but still be hard to reuse. Write a short summary with the companion’s role, the user’s preferred name, important boundaries, recurring goals, major shared memories and current relationship tone. This summary should be understandable without any special software. If another service supports import later, the structured archive can still be useful, but the human-readable version gives the user an immediate fallback and makes it easier to decide what context should actually be carried forward.

Portability starts with knowing what matters

The most valuable part of an AI companion may not be the transcript. It may be the combination of memories, settings and accumulated relationship context. A structured backup makes that value easier to preserve when products, devices or services change.