Tutorial · Task guide

Export, Back Up, and Move Foreverse Data Without Losing Local Work

Updated · 2026-08-10Public document

Direct answer: Before changing phones, uninstalling, or switching between Play and site packages, inventory every local asset family and export each supported format. Copy the exports to storage outside the app, verify that files open and have non-zero size, then import on the destination while the source still exists. API keys and encrypted preferences may need to be configured again; never copy encrypted preference key files between devices.

Before you start

Enough external/cloud storage for exports and generated media.
Access to both source and destination devices/installations until verification finishes.
Provider/API credentials available from their official consoles for secure re-entry.

Where to find it

Me > Advanced settings > Data > Full library backup
Chat > ⋮ > All tools > Export
Companion profile > Export companion backup
Card/Worldbook > Export
Generated asset > Save/Share

Step-by-step

Inventory before touching the installation
List books and branches, character cards, worldbooks/presets/regex/QR/Persona, chat sessions, Companions, generated media, custom themes/skills, account state, and BYOK providers. Mark irreplaceable items.
Export by asset family
Use each feature's export: original-format card/worldbook where available, chat export per session, Export companion backup from the Companion profile, book/project export or the Pro full-library backup, and save/share generated media to user storage.
Move the files outside app storage
Place exports in a clearly named folder on SAF-accessible storage, computer, or trusted cloud. Include the date and source package/version in a small note, but never put API keys in it.
Verify before deleting anything
Check file count, size, and archive integrity. Open representative txt/json/png/zip/media files. On the destination, import into a test copy and verify chats, memory, lore and assets—not just the item title.
Reconfigure secrets and finish the move
Sign in as intended and add BYOK keys from provider consoles. Test one low-cost request. Keep the source installation and exports until the destination passes the complete checklist.

How to know it worked

Every irreplaceable asset family has an export outside app-private storage.
Representative exports open and archives are not empty/corrupt.
Destination imports contain body content, branches/history/memory and referenced assets as applicable.
A provider can complete one small request after credentials are re-entered.
Source data has not been removed before destination verification.

Cost, data, and irreversible-risk notes

Export/import itself should not call AI. Full-library backup may be a Pro-gated convenience; individual supported exports remain the fallback.
Generated media may already have been billed when created. Saving/exporting it is not a reason to regenerate; if saving fails, preserve the successful task and retry delivery instead of paying again.
Play and site release builds share the package name but can have different signing certificates; switching can require uninstalling, which clears local app data.
Backups can contain novels, private chats, memory and personal media. Encrypt trusted storage and do not share the bundle publicly.
EncryptedSharedPreferences/keystore material is device-bound. Copying those files is neither a safe nor supported way to move BYOK secrets.

Troubleshooting

The new APK cannot install over the old one / signature conflict

Likely cause: Play and site builds were signed differently even though the package name matches.

What to do: Do not uninstall yet. Export and verify all local data, then uninstall the source only when ready for a clean install and manual import.

Import recognizes a package but content/assets are missing

Likely cause: The export was incomplete, external references were unavailable, or only metadata was copied.

What to do: Return to the intact source, make a fresh export with assets present, compare file sizes/counts, and test the new package before removing the source.

BYOK providers appear but keys do not work after moving

Likely cause: Device-bound encryption cannot be restored by copying preference files, or credentials were not re-entered.

What to do: Delete any broken copied secret state, add keys again from the official provider consoles, and run a small connectivity test. Never sync keystore files.

Backup/export file is 0 bytes or archive will not open

Likely cause: Storage permission, cancellation, out-of-space, or interrupted write.

What to do: Keep the source data, free space, choose a writable SAF location, export again to a new filename, and verify before leaving the screen.

Frequently asked questions

Does account sign-in restore all local books and chats?

Do not assume so. Credits/account state and local creative data are different. Export local books, branches, cards, chats, Companion memory and media explicitly.

Can I copy Foreverse's encrypted preference files to another phone?

No. Device keystore material does not safely transfer. Re-enter BYOK keys from provider consoles on the destination.

When is it safe to uninstall the old app?

Only after exports exist outside app storage, representative files open, and the destination import has been checked for actual content and assets.

Sources and verification

Settings and Data guide · Foreverse · Verified 2026-08-10
Home Library and Import guide · Foreverse · Verified 2026-08-10
Roleplay Chat guide · Foreverse · Verified 2026-08-10
Agent and Companion guide · Foreverse · Verified 2026-08-10

Coverage and verification

Platform	Android data management
App version	v76+
Path verified	2026-08-10

← Tutorials & Help

Before you start

Where to find it

Step-by-step

Inventory before touching the installation

Export by asset family

Move the files outside app storage

Verify before deleting anything

Reconfigure secrets and finish the move