AOMEI FoneTool manages copies of iPhone and iPad data through a computer. It can back up selected items or a broader device state, move supported files between a phone and the computer, and transfer supported data to another device. It acts on device records, media, settings, and local backup archives. It is not a continuous cloud-sync service, and a backup does not automatically contain everything associated with an Apple account.
The distinction between selective and full backup controls what the user can inspect and restore. Selective Backup opens supported categories and lets the user choose individual photos, contacts, messages, music, or videos. Full Backup captures a wider device state in one operation. Both write to a chosen storage location on the computer rather than silently using iCloud space.
Choose backup scope
Selective Backup is useful when the goal is a readable local copy of chosen material. The category view can narrow a large photo library or contact list before the job starts. The resulting task appears in Backup Management, where AOMEI FoneTool keeps separate versions for later restores.
Full Backup includes device settings, application data, messages, call history, calendars, Safari data, and other supported records. Its name still has limits. It excludes media obtained through Apple’s stores, books and audiobooks, content synchronized from Finder or iTunes, Mail, Apple Pay information, and data that remains in iCloud. Application data can enter the backup, but the applications themselves need downloading again after a restore.
Guard the password
Backup encryption can add sensitive material such as Health records and Keychain data. The password then becomes part of the restore path. Changing the device’s backup password affects later backups; it does not rewrite older archives. An older encrypted backup still needs the password that protected it when AOMEI FoneTool created it.
Deleting the current backup password also leaves earlier encrypted copies unchanged. A forgotten password can therefore strand a backup even when the phone now uses a different one. The full-backup browser adds another constraint: Backup Management cannot open and browse the contents of a Full Backup. The user chooses a complete restore rather than picking one photo out of that archive.
Check the target
A full restore writes corresponding data onto the selected device. It needs free space greater than the backup size, and a backup created on a newer iOS release cannot restore to a device running an older release. Those checks matter when a person keeps several phones connected or reuses an older device as the target.
Device-to-device transfer also depends on a clear source and destination. AOMEI FoneTool uses USB connections for the route, so both devices must trust the computer and stay connected. Phone-to-computer and computer-to-phone jobs use different commands; reversing the intended route can place the wrong device in the receiving position.
Move WhatsApp carefully
WhatsApp Manager has a separate transfer workflow for chats and attachments. The direct iPhone-to-iPhone operation needs the paid function, two cables, and Find My iPhone disabled on the target. It overwrites the target’s existing WhatsApp data. Different WhatsApp builds on the two phones can also cause abnormal data after transfer, so both installations need updating first.
The target restarts when the operation finishes. During its setup screens, the user must follow the specified path rather than starting another device migration. This workflow moves WhatsApp records; it does not merge two unrelated chat histories into a combined account.
Manage local versions
Each backup run creates a separate version under its device task. Backup Management can locate the files on disk, delete one version, remove all versions, or import a task after its record has moved to another computer. Deleting a version can remove the stored backup file as well, so folder cleanup and in-program cleanup should not be treated as unrelated actions.
AOMEI FoneTool keeps these archives under the user’s control, which also leaves storage planning with the user. Full device copies can grow, and several versions can remain side by side. The Locate Backup command reveals the real repository, while the version list shows which restore points the program still recognizes.
