Back Up AI Companion Chats Without Losing Their Memory

A conversation export can preserve every line you want to reread and still leave out what your companion needs to remember you. To back up AI companion chats, keep a readable archive and a separate recovery copy of the app’s data. Treat moving one character as a different task.

The aim is continuity: keeping the history you shared without assuming that a file containing those words can rebuild the relationship. Before changing computers or repairing an installation, decide what you need to recover and what evidence would show that it survived.

Choose a copy by what you need back

The short version: A readable archive answers “what did we say?” A recovery copy has a different job.

Local Waifu’s backup guide distinguishes the following operations. The recovery limitations described here are documented for version 1.7.3; check the guide against your installed release before following a procedure.

The documented conversation export contains chat-message records. It is useful for a private archive or your own processing, but the export panel has no general conversation-import control. Renaming that JSON file “full backup” does not change its contents.

For the underlying distinctions, see the anatomy of AI companion app data. A transcript and the state used for memory recall serve different purposes.

Visible memories are not the same as working recall

The short version: Check that memories can be used in conversation, not merely displayed after import.

Character transfer carries more context than a message archive. The guide describes character-related messages, memories, relationship data, and knowledge entities. It also says the links between knowledge entities are not transferred. Installed models and app-level preferences are outside this operation, as are provider keys and license activation.

Memory retrieval adds another distinction. A saved memory can have readable text and a semantic vector: numerical data used to find memories related in meaning to a new message. Keeping the text alone does not preserve that search behavior.

The guide describes a platform difference: macOS restores stored vectors, while Windows imports memories without them. Older Windows imports remain available through the Memory Book and keyword matching, rather than joining semantic recall as though newly created. Do not turn that into a guarantee that every export works with every memory model.

Before migration, choose one distinctive old memory as a reference. After transfer, inspect its text and ask a natural question that refers to it. A correct answer is useful evidence, but one answer cannot establish that every memory transferred correctly.

A database copy needs a consistent moment

The short version: Dragging a running database into a backup folder can produce an unusable copy.

SQLite’s official corruption guidance explains why: copying during a transaction can mix old and new content. Necessary data can also be in a journal or write-ahead log rather than only the main database file.

Its backup documentation describes database-aware approaches, including the Online Backup API and VACUUM INTO. These support consistent live-database copies. They are not instructions to paste database commands into your app’s data directory.

Use the backup procedure appropriate to your installed release. Do not assume a background sync client makes a transaction-consistent database snapshot. Do not remove journal files to make a folder look tidy. If your installation has crashed or reports damaged data, preserve the available files and seek support before trying replacements.

The committed Local Waifu guide explicitly warns against copying a backup over the live directory while the app runs. It also says version 1.7.3 has no complete Restore UI. A backup’s existence and a supported restoration procedure are separate requirements.

Build a backup you can identify later

The short version: Record what you saved, verify the output, and keep a copy away from the original drive.

Use this checklist before a migration, major update, or repair:

• Record the app version and operating system alongside the backup date.
• Export conversations to a fresh filename. Open the resulting JSON and check an older exchange as well as a recent one.
• Save a character export if moving that companion is part of the plan. Label it separately from the conversation archive.
• Use the release-appropriate app-data backup procedure, choosing a destination outside the live data directory with enough free space.
• Wait for completion. Inspect the destination and compare any reported file count and size; a folder appearing is not proof that copying finished.
• Keep another protected copy on different storage. A second folder on the same failing drive does not protect against losing that drive.
• Write down what remains unverified, especially whether recovery has ever been checked.

A short note such as “conversation archive opened; app-data copy saved; restore not verified” is more useful than “backup done.” Keep the note with the copy, without adding passwords to a plaintext document.

Backup files deserve the same care as the original chats. For storage protection, use the separate FileVault and BitLocker guide. That protection does not establish that the backup is complete.

Verify recovery without risking the only good copy

The short version: Keep the original untouched until a version-appropriate recovery process passes meaningful checks.

This article does not report a tested restore. For full-app recovery, obtain the procedure for your version before attempting replacement. Use a separate test environment where that procedure supports one; do not improvise an overwrite of your working installation.

Define success before the attempt:

• The intended character appears, with the expected identity and relationship information.
• Known old messages and the most recent expected messages are present in order.
• Selected memory entries contain their original text, and recall checks show no unexplained loss.
• Required models and settings are available or have a documented setup step.
• A restart leaves the recovered data accessible, without new errors.

A friendly reply alone is not a recovery test. Compare specific saved facts and inspect the history. Record discrepancies rather than assuming continued conversation will repair them.

Keep the original installation and earlier copies until those checks pass. Before retiring the old computer, review what deleting the app deletes so cleanup does not remove your remaining source of data.

The backup and migration guide is the place for current procedural detail. Match it to your installed release. Your archive lets you reread the past; verified recovery is what gives you confidence about continuing it.

Questions people ask

Back to the blog