Hi Michael
the easiest way will be to re-create on the new SSD EXACTLY the same paths to the projects and all your resources (TMs, etc.) as you have on the laptop. This way, the projects.xml file in folder MyDocuments\Studio 201x\Projects will always point to the same relative path.
By default, Studio puts all this in folder MyDocuments\Studio 201x\, then Projects, Translation Memories, etc.
In my case, all my projects, TMs and other Studio resources are in my own folder structure, created directly from the root of my drive. This means they don't need migrating when a new version of Studio comes out (e.g. 2015 to 2017).
Whichever method you use, you will be able to copy files from one PC to the other (TMs, the folder for the actual project, etc.).
Simon

Hi Michael,

You do not have to create projects in both locations.  Just copy the projects across and then update them to keep it in synch.  The idea Simon suggested was that you create exactly the same structure on both computers and then you only need to copy the SDLXLIFF files in the target language folder and your TMs and Termbases to overwrite the older ones.  So in this example I copy across the project called "multilingual_TMX" from my Desktop Studio projects folder into the exact same folder in the same location on my laptop:

You do a similar thing with your Translation memories and your Termbases.  This way the *.sdlproj files which hold information about where to find all these files on a project will have no problems because the paths it uses to locate the file will be exactly the same on each machine.

Once you have done this you can keep them upto date by either just replacing the sdlxliff files in your target language folder from one machine to another, and also your Translation Memories and Termbases, or you can simply back up your entire Projects structure and other resources each time you finish work in one and need to go back to the other.

You could also play with using dropbox as the location for your projects, Translation Memories and Termbases.  If it's only you working this might be a sensible way forward as this way both machines will be permanently in synch once your dropbox has updated.  The one downside of this is if your TMs are huge because dropbox will be forever synching huge files and this might cause you some performance issues. But the way around this is to use Project TMs and this way they will always be small and you just update your Main TMs at the end of each job.

Hope that seems clear... and will welcome other ideas on how others work with their projects when they operate between more than one computer.

Regards

Paul