I’ve just transferred SDL Trados Studio 2014 onto a brand new work machine. If you’re also planning on retiring your old computer and setting up a new one, I hope you’ll find these instructions useful. I decided to leave Studio 2009 and 2011 behind, but you can follow these steps to transfer them too.
1. Download and install Studio on your new computer
Go to www.translationzone.com > My Account > My Downloads and download Multiterm Desktop and Studio. Install both of them. Run Studio and when you’re asked to activate it, just keep it in the 30-day Demo mode for the time being. Don’t run Multiterm until you’ve activated your license (see the end of this post).
The downloaded version of Studio doesn’t include any Cumulative Updates, so it’s important to go straight to Help > Check for Updates and follow the instructions there.
Now go back to your old computer.
2. Export your user profile
Your user profile contains customised shortcuts, window layout, default languages and everything else that you’ve defined under General Options.
To export your profile in Studio 2014, go to File > Setup > Manage User Profiles > Export user settings and follow the wizard to export your settings onto a pendrive or other device. (In Studio 2011 go to Tools > Manage User Profiles > Export User Settings).
Now import your saved user profile in your new computer using the “Change user profile” wizard in the same location. You can also import it earlier on when you’re running Studio for the first time.
3. Copy your data
You’ll want to transfer all your translation memories, autosuggest dictionaries and termbases. Hopefully you know where you save all these resources, so they’ll be easy to find and copy onto your pendrive.
To move the custom dictionary (where you add words to the spell checker), make sure you know which dictionary you’re using by going to File (or Tools in Studio 2011) > Options > Editor > Spelling.
- If you use the Hunspell Spell Checker, copy your custom dictionary from C :\Users\[Username]\App Data\Roaming\SDL\SpellChecker\CUSTOM.dic and transfer it to the same path in your new machine.
- If you use the MS Word Spell Checker, copy your custom dictionary from C:\Users\[Username]\AppData\Roaming\Microsoft\UProof and transfer it to the same path in your new machine.
In the case of AutoText, export the lists you’ve created for each language by going to File (or Tools in Studio 2011) > Options > AutoSuggest > AutoText and follow the export wizard.
Now import the AutoText in your new computer and copy all your data.
You can copy and recreate Studio projects in your new machine by copying the project folders and the .sdlproj file, but make sure you reproduce exactly the same paths for all the resources that are in each project. If Studio can’t find a certain TM because the path has changed, it’ll make a fuss every time it opens and that can be awkward to sort out. I decided to start my projects from scratch on my new computer.
5. Open Exchange apps
I must admit I didn’t realise how time consuming this part would be. Open Exchange apps have to be installed on your new machine one by one. For my fresh installation, I decided to download all the apps again from the Open Exchange to make sure I was using the latest versions.
If you prefer, you could copy the plug-ins (the apps that run inside Studio) from their old file path to the same path on your new machine. You’ll find them in two different places:
C:\Users\[Username]\AppData\Local\SDL\SDL Trados Studio\11\Plugins\Packages
C:\Users\[Username]\AppData\Roaming\SDL\SDL Trados Studio\11\Plugins\Packages
[If you’re transferring Studio 2015 to a new machine, replace “11” with “12” in the file path.]
In the case of standalone apps, and if you’ve still got the .exe or .msi files in the Downloads folder on your old machine, you could copy them and install them on the new one.
Note: the list of apps in the “My apps” section of “My Account” on the SDL website isn’t at all useful. Most of the links to “more information” are broken and the download buttons only give you the version you originally downloaded. Also, some apps can only be downloaded from an external site and so they won’t be in the list at all.
Regex Match AutoSuggest Provider
If you use this OpenExchange app, don’t forget to copy the variables and settings .xml files from here on your old machine:
to the same place on your new machine after you’ve re-installed the app.
If you’ve paid for any apps you’ll have the extra job of re-activating the license. AnyTM is an example of one of these. It has a single-user, single-activation license, which means you have to contact the developer to ask for the license to be reset. Erik de Vrieze at CodingBreeze (the AnyTm developer) reset my license immediately. He agrees that single activation isn’t very satisfactory and is looking into a system of automatic online activation that would check that the license isn’t in use on any other machine. That sounds promising.
To finish off this app palaver, I recommend installing Menu Maker to get all your apps organised once and for all.
Edited to add: In Studio 2014, AnyTM is now a free app. In Studio 2015, it actually comes bundled with the core product, so you don’t even have to download it.
6. Return your Studio license
Most people know that this is an essential step before you finally retire your old computer. When you’re sure that you’ve got Studio running smoothly on your new computer, the last step is to return your license on the old one. Open Studio for one last time on your old computer and go to Help > Product Activation > Deactivate. That returns your license to SDL.
Now activate the license on your new computer.
Note: Later, if you want to check something on your old machine and haven’t got the Freelance Plus version, simply deactivate the license temporarily on the new one and activate it again on the old one.
Note: Since Studio 2014 SP2, Studio is no longer Java dependent. The paragraph below now only applies to pre-2014 SP2 versions:
I hardly dare mention The Java Issue because it causes so many problems, but I’d like to quickly touch on my experience of Java on a new machine. The first time I tried to add a term to my term base in Studio I just got a blank window. I tried all sorts of solutions. Finally, I realised that Java had automatically installed its 64-bit version (build 51) to match my 64-bit OS. I uninstalled it and installed it again, selecting the 32-bit version. Problem solved.
Getting Studio up and running on a new machine takes time and careful planning, but it’s definitely worth the effort. My new Lenovo Thinkpad S440 with its Haswell processor and SSD is lightning fast. It starts Studio, prepares projects, looks up segments in big TMs and autopropagates numbers in next to no time. I don’t even have an excuse to get up and make myself a coffee any more.
The above instructions worked for me but they may not work for you because computer set ups vary hugely. Follow the instructions at your own risk.
Where to go for more help
- You’re entitled to free help on installation and licensing issues, even if you don’t have a support contract. To contact SDL, go to the Solution Finder and troubleshoot your problem or log a support request.
- For more solutions to Studio-related Java issues, I recommend Shai Nave’s excellent blog post on this subject.