Device Upgrade & Data Migration

Ax1

Hi everyone! :-)

I'm considering upgrading to a new Pixel phone, but the key question is how painful the migration will be.

Obviously, I don't want to install and configure hundreds of programs from scratch over again, and if there isn't a way to avoid this, then it's a big problem and an upgrade stopper.

Is there any data migration feature in GrapheneOS?
Smth like paring the current older Pixel and the new Pixel, syncing/migrating all programs/data/settings/etc, and then just continuing living with the new Pixel and formatting the old one.

If yes, is there any instruction? How can I perform this migration?

If no, is the eternal pain the only way? Are there any other options? Is it planned to add the migration feature to GrapheneOS?

de0u

Ax1 Is there any data migration feature in GrapheneOS?
Smth like paring the current older Pixel and the new Pixel, syncing/migrating all programs/data/settings/etc, and then just continuing living with the new Pixel and formatting the old one.

That would be awesome, but it is not an AOSP feature, and also not a feature GrapheneOS has added.

DirtyDan

There is Seedvault (Settings - System - Backup). Save the backup to an external storage device like a USB for purposes of migrsting to a new device. GrapheneOS prompts you if you want to restore from a backup upon first install of GrapheneOS and for each new profile. If you use multiple profiles, these are effectively treated like separate phones and need to be backed up individually.

I personally just backup and setup things manually. Nearly every app I have installed either:

Just requires that I login to an account and that's it. Maybe I spend 0-60 seconds configuring settings.
Offers a local import/export of app data and settings. I routinely export backups of my apps that offer this setting. I keep this data organized in my encrypted cloud storage, with each app having its own subfolder.

Setting up a new device for me usually goes in this order:

Confirm GrapheneOS integrity and that I'm up to date.
Setup owner. Go through settings. Settings up a new device is a good opportunity to discover new settings or make changes.
Install app installation sources.
Install password manager and 2FA.
Install and setup my encrypted cloud storage.
Start installing by apps one-by-one. Obtainium and F-Droid basic let you export your app list. Play Store adds your previous installs to your library. At the very least, just make a list or take a screenshot of the apps you use. I also take screenshots of some design things like how I organize my apps on my homescreen.
Start logging into apps and importing config data.
Bring over files and media.
Install SIM card.
Install Play Services, Google Messages and enable RCS. Simultaneously, configure Google permissions and settings (like deleting Advertising ID). Don't continue until I can confirm RCS is working.
Use SMS Backup & Restore to restore my messages. I usually do this part overnight since it can take awhile.
Setup additional profile(s) and/or private space(s).

Murcielago

DirtyDan

Thanks for the detailed description of your workflow (I do it pretty much the same way, by the way).

5 . Start installing by apps one-by-one.
[...]
9 . Install Play Services

I have a small suggestion regarding the order:

Installing an app that depends on Play Services and then installing Play Services won't work, so the order matters here

source: https://discuss.grapheneos.org/d/2702-how-well-do-push-notifications-work-with-sandboxed-google-play-services/2

Ax1

Seedvault doesn't work the expected way. There's a lot of stuff it doesn't back up / restore.

I was thinking of some kind of a seamless easy migration tool that just pairs the phones, sends the whole user data thing over to the new phone, and in 30 minutes or whatever it takes it's done and can start using the new phone with all stuff from the old phone.
Is it feasible?

I'm also ok with ADB-based solutions, if this the way to achieve the most complete backup-restore for migration

nologo

Ax1 I was thinking of some kind of a seamless easy migration tool that just pairs the phones, sends the whole user data thing over to the new phone, and in 30 minutes or whatever it takes it's done and can start using the new phone with all stuff from the old phone.
Is it feasible?

No. GOS is built for security. It prevents simple extraction of user data and storage of those data on a different device.

Ax1

That's sad.
Seems like model upgrade has to be indefinitely postponed then.
Pixel 6 is not much different from 7-8-9-10, so it will be fine.
Hope that a device-to-device migration tool (a proper one, for a Full migration) will be added in the future.

chinook

Ax1 yeah, if you really rely on the migration backup/restore software, it's tough. Seedvault mostly doesn't work, or rather somewhat works for some users.

Replacing it with some actual backup software is on the roadmap, but no idea if/when it will be picked up. Maybe Motorola will help with the new device next yet? I can imagine a series of ads aimed at execs and broadly security-conscious people (everyone can be a citizen journalist now!), and that would require a seamless migration solution.