# Migration Assistant, the app you hope to open once

> The 592 KB app that moves a whole Mac between machines, while daemons whose door names spell the wizard's steps do the lifting. Measured on a live Mac, receipts on disk.

Source: https://www.ribbonmac.com/guides/migration-assistant-mac · Updated 2026-11-19

The box opens, the new Mac starts, and within a minute a screen asks whether you want to move your stuff over from somewhere else. Later, months or years on, a folder in Utilities holds the same question in app form. That is Migration Assistant: the only Apple app most people hope to open exactly once.

Its own interface file, the one that holds every sentence the app can say, describes the job in a single line. Migration Assistant helps you transfer your data, settings and apps to this Mac from another Mac, a Windows PC, a Time Machine backup or a disk. You can also transfer information from this Mac to another Mac. Four doors in, one door out, and nothing about the app suggests the size of the machinery behind it.

Because there is machinery. The app you open is a front door, and the house behind it is staffed.

## 592 kilobytes of front door

Start with the app itself, measured on this Mac. It lives at /System/Applications/Utilities/Migration Assistant.app, a 592 KB bundle whose entire executable is 275,744 bytes, built for arm64e and arm64e.x1, version 1.0 build 973, project name MigrationAssistant, minimum system version 27.0. Signed by Apple on the sealed system volume, like every neighbour in Utilities.

One detail hides in the signing record. The bundle identifier is com.apple.MigrateAssistant, Migrate rather than Migration, a small disagreement between the app's name and its own paperwork that has survived every macOS release on record. And the paperwork is all there is: man Migration Assistant returns no manual entry, and a dedicated Migration Assistant guide book on Apple's support site returns not found. What documents this app is a pair of support articles, one for Mac to Mac, one for PC to Mac, both loaded and current as of this writing, the Mac one last updated in February 2026.

For contrast, walk one directory deeper. The Resources folder holds 40 language folders, the icon, and a set of interface files whose names tell the app's history better than any article: a Localizable table of 18 sentences, a MainMenu table, an InfoPlist table, and two named after panes, FUS Logout Pane and HandoffTargetLandingPane. Panes, plural, because this app is assembled from screens the way a wizard is, and two of those screens have outlived the era they were named in.

## The wizard's steps, spelled as door names

The heavy lifting belongs to a system daemon that the app talks to over Mach messages: systemmigrationd, living at /System/Library/PrivateFrameworks/SystemMigration.framework/Resources/systemmigrationd, 223,440 bytes, and unlike the front door it still carries an x86_64 slice alongside arm64e for the Intel Macs that can also run it.

Its launch file is the most readable description of a wizard ever committed to plist form. The daemon registers eight Mach services, and read in order they are the steps you click through:

```
com.apple.installandsetup.systemmigrationd.SelectSource
com.apple.installandsetup.systemmigrationd.Pairing
com.apple.installandsetup.systemmigrationd.MigrateFrom
com.apple.installandsetup.systemmigrationd.Progress
com.apple.installandsetup.systemmigrationd.Customize
com.apple.installandsetup.systemmigrationd.Management
com.apple.installandsetup.systemmigrationd.ODUtils
com.apple.installandsetup.systemmigrationd.Debug
```

Select a source, pair with it, migrate from it, watch the progress. The four you click are the first four doors. The other four are the service corridors: Customize for the category checkboxes, Management for the admins who push migrations with configuration profiles, ODUtils for Open Directory, and Debug for Apple's own engineers. The launch file also names a queue directory, /Library/SystemMigration/Queue, a place other parts of the system can drop transfer requests into, and on this Mac that directory exists and is empty, which is what an idle migration stack looks like.

launchd's ledger for the daemon on the measured Mac: state not running, runs 2 since the last boot, last exit code 0. It woke twice, did work, and went home. Both wake-ups are explained by a receipt later on this page.

## Two front ends, one engine

The first-boot screen that offers to move your stuff is not Migration Assistant wearing a costume. It is a second app, Setup Assistant, at /System/Library/CoreServices/Setup Assistant.app, 13 MB, project name MacBuddyX, and it runs the same migration panes through the same daemon. Apple's support article says it in one line: Migration Assistant is included with your Mac, both as an app and as part of the setup assistant that opens when you first start up a new Mac.

The binary of the Utilities app gives the game away with a single log string of its own: Buddy to start with pane: MigrationToAnotherMac. Buddy is the setup assistant's internal name, and the Utilities app literally starts a Buddy session when it needs the first-boot screens. Two doors, one house.

Count the staff. The system frameworks directory holds seven frameworks with migration in the name: MigrationKit, SystemMigration, SystemMigrationNetwork, SystemMigrationUtils, SystemMigration_SDKHeaders, TCCSystemMigration and CalendarMigration. TCCSystemMigration is the one worth pausing on, because it is the component that carries your privacy permissions across, the list of which apps may reach your camera and folders, which is why a migrated Mac asks so many fewer questions than a fresh one. Beside them runs a service called ContainerMigrationService out of /usr/libexec, whose launch file volunteers to be evicted under memory pressure and throttles its own restarts to one per second, the temperament of a tool that expects to run rarely and get out of the way.

## The logout choreography

People remember two things about a migration: the security code that must match on both Macs, and the strange moment when the app logs everyone out. The second one is choreographed to the sentence, because the strings are on disk.

Before a transfer the app tells you what must happen: before migrating your information, you need to log out of these user accounts, or this user account. Then the wait, rendered as a status line: waiting for the last user to log out. Then the action, with its own polite ellipsis: closing applications and logging out, one moment. And if the logout cannot complete, the flat admission: logging out failed, the exact words behind one of the most searched Migration Assistant complaints.

The window that carries this is not an ordinary window. The app's code holds a method named makeShieldWindows, and that is a literal description: when migration begins in earnest, the app lowers shield windows over the screen so that nothing else can be clicked, the same trick the login screen uses to be the only thing on the display. The giveaway about where this choreography came from sits in the resource named FUS Logout Pane, FUS being Fast User Switching, the older system feature for logging one account out to let another in. Migration Assistant's logout sequence is a descendant of that pane, which is why it behaves like a system takeover rather than an app dialog: it inherited the machinery from one.

## The receipt on your disk

Every migration leaves a paper trail, and on this Mac it is readable right now. /Library/SystemMigration/History holds a directory named Migration-D58BBB9D-D865-46E3-91AA-8642FE1670ED containing one file, Request, 23,196 bytes, stamped 20 October at 12:56. The Mac booted at 12:55 that day, straight after the macOS 27.0.1 update. One minute after boot, the migration stack clocked in.

Open the file and it decodes as a transfer manifest, an archived dictionary of every switch on the wizard's final screen: copiesMachineSettings, copiesNetworkSettings and copiesTimeZoneSettings all true; copiesUsers, copiesHomeDirectories, copiesPrinterSettings and copiesSecuritySettings all false; activateFilevault false; shouldMigrateGuest true. It lists the accounts it considered, by short name, with fields named preserveExisting and nonConflictingShortName for the rename-an-account case. And it names its source, which is the quiet surprise: file:///Volumes/Data/Previous System/, a directory the macOS updater created when it set the old system aside.

So the last migration on this Mac was not Mac to Mac at all. It was the operating system update itself, moving machine, network and time zone settings out of the previous system volume and into the new one, two months after the Mac was first set up on 19 September at 20:46, the timestamp still readable on /var/db/.AppleSetupDone. The same daemon, the same manifest format, the same queue. Migration Assistant the app is one customer of a system service that also serves the installer, which is the deepest answer to what this app is: the friendly counter of a depot that runs whether or not you ever walk in.

One more thing the manifest is worth knowing for. It is readable by every user on the Mac, and it lists account short names. Nothing in it is a password, but if you migrate and then hand the Mac on, that is a file to know exists.

## The helper that never went home

The depot keeps one clerk on the clock permanently. In the user session, launchd runs a process named migrationhelper, out of the SystemMigrationNetwork framework, and on the measured Mac its record reads like a zen koan:

```
state = running
runs = 1
last exit code = (never exited)
```

One run, started at login, still going 30 days and 5 hours later. The cost of that vigil: four hundredths of a second of processor time across the entire month, and 144 KB of memory, smaller than a screenshot of its own process list. Its launch file explains the shape of the job. No RunAtLoad, no KeepAlive. It registers one Mach service, so anything needing migration help can knock, and it signs up for exactly one event: a notification, from the notification center, that its own alert was dismissed. When a migration finishes and the last dialog is clicked away, this is the process that notices.

Even its binary is a little humbler than the front door's: 776,480 bytes, three slices, x86_64 alongside the two arm64e variants, because the network helper has to speak to old Macs as well as run on new ones. A translation tool that keeps the old dialect.

## The bill

Measured on a MacBook Pro, 10 cores, macOS 27.0.1, 30 days of uptime:

| What | Cost |
|---|---|
| Migration Assistant, the app | not running, 0 CPU, exists only when opened |
| systemmigrationd, system side | not running, 2 runs since boot, both during an OS update |
| migrationhelper, session side | running, 1 run, never exited, 0.04 sec CPU per month, 144 KB |
| ContainerMigrationService | idle, volunteers for memory-pressure eviction |

The one number that ever climbs is the one you cause. A transfer over Wi-Fi is hours of network work with progress bars over it; the same transfer over a cable, or from a Time Machine backup disk, is the same machinery with a wider pipe. When people say Migration Assistant is slow, they are usually describing their network, holding a clipboard, while the daemon next door stands ready with a van.

And after the van unloads, the new Mac spends its first evening indexing everything that arrived. That work belongs to Spotlight, and [the Spotlight indexing page](https://www.ribbonmac.com/guides/what-is-spotlight-indexing-on-mac) measures what that first night looks like from the inside. The backup that can feed a migration has its own anatomy, in [the Time Machine page](https://www.ribbonmac.com/guides/time-machine-mac). The screen the first boot hands you when migration is done is drawn by [the loginwindow process](https://www.ribbonmac.com/guides/loginwindow-mac). The app itself, once its work is finished, closes like any other, and only the helper stays behind, keeping the light on.

## FAQ

### What is Migration Assistant on my Mac?

It is the app that moves your accounts, files, settings and apps onto this Mac from somewhere else, and it lives in the Utilities folder of your Applications folder, or in Spotlight under its own name. Its own interface file states the whole job in one sentence: Migration Assistant helps you transfer your data, settings and apps to this Mac from another Mac, a Windows PC, a Time Machine backup or a disk, and you can also transfer information from this Mac to another Mac. Apple's support article on transferring to a new Mac adds the two promises people most want to hear: it does not delete information from your old Mac, and it does not replace the operating system on the new one. The app itself is remarkably small, a 592 KB bundle whose binary is 275,744 bytes, because the app is only the front door. The machinery behind it, a system daemon and a network helper, are the same ones the first boot setup assistant uses.

### How long does Migration Assistant take?

There is no single honest number, because the time is set by three things you choose before the transfer starts: how much stuff moves, where it moves from, and what cable the two machines share. Apple's own article says it plainly: large transfers might need hours to complete, and might seem to pause occasionally. The pauses are part of the design, not a sign of death, and the app even calculates the storage used by everything selected before the copying starts, so a long silence right after you click Continue is arithmetic, not a hang. Wi-Fi is the slow lane and the one most people get by default. A Thunderbolt or USB-C cable between two Macs, an Ethernet cable, or migrating from a Time Machine backup disk instead of a live Mac are all faster, and Apple's preparation list for the transfer asks for macOS to be up to date on both machines and for antivirus, firewall and VPN software to be turned off until you are done.

### Why is Migration Assistant stuck, or telling me logging out failed?

Two different stalls, two different causes. Stuck on starting up, before anything moves, is almost always the connection: the two Macs finding each other over Wi-Fi while a VPN or firewall is still running, which is why Apple's preparation steps ask you to turn those off first, or a Mac still waiting on an update. Logging out failed is the other stall, and it happens at the end, not the beginning. Before a transfer can start in earnest the app logs every other user out, and its own interface strings show the choreography: before migrating your information, you need to log out of these user accounts, then waiting for the last user to log out, and if the logout does not complete, the sheet that says logging out failed. A logged out check that never finishes is usually one open app refusing to quit, and the honest fix is to save in that app, quit it by hand, and continue.

### What password does Migration Assistant ask for?

Up to three, each at a different moment, and the app's own binary carries a preference key named launch-password for the ones it remembers. First it may ask for an administrator password on the Mac itself, because making changes to accounts needs permission. Then, for the accounts being moved, the rules differ by type: an administrator account being transferred asks you to click Set Password and choose a new password you will use to log in on the new Mac, while a standard account gets a temporary password shown on screen that you write down and hand over, and the person changes it at first login. Last, if an account with the same name already exists on the new Mac, you either replace it or rename the incoming one, and if the app asks you to authorize the transfer with the password of an existing user, that password belongs to the account already on the new Mac. When both Macs show the same security code, you are past passwords and into the transfer itself.

### Can Migration Assistant transfer from a Windows PC?

Yes, and the PC side is a separate free download from Apple called Windows Migration Assistant, installed on the PC, never on the Mac. The versions are matched to what each machine runs: version 3.2.1.0 for a PC on Windows 10 or later and a Mac on macOS Sonoma 14 or later, version 2.4.5.0 for Windows 7 or later and a Mac on Ventura 13 or Monterey 12, with older versions still available for earlier macOS releases. What moves from a PC is the portable subset: contacts, calendars, email accounts and similar, placed into the matching Mac apps, and the same no deletion promise applies to the PC. The Mac side needs no download at all. It is the same Migration Assistant this page is about, and the Windows PC simply appears as one more source to choose from.

### Is Migration Assistant running in the background right now?

The app itself, no. On the Mac measured for this page no Migration Assistant process existed at all, because the app runs only when you open it. What does run, on every Mac, all the time, is its helper: a process named migrationhelper, started by launchd at login, alive for the full 30 days of measured uptime on one run, never exited, holding 144 KB of memory and four hundredths of a second of processor time for the whole month. Behind it sits a system daemon, systemmigrationd, that was not running either and had run exactly twice since the last boot, both times during a macOS update. So if you see either name in Activity Monitor on an ordinary day, that is the standing appointment, not a transfer in progress.
