SiftMac
Guide · 12 November 2026

Before you migrate to a new Mac: what to clear first, and what to keep

By Mohit Nippanikar, who makes SiftMac

Migration Assistant moves your old Mac onto a new one: your apps, each user account with everything in it, other files and your settings. It copies what you choose as it is, so years of build files, caches, old installers and backups of phones you no longer have can go across too. Clearing what rebuilds by itself first makes the copy smaller and quicker, and the new Mac starts out lighter.

The short version
In this guide
  1. What Migration Assistant copies
  2. What rebuilds by itself, so it can go first
  3. What you’ve finished with
  4. What to keep
  5. The steps, in order
  6. Questions

1. What Migration Assistant copies

On the new Mac you tick what to bring, and each choice opens up so you can pick parts of it. According to Apple’s Mac User Guide, the choices are:

So everything in your account goes across, hidden folders included. Migration Assistant doesn’t delete anything from the old Mac, and Apple warns that a large transfer can take hours. Time Machine’s local snapshots stay behind: they belong to the old Mac’s disk.

2. What rebuilds by itself, so it can go first

All of this comes back on its own on the new Mac, made fresh for it, so there’s no reason to carry the old copies across. Quit the apps concerned first.

FolderWhat it isBefore you migrate
~/Library/CachesFiles apps keep so they load faster.Safe Clear what’s inside each app’s folder. The apps rebuild them.
~/Library/Developer/Xcode/DerivedDataXcode’s build output and indexes.Rebuilds With Xcode quit. Xcode builds it again on the new Mac.
~/Library/Developer/Xcode/iOS DeviceSupportDebug symbols for each iOS version you’ve connected.Rebuilds Xcode copies them again when you plug a device in.
~/Library/Developer/CoreSimulator/DevicesSimulators, with their apps and data.You decide Remove ones you don’t use with xcrun simctl, below. Xcode can add them back.
~/.npm, ~/Library/Caches/Homebrew, ~/Library/Caches/pip, ~/.gradle/cachesPackage managers’ downloads.Rebuilds They download again when a project needs them.
node_modules in old projectsOne project’s installed packages.Rebuilds npm install brings them back.
Docker’s build cache and unused imagesInside Docker Desktop’s disk image.Rebuilds docker system prune asks first and keeps volumes. Images download again on the next pull.

The commands, for the tools you have (skip the lines for ones you don’t):

xcrun simctl delete unavailable
npm cache clean --force
brew cleanup
docker system prune

More on each, including simulator runtimes and Python: Xcode DerivedData, node_modules and Docker: what’s safe to delete, and what happens after you delete DerivedData.

Moving from an Intel Mac to Apple silicon? Homebrew lives in /usr/local on Intel and in /opt/homebrew on Apple silicon. Rather than bring the old one across, save a list of what you installed on the old Mac:

brew bundle dump --file=~/Brewfile

Then install Homebrew on the new Mac and run brew bundle --file=~/Brewfile there.

3. What you’ve finished with

4. What to keep

These should come across with you:

5. The steps, in order

  1. Update macOS on the old Mac. Apple asks for both Macs to be up to date, so update the new one when you set it up.
  2. Quit your apps, then clear what rebuilds by itself (section 2).
  3. Remove what you’ve finished with, empty the Trash, and restart the old Mac.
  4. Back it up with Time Machine. Migration Assistant can copy from that backup too, if you’d rather not have both Macs side by side.
  5. Turn off antivirus, firewall and VPN software until the transfer is done, as Apple advises.
  6. On the new Mac, open Migration Assistant: it’s offered during setup, and later in Applications › Utilities. Choose the old Mac or the backup, and untick what you don’t need.
  7. Afterwards, deactivate apps that count activations on the old Mac before you erase it or pass it on. In SiftMac that’s Settings › Licence › Deactivate on this Mac.

Questions

Does Migration Assistant delete anything from the old Mac?

No. It copies, and the old Mac keeps everything until you erase it.

Will my iPhone backups come across?

Yes. Finder keeps them in your account’s Library, which Migration Assistant copies with the account. Delete the ones you don’t need first, as in section 3.

How long does migration take?

Apple says a large transfer can take hours and may seem to pause now and then. The less there is to copy, the sooner it’s done.

Should I set up the new Mac from scratch instead?

You can: set it up as new, copy your files across yourself and reinstall your apps. It leaves every leftover behind, but takes longer, and you redo your settings by hand. Migration Assistant stays in Applications › Utilities if you change your mind later.

Or let SiftMac sort the old Mac first. Its free scan lists what rebuilds by itself (app caches, DerivedData, old simulators and device support files, and node_modules in projects you haven’t touched for a month or more) next to what doesn’t: used downloads, the Trash, and iPhone backups with the newest of each device marked. Each item says whether it comes back. Caches go straight away; anything that can’t rebuild waits 7 days on the Undo Shelf, which lives in your Library, so empty it with Free now before you migrate, or it comes across too. Nothing leaves your Mac.

Download SiftMac · scanning is free, and so is your first 2 GB of cleaning · See how it works