Replacing a Phone or Laptop? Migration Checks From Şevket Ayaksız's Technology Blog

null

A device replacement can look complete long before the important dependencies have actually moved. A new phone may have photos and apps while its mobile line still needs verification. A new laptop may open cloud files while an account recovery route or passkey remains tied to the previous device. The safer approach is to treat migration as a series of checks rather than one setup screen.

Permus Blog is an English-language technology blog owned by Şevket Ayaksız . Its home page is organized around Digital, Technology, Mobile, PC, Software and Web Design, and its recent practical guides cover device changes, account access, recovery and software support. Four of those guides are especially useful when replacing a phone or laptop because they focus on what should be verified before old hardware is erased, sold or set aside.

Keep the old phone until the eSIM works

Moving an eSIM is separate from copying applications and photos. Apple documents several activation routes, including carrier activation, Quick Transfer, QR codes and carrier apps, with availability depending on the carrier and device combination. On a supported iPhone transfer, activation on the new phone deactivates the previous SIM.

That is why the practical checkpoint is service, not merely a successful setup message. Before erasing the old phone, confirm that the expected number works on the new device. Test an outgoing call, check incoming service and temporarily disable Wi-Fi to verify mobile data. If the phone uses two lines, review which line is selected for calls and data. Apple also advises against deleting an eSIM as a troubleshooting step unless the carrier directs it, so keeping the old device intact until service is confirmed preserves a clearer fallback while problems are being resolved.

Know where your passkeys live

Passkeys reduce dependence on typed passwords, but they still depend on a credential provider and an account recovery path. FIDO Alliance material distinguishes synchronized passkeys from credentials bound to a particular device. A cross-platform provider can make passkeys available on a new device after the provider is configured, while other arrangements may require the old device or another registered authenticator.

Before retiring hardware, note which provider stores the passkey and which documented recovery method remains available if that provider cannot be reached. Then sign in on the replacement device using the intended method. This is a verification step, not a guarantee that every account will recover the same way. NCSC guidance similarly emphasizes that recovery and credential-manager access remain part of the authentication lifecycle, so the recovery route deserves the same attention as the passkey itself.

Test OneDrive recovery with a harmless file

Cloud synchronization and file recovery solve different problems. Microsoft documents version history for restoring earlier file versions, a recycle bin for deleted items and a broader OneDrive restore option for eligible Microsoft 365 subscribers. The broader restore can roll account changes back within its documented window, while permanently deleted recycle-bin items cannot be recovered through that feature.

A small test is more informative than assuming that a visible cloud folder is enough. Create a harmless document, save an initial version, change it and inspect version history. Restore the earlier content and open the file to confirm that it contains what you expected. For important material, also check whether any files remain outside synchronized folders. The purpose is to learn which recovery route applies before a real mistake or device failure creates time pressure.

Check used Android support by exact model

A second-hand Android phone can still feel fast while having little promised update support left. The useful comparison is not just the Android version currently installed but the manufacturer's policy for the exact model. Google tells owners of non-Pixel Android devices to consult the manufacturer or carrier for update information, and its Android guidance separates the Android version, security update, Google Play system update and build number.

For a used purchase, record the exact model and current update information, then compare those details with the manufacturer's official support policy. Do not calculate remaining support from the day you buy the handset unless that is how the manufacturer defines its commitment. For example, Google states that Pixel 8 and later models receive seven years of operating system and security updates starting from first availability in the US Google Store. Other manufacturers can use different terms, starting points and schedules.

Migration area	Check before retirement	Evidence that matters
eSIM	Keep the old phone until the new line is verified	Calls, incoming service and mobile data work as intended
Passkeys	Record the provider and recovery route	The replacement device can complete the intended sign-in
OneDrive	Run a small restoration exercise	The restored file opens with the expected content
Used Android	Read the exact model policy	Manufacturer support terms match the planned ownership period

What should happen before the old device is erased?

The common thread is sequencing. First make the replacement usable, then verify the dependencies that are easy to overlook, and only after those checks should the old device be wiped or transferred to someone else. A migration checklist cannot promise that data will always be recoverable or that an account will always remain accessible. It can, however, expose missing recovery paths while the previous device is still available to help resolve them.