Unfortunately, the old procedure I developed for moving the database doesn't quite work properly in build 1533 of the server, which is the 2.0.1 version; unfortunately there's a small bug I introduced that stops the process server importing the database password information properly.
I've written a script that automates the database backup/restore process for GSS1.1 and GSS2.0 which you can get by registering with a Google account at
http://groups.google.com/group/gss-scripts - the database backup/restore scripts can be used to easily move servers as well.
As for the ODBC drivers, actually they are probably present and working fine on the 64-bit system, it's just you can't see them in the ODBC control panel. One of the peculiarities of 64-bit Windows is that 64-bit programs can't use 32-bit DLLs or vice versa; ODBC drivers are DLLs, and so for our (32-bit) executable we install 32-bit ODBC drivers.
However, the ODBC control applet (odbcad32.exe) is a 64-bit program on 64-bit Windows, and is completely unaware of the 32-bit ODBC system. It doesn't know the 32-bit drivers or any 32-bit data sources exist. To work with ODBC on a 64-bit windows system, you have to know to manually run the 32-bit ODBC control panel applet, which doesn't have a shortcut anywhere.
To run the 32-bit ODBC applet, use Run from the start menu and use this as the file name:
%WINDIR%\SysWOW64\odbcad32.exe
That should let you see the providers which have 32-bit drivers installed, and any data sources defined for them.