How to Migrate AI Companion Chats to a New App Safely in 2026

Step 1: Decide what should and should not move

Make three lists: preserve, rewrite and discard, before opening the new app.

Preserve only what has ongoing value, such as a fictional character brief, a preferred response length or a conversation boundary. Rewrite anything that contains a real person's name, exact location, employer, medical detail, financial detail or private relationship history. Discard repeated small talk, accidental oversharing and data that you no longer want either provider to hold.

1. Write down why you are switching: cost, quality, mode, privacy or workflow.
2. List the minimum preferences needed for that goal.
3. Mark every personal identifier for removal or replacement.
4. Separate billing proof from conversation content.
5. Set a date by which the old account will be reviewed again.

Do not let the old app decide what is important simply because it has stored it. Migration is an opportunity to reduce the data footprint.

Step 2: Check export, retention and account controls

Look for the provider's current information about export, history, memory, deletion, backups, media and account recovery.

Product names and controls vary, so use the provider's own help or account pages rather than assuming that “delete chat” means “delete every copy.” Check whether an export includes attachments, timestamps, metadata or account identifiers. If you cannot find an export, make a short manual note instead of using an unofficial scraper or giving your login to another service.

1. Confirm whether you can access and download the records you need.
2. Review what an export contains before opening or sharing it.
3. Find the current route for deleting chats, memory, media and the account.
4. Check whether the old plan is billed directly or through an app store.
5. Save the provider's support and cancellation information.

Keep any file in a controlled location, protect it with your device security and delete temporary copies. An export is another copy, not a privacy solution by itself.

Step 3: Build a redacted transfer pack

Create a short, provider-neutral note with goals, tone, boundaries and fictional facts instead of pasting a full transcript.

Use this structure:

Transfer pack: “Goal: a calm, concise conversation partner. Tone: warm, not overly familiar. Response length: under 100 words. Boundaries: do not claim to be a human or pressure me to continue. Confirmed fictional facts: the character likes coastal walks and old films. Current workflow: ask one question at a time. If a fact is missing, say so instead of inventing it.”

Remove real names, exact dates, addresses, workplace details, financial information, health records, intimate images and another person's private messages. If a fact is necessary, replace it with a label such as [CITY] or [PERSON A]. The new app should receive a useful specification, not your entire history.

Step 4: Test the new app before transferring personal history

Run a small fictional test that checks tone, boundaries, context, privacy and cost before importing anything sensitive.

1. Open a new conversation with the redacted transfer pack.
2. Ask two neutral questions and one follow-up about a fictional fact.
3. Test a boundary by asking the companion to admit uncertainty.
4. Check whether history, memory, voice or media is enabled by default.
5. Record what worked, what was invented and what you would need to repeat.

Do not treat a friendly first reply as proof of reliable long-term memory. NIST recommends considering trustworthy characteristics through use, testing and evaluation; this small repeatable test helps you make a product-fit decision without pretending to run a formal benchmark.

Step 5: Review cost and cancellation before switching fully

Confirm the new plan's real limits and the old plan's billing route before you run both services for another month.

Test the workflow on the free or lowest-risk path where available. Write down expected weekly messages, voice minutes, media requests and storage needs. Then check whether those units map to the new plan, credits or add-ons. Verify renewal timing and whether the subscription is controlled by the provider or an app store.

1. Confirm the new app supports the mode and limits you actually need.
2. Check current price, renewal, credits, storage and media conditions.
3. Cancel the old plan through the correct billing channel.
4. Keep cancellation confirmation and relevant payment records.
5. Wait until the new workflow is usable before deleting the old account.

Do not keep paying for two services because you have not decided what to transfer. A short overlap can be reasonable for testing, but set an end date and avoid uploading more personal data while comparing.

Step 6: Delete unnecessary copies and close the old account

After access, billing and records are settled, remove temporary exports, old media and account data you no longer need.

Review your own downloads, cloud backups, synced devices and shared folders. Check the old provider's deletion information and note any stated retention or support-record limits. You cannot verify every backend copy yourself, but you can stop creating extra copies and use the account controls available to you.

If you need a receipt or dispute record, keep that separately from the chat export. If you discover that the new app requires more sensitive information than you accept, stop the migration and use an offline or less personalized workflow instead.

When should you stop the migration?

Stop when export or deletion is unclear, the new service pressures you to overshare, or the cost and privacy tradeoff no longer fits the goal.

A new interface is not automatically a better fit. Return to your original reason for switching and compare the result against that requirement. If the service cannot meet a basic boundary, misrepresents what it remembers or makes cancellation hard to verify, do not add more history in the hope that it will improve.

Keep the redacted transfer pack for future comparison, or delete it when it is no longer useful. You can switch again without repeating the full data trail.

Summary: a privacy-first migration workflow

Decide what matters, audit export and deletion, build a redacted transfer pack, test fictional content, check billing and clean up old copies.

Migration should reduce uncertainty and unnecessary data, not simply move every old message to a second provider. Compare chat, memory, media, privacy, price and cancellation, then keep the smallest working setup that meets your use case.