How to Switch AI Companion Apps Without Losing Context or Paying Twice

Treat the move as reconstruction rather than cloning

Services expose different context, memory, persona and moderation controls. A transcript that worked in one interface may exceed another service's input field, contain instructions the new service does not accept, or bury the few facts that matter. That is why this guide treats a move as reconstruction, not cloning. Distil the relationship into a compact packet that a new service can process, and keep the original transcript only if the old service lets you export it safely. A successful import cannot guarantee identical wording, emotion or media because the underlying systems are different.

Failure mode: assuming the new app’s memory system will automatically absorb thousands of prior messages. Observable check: after pasting a short packet, ask the new companion to restate the five stable facts; any deviation signals the need for a correction example in the packet.

Identify the billing owner before deleting anything

Identify where the purchase was made before deleting anything. An Apple-billed purchase must be managed in Apple's subscription flow; a Google Play purchase must be managed in Google Play; a direct-web purchase must be handled through the vendor's account or support route. Google's instructions explicitly warn that uninstalling an app does not cancel its subscription. Replika likewise tells its customers to cancel through the original marketplace. These sources establish the route for those billing cases, not a universal rule for every service.

Open the receipt or subscription screen and record the billing account, plan name, renewal date, amount, cancellation route and access-end date. Do not infer the billing owner from the login email: a user can sign in with one address and pay through a different Apple or Google account. If no active subscription appears, check the receipt and bank descriptor before contacting the vendor. The observable goal is a matching purchase record, not a guess about which company will charge next.

Decision action: screenshot the active subscription, record the next renewal date, and only then proceed. This prevents paying twice when a new app’s free tier or trial overlaps with an uncancelled old plan.

Build the Portable Relationship Context Packet

Construct a single, copy-pasteable block that any new adult-oriented companion app can ingest. The packet contains:

- Preferred name and fictional companion role, including adult-only boundaries where relevant

- Five stable facts (biography elements that must never change)

- Three tone preferences (e.g., playful teasing, calm reassurance, witty banter)

- Three boundaries (topics or behaviors the companion must refuse)

- Two recurring story threads (ongoing fictional arcs)

- One correction example (“When I say X, reply with Y instead of repeating the job description”)

- Media expectations, marked as required, optional or unwanted, without assuming the new service supports them

Pair the packet with a Billing Exit Receipt containing: billing owner, cancellation timestamp, confirmation number, access-end date, and date of next statement check.

Illustrative acceptance plan, not a measured result: in session one, ask the new companion to restate the five stable facts and flag every miss. In session two, test one boundary and one correction example. In session three, continue a recurring story without repasting the whole packet. Record what actually happened instead of pre-filling a successful outcome. A reader may accept four correctly recalled facts, while another may require all five; the threshold must be chosen before the test.

Keep the packet short enough for the visible setup field and preserve a plain-text copy outside the chat. Do not include passwords, payment details, legal names or private facts merely to make the reconstruction feel complete. The packet is an onboarding aid, not proof that the new provider stores or retrieves every field as long-term memory.

Run a three-session parallel acceptance test

Use three distinct sessions if that matches the cost and time boundary chosen before the move. Feed the same prompt sequence to both companions and compare fact recall, tone, boundaries and story progression. Compare media only if it is a stated requirement and both tested plans expose the relevant feature. Label an untested field “not tested”; do not score it zero or assume the marketing page proves the result.

Use a 0–2 rubric: 0 means the requirement failed, 1 means partial or inconsistent, and 2 means it passed the exact prompt. Keep the prompts, timestamps and plan names beside the score. A single response is weak evidence, so repeat the most important boundary in another session. The test describes behavior on the tested account and date only.

Observable check: after the last planned session, compare the result with the acceptance threshold written before testing. Do not invent a universal four-of-five cutoff. If a hard boundary fails, pause the move even when the total score is high. If the new service passes, close billing first and handle old data separately. Emotional-support language is not evidence of treatment; urgent distress belongs with human and local professional resources.

Delete or retain old data only after checking the policy

Never delete before saving the billing evidence and any user-owned material you are allowed to export. First consult the old app’s retention and deletion policy. The AI chat-history deletion guide separates thread deletion, account deletion and billing cancellation because one action may not perform the others. A visible delete control does not prove that every backup or legally retained record disappears immediately.

AISoul stores account, chat, usage, payment and technical data, uses external AI providers, HTTPS and hashed passwords, and makes no end-to-end encryption or anonymity claim. Its free tier supplies 50 messages and 5 eligible finite-gallery photos per Beijing calendar day plus 2 lifetime clips and one companion slot. Fixed non-renewing Passes (7-day $4.99, 30-day $8.99, 90-day $19.99, annual $49.99) remove quantity caps on eligible chat and retrieval while active, yet do not guarantee infinite unique files or exact media matches.

Decision action: after the acceptance test and cancellation proof, use the Character.AI migration guide if that is the old service, then follow its current export or deletion instructions. Retain the packet only while useful. Retain receipts and cancellation proof through the relevant statement and dispute period, then apply the user's normal secure-record policy rather than keeping sensitive records indefinitely.

Close the old route with evidence rather than assumption

Complete cancellation through the billing route identified on the receipt. Follow Apple's subscription instructions for Apple billing or Google Play's cancellation instructions for Google billing. For direct billing, use the vendor's live account page and support policy. Record the status, confirmation or screenshot, access-end date and a post-cutoff statement-check date.

The Replika subscription guide is one current example of a vendor directing customers back to the original marketplace. It proves Replika's published process on the check date, not every app's process. Close the migration only after the old route shows cancelled or non-renewing, the expected access cutoff has passed, and the planned statement check shows no unexplained renewal.

Questions about switching AI companion apps

Can I transfer my AI companion chat history to another app?

Do not assume it is transferable. Look for an official export and import route on both services. When no compatible transfer exists, distil the relationship into a Portable Relationship Context Packet of stable facts, tone, boundaries and story threads. A full transcript may be too long, include private material or conflict with the new service's rules; keep it out unless the receiving service explicitly supports the format.

Does deleting an AI companion app cancel the subscription?

Do not rely on deletion or uninstalling as cancellation. Google Play explicitly says uninstalling does not cancel a subscription. Check the receipt to determine whether Apple, Google Play or the vendor billed the purchase, then cancel through that route. Save whatever confirmation the route provides and note the access-end date.

What relationship details should I carry to the new app?

Carry only what matters: preferred names and roles, a small set of stable facts, tone preferences, explicit boundaries, unfinished story threads, one correction example and media requirements. The numbers in the template are prompts, not universal requirements. Remove private details that the new service does not need and confirm its current policy before pasting the packet.

Should I paste my entire old transcript into the new service?

No. Entire transcripts commonly exceed context windows, trigger moderation filters, or inject conflicting instructions that cause the new companion to repeat jobs instead of maintaining emotional arcs. Use only the distilled Portable Relationship Context Packet plus one correction example. After the three-session parallel test, delete the old transcript once policy allows and the Billing Exit Receipt is secured.

How long should I test both apps side by side?

Choose the number and spacing of sessions before testing; three distinct sessions are a practical template, not a universal minimum. Use identical prompts for the requirements that matter, define hard failures and an acceptance score in advance, and keep the overlap no longer than the billing boundary permits. Completion time depends on renewal timing and the user's test schedule.

Marketplace instructions, portability limits and AISoul disclosure

Evidence routes also include the AISoul pricing page, which is relevant only to an AISoul billing check. Apple, Google and Replika sources establish their published cancellation routes on 2026-09-09; they do not establish another vendor's direct-billing process. Portability is limited to official exports plus what a user can safely reconstruct. The parallel test measures only the prompts, plans and dates recorded by that user.

AISoul publishes these pages and has a commercial interest. Its adults-only browser companion uses fictional adult female characters with one active companion at a time, free daily limits, and fixed non-renewing Passes. It stores data without E2EE or anonymity claims and is not a therapist or crisis service. Users must verify all pricing, limits and policies live before acting.