Paul Patruno

I've moved your post away from the community help forum, which is for help about the community platform itself, and into the Trados Studio forum.

On your post... first of all Trados Studio 2022 can run alongside 2021, so it is independent and does not share the same resources.  Plugins for 2021 won't even work in 2022 for example!

Paul Patruno said:

After the upgrade all my projects are no longer in the project list.

In practice I would recommend you complete your projects in 2021 and only start new projects in 2022.  You can easily retain 2021 and carry on working with it even though you have 2022 available to you.  However, you can also bring in the 2021 projects just by using the Open Project command in your ribbon and select the sdlproj file for the project you wish to work on.  If you wanted all of your old projects in your list as well... well ten I'm afraid you'll have to open them all one by one. But I wouldn't really recommend this as they will all be using project settings that have been updated and you may start introducing problems for yourself especially if you add files to these older projects in 2022.

But it's not a difficult process.

Paul Patruno said:

All my Add-ins are gone

As I explained, add-ons (plugins) from 2021 will not work for 2022.  However, using the integrated appstore is a trivial exercise and you can reinstall install many apps in a minute or two.  If you don't know where this is look here:

Paul Patruno said:

Do I have to reinstall everything?

I guess you mean apps... and the answer is yes.  There were a lot of changes in 2022 that have meant all app developers have to upgrade their plugins.  Trust me this is not something we do on purpose.  My team has over a 100 apps we support and the number is growing so having to do this is a painful process and not something we enforce just to force users to do something they might think we do on purpose!  We also had to upgrade all the 2021 apps first to make sure they could not be installed into 2022 as this will not work... so a tremendous amount of work.

Paul Patruno said:

Why is it that Studio Migration Utility is NOT yet setup for Studio 2022?

First of all I think it's worth noting this app isn't really useful at all!  It's far easier to do this manually because there is no quick solution to this.  Anything of real value won't work as I have note above, so it's better for you to understand how your software works.  If you have any questions at all on how this works please do ask in here ad we'll be happy to help you.

I started the project for this migration tool a log time ago to try and engage developers to contribute on something together.  Sadly it failed and we ended up doing all the work.  So after a few years it's pretty much stagnated and I'd have to say I have never even installed it for many years because the process of upgrading is actually really simple and not difficult at all.  There are also many new features today that support the transferability of things used in the past that were difficult to get at.  So the relevance of the migration tool has become less and less.  If you're interested you can read about that project idea here

http://multifarious.filkin.com/2015/07/06/walhfmf/

In my opinion we need to introduce something into the Studio installation process itself that looks to see if there was an earlier version of Studio installed and if there was offer to move over anything that is possible.  It should not need a separate tool.  But that's another story!

Paul Patruno

I've moved your post away from the community help forum, which is for help about the community platform itself, and into the Trados Studio forum.

On your post... first of all Trados Studio 2022 can run alongside 2021, so it is independent and does not share the same resources.  Plugins for 2021 won't even work in 2022 for example!

Paul Patruno said:

After the upgrade all my projects are no longer in the project list.

In practice I would recommend you complete your projects in 2021 and only start new projects in 2022.  You can easily retain 2021 and carry on working with it even though you have 2022 available to you.  However, you can also bring in the 2021 projects just by using the Open Project command in your ribbon and select the sdlproj file for the project you wish to work on.  If you wanted all of your old projects in your list as well... well ten I'm afraid you'll have to open them all one by one. But I wouldn't really recommend this as they will all be using project settings that have been updated and you may start introducing problems for yourself especially if you add files to these older projects in 2022.

But it's not a difficult process.

Paul Patruno said:

All my Add-ins are gone

As I explained, add-ons (plugins) from 2021 will not work for 2022.  However, using the integrated appstore is a trivial exercise and you can reinstall install many apps in a minute or two.  If you don't know where this is look here:

Paul Patruno said:

Do I have to reinstall everything?

I guess you mean apps... and the answer is yes.  There were a lot of changes in 2022 that have meant all app developers have to upgrade their plugins.  Trust me this is not something we do on purpose.  My team has over a 100 apps we support and the number is growing so having to do this is a painful process and not something we enforce just to force users to do something they might think we do on purpose!  We also had to upgrade all the 2021 apps first to make sure they could not be installed into 2022 as this will not work... so a tremendous amount of work.

Paul Patruno said:

Why is it that Studio Migration Utility is NOT yet setup for Studio 2022?

First of all I think it's worth noting this app isn't really useful at all!  It's far easier to do this manually because there is no quick solution to this.  Anything of real value won't work as I have note above, so it's better for you to understand how your software works.  If you have any questions at all on how this works please do ask in here ad we'll be happy to help you.

I started the project for this migration tool a log time ago to try and engage developers to contribute on something together.  Sadly it failed and we ended up doing all the work.  So after a few years it's pretty much stagnated and I'd have to say I have never even installed it for many years because the process of upgrading is actually really simple and not difficult at all.  There are also many new features today that support the transferability of things used in the past that were difficult to get at.  So the relevance of the migration tool has become less and less.  If you're interested you can read about that project idea here

http://multifarious.filkin.com/2015/07/06/walhfmf/

In my opinion we need to introduce something into the Studio installation process itself that looks to see if there was an earlier version of Studio installed and if there was offer to move over anything that is possible.  It should not need a separate tool.  But that's another story!