Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

iproductsuser

macrumors 6502a
Original poster
Apr 13, 2012
538
0
I have an old 2008 MBP running Mountain Lion. Works perfect. I bought a brand new 2012 MBP that came running Lion. I used migration assistant to transfer my 160GB of data - it took 2 days but ok it worked without errors. Now with that being said, on my new MBP, I cannot open iPhoto, Mail, Safari and there are probably more. What's the problem?

I downloaded ML in the app store via my purchases and have started the install this morning when I left for work. Think the upgrade to ML will alleviate the issues I was having? Could it be that those specific apps require ML files since they were migrated from ML?

If you don't think that will work, what's my best bet to ensure I get all of my information, media, data, safari bookmarks, passwords etc to my new MBP?

I am slated to sell my old MBP tomorrow locally and would like to get this sorted out b/c i'll be wiping my old MBP clean before I sell it but would hate to lose any info.

Thanks in advance to the experts
 

MagicBoy

macrumors 68040
May 28, 2006
3,968
1,058
Manchester, UK
Mountain Lion to Lion is a downgrade and not a supported migration path. The internal database formats behind the scenes for the bundled applications will likely have been changed rendering them incompatible with Lion.

The ML upgrade should fix it.
 

iproductsuser

macrumors 6502a
Original poster
Apr 13, 2012
538
0
Mountain Lion to Lion is a downgrade and not a supported migration path. The internal database formats behind the scenes for the bundled applications will likely have been changed rendering them incompatible with Lion.

The ML upgrade should fix it.

Is there something that says for sure this is not a supported migration path? I'm crossing my fingers you're right and hoping it will be good to go when I get home from work. Your logic makes sense and that's what my thought path told me regarding files behind the scenes. It mentioned frameworks in the error report so that was my logic. Thanks for your input.
 

danb77

macrumors 6502
Sep 4, 2007
442
3
IF you still have your old computer, it'd probably be best if you clean install Mountain Lion on your new computer and then redo the Migration from scratch.

I am puzzled that M Assistant even allowed a Migration from ML to L.
 

iproductsuser

macrumors 6502a
Original poster
Apr 13, 2012
538
0
The upgrade to ML fixed everything. I have just went through all of my applications, documents etc and it is exactly as is was on my old MBP.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.