Upgrading Macbook, fresh install queries.

[snerkler]

I currently have a 2017 Touchbar Macbook Pro and will be upgrading to the new M1 Macbook Pro. I was initially going to install a time machine backup onto the new Macbook so that it was a carbon copy of my current one, but have been advised a fresh install is better.

Over the years I've added software, plugins, and files and if I'm honest I don't know exactly where all the files and extensions have gone as as softwares have updated the program files have gone into different locations, in particular lightroom presets and profiles, as well as Logic Pro 3rd party plugins.

Will the library structure of the new MBP be the same as my current one and therefore allowing me to essentially drag and drop files into the same locations within the libraries? Currently my MBP has two libraries (I'm not sure why), one that I can access from the "go" menu in finder by pressing the option key. The second library is accessed by going into "Macintosh HD". There appears to be a lot of duplicate folders in each library but some files go into one, and some into the other.

Lastly, if I can just drag and drop like I want to is it possible to plug the old MBP into the old one and swap from one to the other, or do I need to plug in the time machine drive and find the files within that?

Any help would be appreciated.

 

[Fishrrman]

You haven't told us WHICH VERSION of the OS you're using on the 2017 MBP.
Chances are, the "library structures" may have changed a bit.

If you are determined to "do this by hand", then a cloned backup would suit you better than a time machine backup. You can create one with either CarbonCopyCloner or SuperDuper -- both are free to download and use for 30 days.

REASON WHY: The cloned backup can be mounted directly in the finder, and files copied from it as they would be from any other drive.

But it's going to be A LOT of work and you'd better keep detailed handwritten notes as you go along.

There could be permissions problems as well, so you need to mount the cloned backup and put a check into "ignore ownership on this volume" (as seen at the bottom of the "get info" box for the drive). After doing this, almost anything you copy from the backup drive will "come under the ownership" of your new account on the new MBP.

Perhaps you ought to give reconsideration to using setup assistant during the initial setup of the new MPB. And if you do, I'd still recommend using a CCC cloned backup rather than a tm backup as your "source drive").

 

[snerkler]

You haven't told us WHICH VERSION of the OS you're using on the 2017 MBP.
Chances are, the "library structures" may have changed a bit.

If you are determined to "do this by hand", then a cloned backup would suit you better than a time machine backup. You can create one with either CarbonCopyCloner or SuperDuper -- both are free to download and use for 30 days.

REASON WHY: The cloned backup can be mounted directly in the finder, and files copied from it as they would be from any other drive.

But it's going to be A LOT of work and you'd better keep detailed handwritten notes as you go along.

There could be permissions problems as well, so you need to mount the cloned backup and put a check into "ignore ownership on this volume" (as seen at the bottom of the "get info" box for the drive). After doing this, almost anything you copy from the backup drive will "come under the ownership" of your new account on the new MBP.

Perhaps you ought to give reconsideration to using setup assistant during the initial setup of the new MPB. And if you do, I'd still recommend using a CCC cloned backup rather than a tm backup as your "source drive").

Thanks very much for your reply. Currently I have Catalina, however if required I can update to Monterey once the Logic Pro X plug ins that I use are updated. There's a bit of a wait on MBP's in the UK at the moment so I'm hoping that most software will have been updated by then.

I'm not determined to do it by hand at all, and I'd rather just install the latest time machine backup from my old computer onto the new one but I was told this is not the best way to do things? I've never used setup assistant other than reinstalling time machine backups. What's the reason the cloned drive is better than TM?

 

[InnerSongs]

I have this same issue/concern, also upgrading 2017 to new MBP M1 Pro.
My OS was, and is Monterey.
Upgraded to Big Sur on my 2017 and everything worked fine. Worked fine under Monterey after upgrade.
As most know however, the LR installer, being 32 bit, brone under Big Sur.
I did a CCC to the new M1 Pro and LR is now broken And I can’t reinstall.

What migration method can I use to transfer a functioning LR to my new machine that won’t make it FUBAR.
As ‘snerkler’ more or less asked, can it be moved in pieces?
I have a ™ backup of my 2017, but was advised to Use CCC, and not a migration with or without TM.
If CCC is a true clone, why should it break?
My only thoughts are that the LR install keeps a reference to the Mac’s hardware name or ID,
OR the code in Rosetta 2 screwed the pooch.
Keep me informed ‘snerkler’ as to what you learn.
Thanks to all.

 

[snerkler]

I have this same issue/concern, also upgrading 2017 to new MBP M1 Pro.
My OS was, and is Monterey.
Upgraded to Big Sur on my 2017 and everything worked fine. Worked fine under Monterey after upgrade.
As most know however, the LR installer, being 32 bit, brone under Big Sur.
I did a CCC to the new M1 Pro and LR is now broken And I can’t reinstall.

What migration method can I use to transfer a functioning LR to my new machine that won’t make it FUBAR.
As ‘snerkler’ more or less asked, can it be moved in pieces?
I have a ™ backup of my 2017, but was advised to Use CCC, and not a migration with or without TM.
If CCC is a true clone, why should it break?
My only thoughts are that the LR install keeps a reference to the Mac’s hardware name or ID,
OR the code in Rosetta 2 screwed the pooch.
Keep me informed ‘snerkler’ as to what you learn.
Thanks to all.

I haven't got my MBP yet, but will. update as and when (couple of weeks or so). When you say LR doesn't work I assume you mean Adobe Lightroom?

 

[InnerSongs]

I haven't got my MBP yet, but will. update as and when (couple of weeks or so). When you say LR doesn't work I assume you mean Adobe Lightroom?

Yes, Lightroom. Thanks. I only have a couple more days before I have to return my 2017 for credit so using Migration Assistant options are diminishing. I have LR working on my Monterey iMac so all is not lost, but using Lightroom with clients and while 'in the bush' is the need.

 

[snerkler]

Yes, Lightroom. Thanks. I only have a couple more days before I have to return my 2017 for credit so using Migration Assistant options are diminishing. I have LR working on my Monterey iMac so all is not lost, but using Lightroom with clients and while 'in the bush' is the need.

That's not good. Why won't it let you reinstall LR?

 

[InnerSongs]

That's not good. Why won't it let you reinstall LR?

32 bIt applications will not install under Big Sur or newer MacOS (Monterey) ~ (?) Apple asked App publishers to update their software to support the 64 bit code of the MacOS. Adobe declined and the installer is 32 bit. As I perceive it they want to push everyone to Lightroom Cloud and to subscribe with a monthly fee. If it needs to be reinstalled apparently one is screwed.
Someone please Correct me if I’m wrong, but Apple’s Rosetta 2 otherwise allows 32 bit Lightroom code to function inside of a sandbox within the 64 bit environment of Monterey. It’s fuzzy to me why the installer can’t perform but the App can. I’m out of my depth here a bit, maybe someone else can fill in the gaps better.

 

[snerkler]

32 bIt applications will not install under Big Sur or newer MacOS (Monterey) ~ (?) Apple asked App publishers to update their software to support the 64 bit code of the MacOS. Adobe declined and the installer is 32 bit. As I perceive it they want to push everyone to Lightroom Cloud and to subscribe with a monthly fee. If it needs to be reinstalled apparently one is screwed.
Someone please Correct me if I’m wrong, but Apple’s Rosetta 2 otherwise allows 32 bit Lightroom code to function inside of a sandbox within the 64 bit environment of Monterey. It’s fuzzy to me why the installer can’t perform but the App can. I’m out of my depth here a bit, maybe someone else can fill in the gaps better.

Ahh right, that's pants. I'm on CC though so should be OK.