GrapheneOS backup checklist before you switch phones
Prepare your important data and recovery routes before ordering. After delivery, check what actually works on the new phone before you erase, sell or trade in the old one.
By GhostSims · Source guidance checked .
Plan before purchase; verify restoration after delivery
Switching to a prepared GrapheneOS phone still requires a plan for your files, app data and account access. Start with the things you cannot afford to lose, then identify a supported route for each. If you do not have the destination phone yet, leave its restore checks marked “not tested”.
This is an editorial readiness checklist, based on current documentation. We have not performed a hands-on migration of your apps or tested a complete device restore. Buying a phone does not establish that your accounts or data will be transferred for you.
Understand what GrapheneOS backup covers
GrapheneOS includes Seedvault encrypted backups, supporting local storage and cloud storage through a storage-provider app. Its FAQ says OS backup must be explicitly enabled. Check the destination and recovery requirements of the backup you actually intend to use.
Coverage depends on the app and backup method. Android’s developer guidance distinguishes cloud-backup and device-transfer behaviour. Confirm important data through the app’s supported process and inspect the destination result.
GrapheneOS currently documents most Vanadium browser data as excluded from OS backups. Check the current browser-specific export/import options for each item; do not infer complete browser-state restoration.
A file copy, an app’s own export, account synchronization and an OS backup have different scopes. The GrapheneOS file-transfer FAQ explains that shared-file transfer does not include internal app data. A successful backup timestamp alone cannot tell you whether everything you need will be usable on another phone.
Make a migration inventory before you order
Use this matrix to find missing evidence. For each important item, record where it lives now, the app or provider’s current instructions, and any requirement to retain the old device. Scroll the table sideways on a narrow screen.
| What matters | Before ordering | After delivery, before retiring the old phone |
|---|---|---|
| Photos, downloads and documents | Locate originals, including files held only inside an app or cloud account. Make an independent copy of irreplaceable files and open representative copies. | Confirm required files reached the new phone. Open samples from different folders and dates; check any essential offline access. |
| Contacts and calendars | Identify the account or local store that holds them. Confirm its supported export, import or synchronization route and access requirements. | Check important contacts, recurring events and the date range you need. Confirm changes reach the intended account where synchronization is used. |
| App-local data and messages | Check each app’s official migration instructions, Android availability and installation source. Record old-device, version or recovery prerequisites. | Inspect required history, attachments or records and try an ordinary task. An installed app or visible account name alone is incomplete evidence. |
| Browser information | List essential bookmarks, saved information and website access. Confirm a supported route for your actual browser; record anything without one. | Check required information and website access directly. Keep missing items unresolved rather than assuming OS backup included them. |
| Accounts and authentication | Check passwords and provider-approved recovery routes. Review authenticator, passkey and work-account requirements individually; retain required old-device access. | Verify sign-in and essential account actions through the intended method. Confirm recovery access without deleting your working credentials prematurely. |
Save a private note for each critical item: item → current location → official method and date checked → old-device requirement → preparation status → destination result. Use “unknown” or “not tested” where appropriate. Record references and outcomes, keeping passwords, backup keys and recovery codes out of shared notes or support messages.
Resolve the purchase blockers first
- Choose the essentials. List the files, histories and account actions needed for daily use. A rarely used but irreplaceable record belongs on the list too.
- Confirm each supported route. Read the app or account provider’s current instructions for your source device and intended Android destination. Ask about unclear prerequisites before paying; do not assume an existing cloud backup can be imported.
- Prepare independent access. Check copies and recovery options while the old device still works. Keep any old device required by the documented transfer process available.
- Ask what the selected phone includes. Confirm the exact model, supplied setup and work you must complete. A prepared handset is not evidence of a seller-managed migration service.
Send GhostSims your purchase requirements: the proposed phone, essential app names, source-device type and unresolved setup questions. Ask the app provider about its data-transfer rules. Share the requirement rather than private backups or account credentials.
Check the destination before you retire the old phone
Follow the supported instructions for each item, then record the actual result on the new phone. Check representative files and important older records as well as recent ones. Verify essential logins and normal app tasks. Leave a partial history or untested account explicitly open.
Use the existing banking-app checklist for bank access and approvals, and the notification readiness guide for essential alerts. Successful data restoration and reliable daily operation are separate checks.
Keep the working phone and independent copies until your critical items are verified. If an important item is missing, pause retirement and consult its provider; erasing the source device can remove your remaining transfer route.
Use the record to decide your next step
- Ready to consider the phone: essential items have documented preparation routes, required source access is available, and you accept the remaining after-delivery checks.
- Confirm before ordering: a critical app, recovery route or supplied service remains unknown. Resolve that specific question first.
- Keep the existing phone in service: after delivery, required data or account access is still missing. A completed backup does not close that item.
Compare GhostSims GrapheneOS phone options around those requirements. For retaining your carrier number, use the separate existing-number eSIM guide. Data migration does not establish transfer of a SIM, service credit or subscription entitlement.