Hello Andrew,

Unknown said:

Can I simply drag and drop them into the TM folder in Studio 2017, and then add them from there into projects in 2017?

You can drag and drop them to any location you like!  In fact if you want to avoid migration every time there is a major release you could keep your Translation Memories in a location of your choosing.  There is no need to use the defaults at all.

Unknown said:

Or is it a case of just adding them to the TM view in Studio 2017, and then it will identify the path?

The TM View is purely for Maintenance.  You can add them there if you like but this has no effect at all on how Studio sees them in projects.

Unknown said:

Or is it better to export them and then import into new TMs created in 2017?

There is no need to do this at all.  You should do two things though as there has been a few changes since Studio 2011 that you can benefit from in Studio 2017.  Here's what I'd do:

1. Copy all your TMs to a new folder of your choosing.  Somewhere you back up regularly.
2. Keep a copy of these TMs somewhere else and then upgrade the originals with two processes:
   1. Reindex them to take advantage of the changes in tokenization
   2. Prepare them for upLift

There is a tool on the appstore to help with this if you have a lot of TMs:

https://multifarious.filkin.com/2016/11/17/more-power-to-the-elbow-uplift/

But if you only have a few I'd just do them manually.

Regards

Paul

Hello Andrew,

Unknown said:

Can I simply drag and drop them into the TM folder in Studio 2017, and then add them from there into projects in 2017?

You can drag and drop them to any location you like!  In fact if you want to avoid migration every time there is a major release you could keep your Translation Memories in a location of your choosing.  There is no need to use the defaults at all.

Unknown said:

Or is it a case of just adding them to the TM view in Studio 2017, and then it will identify the path?

The TM View is purely for Maintenance.  You can add them there if you like but this has no effect at all on how Studio sees them in projects.

Unknown said:

Or is it better to export them and then import into new TMs created in 2017?

There is no need to do this at all.  You should do two things though as there has been a few changes since Studio 2011 that you can benefit from in Studio 2017.  Here's what I'd do:

1. Copy all your TMs to a new folder of your choosing.  Somewhere you back up regularly.
2. Keep a copy of these TMs somewhere else and then upgrade the originals with two processes:
   1. Reindex them to take advantage of the changes in tokenization
   2. Prepare them for upLift

There is a tool on the appstore to help with this if you have a lot of TMs:

https://multifarious.filkin.com/2016/11/17/more-power-to-the-elbow-uplift/

But if you only have a few I'd just do them manually.

Regards

Paul