Migration Assistant doesn't recognize old iMac OSX

I just bought a new iMac 20 inch running Tiger. In the migration assistant (first initial setup), it asks if I would like to transfer files and settings from an old iMac using a FireWire cable (I do). After it prompts me, I boot my "old" iMac (PowerPC G4 running OS 10.2.8) in FireWire Target Disk Mode (pressing "T" while restarting). Then connect the FireWire cable from my old iMac to the new iMac. The migration assistant says that OSX is not installed on my "old" computer (which it is).
I've done some research on this forum about this topic. I've checked if my old Mac needs a firmware update (it doesn't). How can I fix this problem - I would really like to run the migration assistant from the get-go. Any assistance would be very appreciated. Thanks.
iMac Mac OS X (10.4.4)

One thing I don't know if it is relevant, but I found having the same username already created on my new machine when I ran the migration assistant caused it to fail.
If you haven't created anything essential on your new Mac, run the restore disks over again, and create an alternative user name:
http://docs.info.apple.com/article.html?artnum=61802
Once that is done, then try to run the Migration Assistant from the Applications -> Utilities folder, and then login the old username and delete the new one.

Similar Messages

Migration Assistant Won't Recognize "old" MBP via Fire Wire

I purchased a new MacBook: 2.16 GHz, Intel Core 2 Duo, 1 GB 667MHz DDR2 SDRAM, 160 gig drive
As usual when I get a new Mac, I erased the drive installed OS X.4.11-Tiger and personalized the mac.
Along the way, something odd happened. I cannot double click on any application and open it—unless—I place its alias into the dock. Then it opens.
I have run disk repair as well as permissions repair to no avail.
Want to use Migration Assistant to transfer files from my MBP to the MB. However, when I connect the Fire Wire, restart the "old" MBP with the "T" key depressed, the firewire wheel shows—but—the MB will not recognize the MBP. So, I can't transfer any data.
MBP has OS 10.4.10 while the MB has OS 10.4.11. Could this be the issue?
Anyone have any ideas as to how I can get past this?
Thanks,
Tek

I have the exact same problem. When setting up the new MacBook, I attached the firewire cable and restarted the PowerBook into target disk mode. The Firewire symbol appears on the screen but the MacBook gives the error message "There are no versions of MacOS X available on your old Mac". I wanted to test if it is a problem with the MacBook, and found that the MacBook will recognize and mount a portable firewire hard drive. Furthermore, when I tried attaching it to an intel iMac, it recognized it and was ready to import files from it. Therefore it seems that the problem is that the OS X 10.4.11 on the PowerBook is somehow 'invisible' to the MacBook migration assistant. I tried repairing permissions on the old PowerBook, but that didn't help. In the meantime I also ran software update on the MacBook, which brought it up to the very latest version of Leopard.
Could it be that the version of OS X needs to be the same on both machines? Next I am going to backup the PowerBook, then upgrade it to Leopard, then try again. I am surprised more people haven't had this problem, at least I have seen few postings about it.

Migration Assistant won't recognize old computer

Hi everyone!
I recently purchased a new MBP 2.8 GHz Intel Core i7, running 10.8.3 now. I'm trying to use migration assistant do transfer my files from a MBP 2.8 GHz Interl Core 2 Duo (running 10.8.3 as well) via firewire. I've puchased a thunderbolt to firewire adapter since the new MBP is not support firewire port anymore. However, the two computer was recognized when I was using wireless transfer but not the firewire connection. The wireless transfer was estimated over 80 hrs to transfer the files. After talking with Apple Support, I was informed that the firewire will be must faster. But the two computer won't recognize each other! What did I do wrong here? Please help!

I have the exact same problem. When setting up the new MacBook, I attached the firewire cable and restarted the PowerBook into target disk mode. The Firewire symbol appears on the screen but the MacBook gives the error message "There are no versions of MacOS X available on your old Mac". I wanted to test if it is a problem with the MacBook, and found that the MacBook will recognize and mount a portable firewire hard drive. Furthermore, when I tried attaching it to an intel iMac, it recognized it and was ready to import files from it. Therefore it seems that the problem is that the OS X 10.4.11 on the PowerBook is somehow 'invisible' to the MacBook migration assistant. I tried repairing permissions on the old PowerBook, but that didn't help. In the meantime I also ran software update on the MacBook, which brought it up to the very latest version of Leopard.
Could it be that the version of OS X needs to be the same on both machines? Next I am going to backup the PowerBook, then upgrade it to Leopard, then try again. I am surprised more people haven't had this problem, at least I have seen few postings about it.

Migration Assistant won't recognize my Time Capsule's sparse-bundle so I can migrate to my new iMac

Background.......
iMac (intel core duo) hard drive crashed while backing up to time capsule. Had Snow Leopard OS 10.6 (100% up-to-date)
2. Purchased new iMac with Lion. 100% updated.
3. Want to migrate from Time Capsule to new iMac
Problem.......
4. Migration Assistant does not see (recognize) my sparsebundle, message says it's "possible that it is in use." But it's not of course.
5. If I mount the Time Capsule from the Finder, I can see the sparsebundle I want to migrate. So, it present but the Migration Assistant doesn't see it!
6. Time Capsule recognizes the sparsebundle of my other Mac (#2) that backs up to the same Time Capsule
Question.......
What do I have to do to get Migration Assistant to recognize my sparsebundle so I can migrate to my new iMac?
Thanks

I finally solved the problem by disconnecting the Time Capsule ethernet cable from the internet. Then the sparsebundle suddenly appeared.

HT4889 Migration assistant doesn't see my 3TB Time machine it just keeps looking for other computers

I just did a clean install of Mountain Lion on my iMac and Migration Assistant doesn't seem to see my 3TB Time Machine. It continuously looks for other computers, and nothing else. I know the files work because I loaded it on my other MBP and it sees them just fine? am I just inpatient or is something wrong?

This happened to me after hard drive replacement under the Seagate Drive Recall at the local Apple Store. Here's what I learned from the process:
I Wagged the Mac home, fired it up (with naked OS installed at the Apple Store), and it wouldn't see my Time Machine drive with Setup Assistant - not on firewire 800 nor USB. Just a grey spinner that lasts forever. When I try just continuing anyway, it offers me something that looks plausible, but then puts up a dialog about duplicate user name, and no matter what I enter, it always says "that user already exists". So I think - maybe Migration Assistant. Complete the setup, create an account, watch the nice welcome movie. BAM - there's my Time Machine drive on the desktop. OK - it has to work . . . but no. Same behavior in Migration Assistant, plus the new OS offers to start making backups on my Time Machine disk - it's not recognizing it at all.
So - back to the Apple Store - let the genius figure it out. It turns out there are multiple problems. First, the "genius" who imaged my new machine picked 10.7.2 but my machine had 10.7.5 - turns out, it's not enough just to have right cat. Even a point release older OS may not recognize a newer Time Machine drive. The guy at the desk said "We have images of everything but the 10.7.2 has free iLife in it, so they like to use that one". What the heck? They don't image what you had originally as a matter of sane process?
Having figured that out, we re-image 10.7.5 at the store thinking we've fixed it. But no - Setup Assistant still won't see the Time Machine drive. Not on USB, not on Firewire. Not in a box, not with a fox.
So here's the second trick - newer machines have a recovery partion. see: http://www.apple.com/osx/recovery/ Boot with the option key held down, pick that partition, then you'll get a "system restore" option, to restore your whole system from a Time Machine backup. My drive was recognized by the recovery partition restore process when neither Setup nor Migration Assistant would. Obviously, there's something broken in Setup/Migration Assistant.
Takeaway:
- if you're getting a drive replaced by Apple, make sure they image *exactly* the same OS
- if Setup Assistant fails, use the recovery partition for system restore
- Use Recovery Disk Assistant http://support.apple.com/kb/DL1433 NOW to make yourself a recovery thumb drive just in case. With Apple's new "no media" approach to the OS, you're hosed without it.

Migration assistant doesn't "see" Time Machine disk

Just got a new logic board, and they wiped the hard drive. My Time Machine disk mounts, and I can see the files. However, migration assistant doesn't list it as a source. (Yes it's formatted Mac OS Extended [Journaled])
Time Machine recognizes it and wants to use it as a new backup disk, but it doesn't want to show me anything from the old back up. I didn't do a new backup of the "new" computer. I don't back up applications just users.
2.2 i7 MbP 8GB 10.7.4
thanks
DLS

Just back home from a follow-up visit to the Genius Bar on this migration issue (from MacBook Air to new MacBook Pro).
Previous efforts to migrate had taken endless hours and seemed to hang at the 20-mins-remaining mark.
At the store, even after we manually turned off WiFi before connecting the Thunderbolt cable, Migration Assistant seemed to turn WiFi back on and start the migration over WiFi.
In the end, we used the Air (source) in Target Disk mode, which forced the computers to use the Thunderbolt cable. Migration took a little over half an hour, as opposed to 12 hours or more that Migration Assistant was saying earlier when apparently trying to use WiFi.

HT201250 I have had my mac stolen, I have an external HD I connect via USB for these time machine backups, I now have a new replacement mac and wish to restore from my external HD, migration assistant doesn't seem to recognise or see my drive ? please hel

I have had my mac stolen, I have an external HD I connect via USB for these time machine backups, I now have a new replacement mac and wish to restore from my external HD, migration assistant doesn't seem to recognise or see my drive ? please help

See Pondini's Excellent information here...
Setting-up a new Mac from an old one, its backups, or a PC
See the Second Chance to Use Setup Assistant here...
http://Pondini.org/OSX/SetupLion.html

Migration assistant does not recognize time machine backup

Hi Guru,
I made a time machine backup today, 10.8.2, then made full reinstall of system in Apple store, in Berkeley, because my iMac experinced some unstability.
we installed new Mac OS, and now I face a problem: migration assistant does not recognize hard disk with buckup.
Finder sees this disk, it has Backups folder.
OS: 10.8.2
BackUp made: Time Machine 10.8.2
Hard Disk: Lacie 500MB
any ideas?
Thank you

I am conserned about restoring using setup assistant because I need to transfer personal files and applications only.
You can do that in Setup Assistant.
Migration Assistant doesn't accept Time Machine backups of the computer it's running on; it only accepts compatible backups of other computers. You can't migrate a system to itself. To restore files from the same computer, enter Time Machine in the usual way, or else boot into Recovery and either restore the whole startup volume or erase, reinstall OS X, and restore in Setup Assistant.

Migration Assistant fails to recognize a Time Machine disk (itself migrated using Disk Utility)

So I outgrow my Time Machine disk. I listen to the advice (repeated in multiple places) that one can simply use Disk Utility's Restore tab, select the old time machine disk as source and the new one as destination, and click restore to copy block-by-block, then rename the disk.
This works very well. I have indeed been able to use Time Machine on the new disk without losing any of the history.
But now I am in trouble. I am also outgrowing my MacBook disk. I put a larger disk in and install Snow Leopard from scratch. Now Migration Assistant does not recognize the new Time Machine disk (perpetually spinning wheel). Renaming the disk to the old name does not help. M.A. does recognize the old Time Machine disk, but that means manually managing the changes (and giving up on the larger TM disk). I reinstall Snow Leopard and do not miss that time the option to restore from Time Machine, but it still does not see the new Time Machine disk.
How does one convince Migration Assistant to use a Time Machine disk that duly has Backups.backupdb as a root folder and where "ignore ownership on this volume" is not set?

Thanks, Pondini, but the Time Machine disk passes the Disk Utility repairs and only the spinning wheel was visible under both the Setup Assistant and the Migration Assistant.
I now have some good news, and some bad.
First the good news: Lion's Migration Assistant offers the option to copy user (and other) files from the previous OSX disk, not just the Time Machine disk. If this option was already in Snow Leopard, then I missed it.
Now the bad news..
I spent several hours reading (Pondini's and others') suggestions to ensure that my Time Machine is as seamless as possible, namely, for the next backup to be incremental. No luck: all user data are copied. Until the interface of Time Machine stops trying so hard to shield us naive users from making decisions on our own, one idea is to keep the iPod and pictures/video collection backed-up by the straight-forward rsync. Then whether Time Machine is really incremental will not matter, and in any case a spare copy of the documents you wrote by hand is nice in case the some blocks of the disk fail.
But I may have been the one who messed it. In Preferrences \ Time Machine \ Options... I excluded all users except the user "Admin" who restored the user accounts. The idea was to test first whether the mildest user will get a full backup. It may be that Time Machine does not look in the history to see if a given file or set of files already have some copy in the past. If a file does not exist in the very last backup, it is saved to the Time Machine disk.
If you're reading this and are keen on an incremental backup, try this: restore your user accounts using a user Admin, but do not start to backup until after the accounts are restored. Will the backup afterwards be incremental?

I have cs5.5 master collection. Replaced my iMac with a new one, used migration assistant, now on the new iMac the apps will not open,

I have cs5.5 master collection. Replaced my iMac with a new one, used migration assistant, now on the new iMac the apps will not open,

I found that out, so used the dvd install disk w the key and tried to install, ran to 87% complete then told me to close,
safari
safarinotificati
i closed safari, still wouldn't finish loading, i closed all safari notifications, nope, can't find any app called safarinotificati
New iMac, 10.10.2, photoshop ran perfectly on my old iMac with 10.10.2
so I cannot complete the loading,
John

ISO x 10.8.3 migration assistant will not recognize time machine disk

I recently had my computer wiped clean by Apple genius bar. After updating the ISO X 10.8 software to 10.8.3, I attempted to restore files from my Time Machine backup to the computer. Unfortunately, the migration assistant would not lock onto the Time Machine disk, as if it were not there. What can I do to restore my original files back into the repaired computer?
My imac was purchased new in December of 2008 and the back up disc was connected to it in Aug 2009. I think the original operating system was pre Snow Leopard - the only CD I have and dated 2010.

I am conserned about restoring using setup assistant because I need to transfer personal files and applications only.
You can do that in Setup Assistant.
Migration Assistant doesn't accept Time Machine backups of the computer it's running on; it only accepts compatible backups of other computers. You can't migrate a system to itself. To restore files from the same computer, enter Time Machine in the usual way, or else boot into Recovery and either restore the whole startup volume or erase, reinstall OS X, and restore in Setup Assistant.

How can I copy programs (iWorks) and files from Time Capsule to my HD manually? The problem is that the migration assistant does not recognize my backup file and the user on the TC. (If I open the TC on finder, it it there though)

How can I copy programs (iWorks) and files from Time Capsule to my HD manually? The problem is that the migration assistant does not recognize my backup file and the user on the TC. (If I open the TC on finder, it it there though)

How can I copy programs (iWorks) and files from Time Capsule to my HD manually? The problem is that the migration assistant does not recognize my backup file and the user on the TC. (If I open the TC on finder, it it there though)

Using migration assistant to setup a new iMac from a TimeCapsule backup?

how do I use migration assistant to setup a new iMac from a TimeCapsule backup

OS X: How to migrate data from another Mac using Mavericks

HT4796 link to migration assistant doesn't work. Where can I find it?

link to migration assistant doesn't work. Where can I find it?

Do you mean the link in the article to Apple Support Downloads? It works for me, now, and should take you here:
If not, try this one: http://support.apple.com/kb/DL1557
Sometimes an Apple server won't find the article you want immediately.

Migration Assistant Won't Recognize External Hard Drive

I have a PowerPC G5 and made a bootable backup of the computer's content to an external firewire hard drive. I tested the backup to make sure that it booted and everything was fine. So, I then did a clean install of Leopard to the machine. After the computer restarted, I reconnected my external drive and it mounted fine. However, when I went to use Migration Assistant to bring over all of my applications, it would not recognize the hard drive as an option to migrate files from.
The hard drive is formatted as Apple Partition Map, and works fine as a bootable copy. Does anyone know why Migration Assistant will not recognize it?
I recently did a clean install of Leopard on my Macbook this weekend using a different external drive with a bootable backup of the drive (GUID formatted) and then used the migration assistant to move all of my files and everything worked just fine.
I can't find any reason that I shouldn't be able to get my applications through migration assistant from the external hard drive but maybe someone knows how to fix this or of a workaround.

Very curious, indeed.
Welcome to the Apple forums where we do try to sort things out
Your delineation of the problem and comparison to your MBP is perfect.
I migrated my G5 from a second internal disk, but actually used the setup assistant when Leopard came alive.
You might see what happens if you eject your external HD and then do what you need to to connect it back (turn off/on - unplug/plug, etc.)
Are there any errors when Migration assistant runs?
It is perhaps that Spotlight is doing its thing and the drive is not available until it is indexed?
I would remove the external HD temporarily from the SpotLight indexing list and then see what happens.
I recall that there were some odd issues with external drives taking up to 1/2 hour to be recognized by Leopard, but I don't recall why.
I am not sure these things will help, but they will eliminate some of the possibilities, and when we have eliminated the probable, what is left is where the answer lies
I wonder if Leopard is confused by the external drive not being GUID?
Try this - - connect the GUID external drive to your G5 and see if Migration assistant sees it. Obviously do not migrate anything, but if you can see that one, we may have a solution.
Keep us posted.

Migration Assistant doesn't recognize old iMac OSX

Similar Messages

Maybe you are looking for