Zero IT involvement
User runs shft on both Macs. IT gets the migration log. No tickets, no white-glove sessions, no remote desktop.
Mac → Mac migration
Move every Mac in minutes, not days.
shft moves everything from the old Mac to the new one. Apps, preferences, dev environment, data. IT gets a migration log. Users get a ready Mac.
MDM-aware user mapping
Destination Mac already enrolled? shft detects managed accounts and rewrites every path in preferences and configs. jsmith becomes john.smith cleanly.
Engineering tools, accounted for
Homebrew, dotfiles, shell configs, version managers, dev directories — scanned, migrated, and itemized. Engineers get a checklist of exactly what to verify.
Everything that matters
What shft moves
Six categories. Scanned, sized, and previewed before a single byte moves.
User files
Documents, Desktop, Downloads, Pictures, Music, Movies, and any custom folder in your home directory.
~/Documents · ~/Desktop · ~/Downloads
App preferences
Settings and support files for every app. Compatibility-checked against the destination first.
~/Library/Preferences · ~/Library/Application Support
Browser data
Bookmarks, history, and extensions from Safari, Chrome, Firefox, and Arc.
Safari · Chrome · Firefox · Arc
System settings
Dock layout, Finder preferences, keyboard shortcuts, accessibility settings.
Dock · Finder · Keyboard · Accessibility
Keychain items
Passwords, certificates, and secure notes. AES-256-GCM in transit. Never written to disk unencrypted.
Passwords · Certificates · Secure notes
Engineering tools
Homebrew, dotfiles, shell configs, version managers, and dev directories. Engineers get a post-migration checklist.
brew · .zshrc · ~/.ssh · nvm · ~/dev
How it works
1
Install shft on both Macs
One installer, same on source and destination.
2
Connect source to destination
shft discovers the other Mac over your local network.
3
Select what to migrate
Pick the categories you want — shft handles the rest.
Built for IT
Security, policy, and audit — by design
Native macOS. Zero third-party dependencies. Configurable from your MDM.
Encrypted end to end
Pairing derives a 256-bit session key. TLS uses EC P-256 with certificate pinning. Every chunk verified by SHA-256.
- 6-digit code → HKDF → 256-bit key
- EC P-256 TLS, cert pinning
- SHA-256 per chunk, 3 retries
- AES-256-GCM for keychain
Policy from your MDM
Sixteen keys in the com.shft.config profile let admins cap categories, sizes, connection types, and time windows.
- allowedDataCategories
- maxTransferSizeMB
- allowedConnectionTypes
- migrationWindowStart/End
Every migration, logged
A per-device migration log POSTs to your endpoint when the transfer completes — categories moved, sizes, duration, and an engineering tools audit.
- JSON log per migration
- POST to your endpoint
- Engineering tools audit
- No PII unless you ask
Ready when you are
Migrate the next Mac in minutes.
Buy a license, run shft on the old and new Mac, walk away.