1: Transitioning from HyperLaunch v3.1 to RocketLauncher

Download the Transition Tool [RL_Transition_Tool.rar]
Extract the transition tool to any folder. This must not be in your HyperLaunch or HyperLaunchHQ folder or any sub-folder in them, as these folders will be renamed. Your Downloads folder works fine.
Run the Transition tool and you will be presented with this:

Either type in your HyperLaunch path or click the little . button and use the folder browser to select it.

You will be presented with some verification prompts to acknowledge what is taking place. Depending on your choices, you may also be presented with some additional checks to point to other folders. This is just to make sure the transition is accurate.
Upon completion, the tool will let you know what was updated and exit on its own.
If you did not run it directly from the archive, you can find a log in the same folder the tool was ran from of all the files/settings updated.

2: Extract the update pack

Download the Update pack: [RL_Transition_Update_Pack.rar]
Extract it into your folder you are running RocketLauncher from (C:\RocketLauncher or D:\RocketLauncher are recommended)
Be sure the RocketLauncher.exe is in the root of this folder.
RocketLauncherUI folder does not need to be in the RocketLauncher folder, but if the old HyperLaunchHQ was there before, keep it there so the transition is seamless and relative folders still work.
You should have a structure like this (using C: as the example drive):

C:\RocketLauncher\RocketLauncher.exe

C:\RocketLauncher\RocketLauncherUI\RocketLauncherUI.exe

C:\RocketLauncher\RocketLauncherUI\RocketLauncherUI.exe.config

Make sure all the other files in the archive kept their folder structure as well.
Now run RocketLauncherUI.exe and you will be presented with a prompt that updates were found. So go ahead and update!

You can now uninstall GIT if you were using it prior for HyperLaunch3. It is no longer used or being updated.
That's it, you are now using RocketLauncher! Enjoy!

This step is not needed if you agreed to do it on Step 1.
Hyperspin versions prior to 1.4 were never designed to work with other launchers, so it only looks for HyperLaunch.exe when you have Hyperlaunch enabled in HyperHQ. Part of the v1.4 Hyperspin update now requires the full path to your Hyperlaunch executable, which means you can divert it to another launcher (aka RocketLauncher.exe).
The Transition tool will automatically update this path for you if you select yes when it asks if you use Hyperspin as your front end.
If you selected No on that step, you can open the Transition tool again and simply click the Convert Hyperspin button: