(1) The biggest issue is to ensure that GIT for Windows has a downloaded installer file, 32bit version, sitting in the new computer’s Downloads folder (i.e. download it, but don’t try to install it – Adapt It will do that later, after you have Adapt It downloaded and running (go to the Tools menu, and click ‘Install the Git program…’ and it will open a dialog, navigate to the GIT installer file in the new machine’s Downloads folder, select the installer file, and click OK). Git only has to be installed and integrated once. All new Adapt It downloaded versions will then just use it automatically. (Will GIT 64bit version still work okay with Adapt It? Yes.)

(2) You should also make sure that when you do the setup of Adapt It, you do it as “administrator” permission level. If you install on a ‘standard’ permission level, you will need to know what the administrator password is, so you can supply it when asked – otherwise, on a ‘standard’ account, Adapt It will not install. On an administrator account, you’ll have no problem getting the install done, and with connecting the stored GIT installer file to link in to Adapt It. (Adapt It uses that for the File menu’s command “Save and remember in history”) If GIT does not get integrated, that command will not work; but Adapt It will continue to work for everything else. You can download GIT’s windows installer from: https://git-scm.com/download/win/

(3) On your new machine, get issues (1) and (2) above, sorted out. Get your GIT download, but don’t install it. Get the latest Adapt It, if you’ve not already done so, and install.
Now, get Adapt It running. You’ll see the Welcome window, and a message (which you should ignore) that configuration files are not available. Click that warning away. Then close Adapt It. That will create new configuration files, and you’ll have Adapt It’s internal folders all set up – though empty, and the Adapt It Unicode Work folder will be set up too. At this point you are ready to copy over your projects from the faulty machine.

(4) Use Windows Explorer, and a usb memory stick or similar movable storage device. Do these steps:
On the faulty machine:
a) Insert the memory device, in Explorer navigate to the Adapt It Unicode Work folder, select and copy ALL the files and folders, and paste them into a folder of any name (but empty of course) on the memory device.
b) safely remove the memory device.
On the new machine:
c) Insert the memory device, in Explorer navigate to the Adapt It Unicode work folder, clear out it’s contents to make it empty.
d) Navigate to the memory device, open the folder where you copied all the files etc. from the faulty machine at a), select ALL of them, and copy them.
e) Navigate to the empty Adapt It Unicode Work folder, and paste all the files into it.

(4) Run Adapt It on the new machine. Check that you can open every project, and open a file in each project. If that works, your configuration files copied from the faulty machine are being accepted by the new machine, even if some file or folder paths are not identical – Adapt It will try to adjust them to make them correct without you asking it to.
If you find that you get an error report saying Adapt It can’t open a configuration file then do the following:
Run Adapt It, holding down the SHIFT key, (this causes the configuration files to be skipped while you hold down the SHIFT key), and keep it held down until you get just one project open, and you have opened just one document file in that project.
At that point, shut down Adapt It – this causes the project configuration file and the basic configuration file to be renewed, and stored with correct paths on the new machine. But you will have lost various settings, they will have been replaced by default values – so you’ll need to do Edit > Preferences… and set up your wanted fonts, sizes, colours, punctuation settings, and so forth. Once you’ve done that, close Adapt It again, and reopen, without holding SHIFT down. From that point you should have no problems – except that other copied projects which are not that particular one, will need to have their project settings updated too. When all that is done, you’ve finished.

Moving projects to a new machine