Time Machine is a good local snapshot tool. It’s not a backup strategy. This guide walks the clean migration: install macup, run both side-by-side for a month, verify, then decide whether Time Machine stays or goes.
Why leave Time Machine
You need off-site. Time Machine is local-only. A drive in the same room as your Mac is gone in the same fire.
You need versioned cloud. iCloud Drive syncs the latest version of your files; it’s not a backup, it’s a mirror. Delete something, wait long enough, and it’s gone from iCloud too.
You need multi-drive coverage, bandwidth throttling, encrypted off-site retention, or a policy that spans more than one Mac. Time Machine doesn’t do any of that.
Time Machine is fine for what it is — a local timed snapshot — and plenty of people keep it running alongside macup. This guide doesn’t tell you to kill it. It tells you how to migrate the responsibility for your backups, and lets you decide afterwards.
Step 1 — Don’t turn off Time Machine yet
The whole point of a migration is that you don’t have a gap. Time Machine keeps running while macup builds up its own history. You’ll decide at the end of this guide whether to retire it.
Step 2 — Install macup
Follow “Install macup and run your first backup.” That article covers the download, system-extension approval, and first sign-in. Come back here when you have the macup menu-bar icon running and you’ve signed in.
Step 3 — Add destinations
macup separates the backup set (what to protect) from the destination (where it lives). Set up at least one destination before your first backup set:
- macup Cloud — managed off-site, immutable, zero configuration. The direct replacement for “I want an off-site cloud copy.”
- External drive — fast local restores, same physical exposure as Time Machine. Good as a second tier.
- Bring your own storage — your own S3-compatible bucket, if you want to own the bill and the data path.
Most Time Machine migrants pick macup Cloud for off-site and an external drive for fast local recovery. See “Back up to macup Cloud” and “Back up to an external drive.”
Step 4 — Create a backup set for your home folder
Create a set called Home, point it at ~ (your user folder), leave the defaults. macup auto-excludes caches, system noise, and anything in ~/Library that shouldn’t be backed up. Click Back up now.
First snapshot takes the usual hours — scales with data size and upload speed. macup shows progress per file. You don’t have to wait at the keyboard; close the lid and it resumes.
Step 5 — Keep Time Machine running
No conflict. macup and Time Machine read the same filesystem but use different disk I/O paths, and neither of them gets confused by the other. Leave Time Machine on. Leave its drive plugged in. Carry on.
Step 6 — Wait 30 days
This is the part most people skip, and it’s the part that matters. Before you rely on macup exclusively, you want at least a month of real history — so you’ve seen daily snapshots accumulate, you’ve watched at least one retention prune, and you’ve gone through a real week of editing files.
Time Machine continues to act as a safety net during this window. If anything about macup surprises you, you haven’t lost coverage while you figure it out.
Step 7 — Run a test restore
Don’t trust the UI. Actually test it.
Pick a file, delete it, and restore it from macup. Pick a folder, rename it, and restore the previous version. See “Restore a single file” and “Restore a whole folder” for the step-by-step. A backup you haven’t restored from is a backup you don’t have.
Step 8 — Decide what to do with Time Machine
Three honest options:
- Keep it. Belt-and-braces is a legitimate position. A local hourly snapshot is a useful tier beneath cloud backup, especially if you work on large files and want a sub-second local restore.
- Disable it and reclaim the disk. If you’d rather have the disk back, turn Time Machine off in
System Settings > General > Time Machine, unplug, reformat the drive for whatever you want. - Repurpose the drive as a macup external destination. Format the Time Machine drive, add it as a macup destination, and it becomes your fast local tier. See “Back up to an external drive.”
What doesn’t come across
Time Machine’s local sparsebundle structure is a filesystem-level construct, not an importable backup format. macup doesn’t read it and doesn’t pretend to. Your macup history starts fresh on day one; your Time Machine archive stays exactly where it is, readable from Migration Assistant or from the Time Machine UI for as long as you keep the drive.
You’re not converting. You’re starting a new backup, in parallel, and choosing when — or whether — to retire the old one.