Scenario

Backup plan for replacing a Mac

The moment this usually goes wrong

The old Mac still works, so the backup plan feels optional. Then a trade-in deadline, repair appointment, failed migration, or rushed erase turns the old device into something you no longer control.

The risk is not only losing files. It is losing the exact combination of storage access, recovery password, app state, and source-folder knowledge that made the backup usable.

Back up before the old Mac changes

Create Azivault plans for the folders that matter: active projects, documents, archives, photos, exports, and any folder that is not already safely available somewhere else.

Run the plans manually before handing over the old Mac. A recent completed run matters more than a backup schedule that has not run yet.

Separate migration from backup recovery

Migration tools are useful when the old Mac is present and healthy. Backup recovery is the fallback when migration is incomplete, skipped, or unavailable.

Use Azivault for the folders you cannot afford to reconstruct manually. That could be a client folder, accounting export, project archive, writing folder, research set, or photo export that needs a clear restore path.

Keep recovery material outside the old Mac

A replacement Mac needs both the repository and the recovery material. Store the recovery password somewhere you can reach without the old device.

If you choose iCloud Keychain for recovery-key sync, still keep the recovery password. It is the durable fallback if Keychain access is unavailable during recovery.

Choose storage the new Mac can reach

External disks and network folders work well for same-location migration. S3-compatible object storage is useful when the old Mac might not be present or the replacement happens away from the original backup disk.

Run a replacement-Mac drill

Before the old Mac leaves, pretend the new one already arrived. Pick one completed run, reveal it in Finder, and copy a small file to a temporary folder.

The drill should prove three things: the destination is readable, the repository unlocks, and you understand where restored files will land.

Restore deliberately

Azivault is not a whole-system migration tool. Use it to restore selected folders and files from completed backup runs.

After importing or unlocking the repository on the new Mac, browse the backup in Finder and copy files to a safe location before replacing current working files.

What Azivault does not replace

Azivault does not recreate system settings, installed apps, login sessions, device management profiles, or every hidden application support folder. It is for selected-folder backup and restore.

That is a feature, not only a limitation: selected repositories are easier to store offsite, easier to reason about, and less dependent on the old Mac remaining bootable.

Related guides

FAQs

Can Azivault migrate an entire Mac?

No. Azivault restores selected files and folders from encrypted backup repositories. Use Apple's migration tools for full-system migration.

Can I restore after my subscription expires?

Yes. Azivault keeps restore access available for existing backups even when new backup creation is paused by expired access.

Should I test restore before erasing the old Mac?

Yes. Restore one small file from the latest completed run before erasing, trading in, or sending the old Mac for repair.