Upgrading 2012LT, what happens to my custom toolbars & commands etc?

[rhoscadman]

Hi Folks,

We have just been sent a round-robin e-mail from the boss saying that now there is an upgrade available to the 2012Lt we're using (to 2013LT). On this e-mail there's a link saying "download now" or similar. I'm worried about all the custom commands (macros) I've created, icons, workspace arrangement, custom toolbars, custom toolpalettes etc. What shall I do with them to make sure I can import them to the upgrade? I really get confused with the "transfer" feature in the cui page. Transfer what? From where?

Can someone point me in the right direction please, I really don't want to spend a whole afternoon copying and pasting macros, icons and tool palettes.

Thanks

Rob

[Charles_Shade]

I've used Migrate in the past with great success. The Guru here is not as warm to doing this.

Download the Trial and see if a Migrate works for you. This will not change your current setup or do it on one of your colleagues machines if you want someone to be the guinnea pig.

Best would be to work thru the Transfer Tab of the CUI and understand that.

Transfer is from the previous CUI file to the new CUI of the current program.

It is fairly inutuitive albeit unwieldy in terms of moving from one version to the other.

My own experiecnce going from LT 2011 to LT 2012 using Migrate was flawless.

The only thing that changed was the name of the program in the Menubar.

This was the first time there was not a week of setting up the program the way I wanted.

[pendean]

Migration works for most, fails for a few: recognizing when it fails and knowing how to put everything back manually is still a rational skill to have.

All customizations need to be documented, organized, and regularly backed up: whether you upgrade automatically or manually, if you are not familiar with your own customizations' structure you always risk a chance of misplacing things that stop working.

[Charles_Shade]

Yes, you taught me that lesson several years ago about having these customizations stored and referenced by CAD in the proper way.

Like going to the bottom of the PAT file if you want to add a Hatch there instead of in its own file...