Overview
We recommend installing Hybrid OSTO after the Live Migration. If installation is required during the Test Migration, ensure that the following steps are performed during the Live Migration itself.
When Do I Need to Follow These Steps?
⚠️Important: Only follow this procedure if the customer set up Hybrid OSTO during Test Migration. If the customer does not use Hybrid OSTO, skip this section entirely — it does not apply.
To check, look at the OSTO database for the customer. If the table ConQuestOstoUserSqlLogin has any rows, the customer has Hybrid OSTO credentials that need to be preserved.
Why Do I Need to Do This?
When the customer's OSTO database is deleted during Live Migration and a fresh one is restored, the customer's OSTO connection credentials are lost. Without this procedure, the customer's local OSTO application will stop connecting and will need to be manually reconfigured.
By saving the credentials before the migration and restoring them afterwards, the customer does not need to take any action, everything continues to work as before.
Preparing the Script Files
Obtain the two script files: Save-OstoCredentials.ps1 and Restore-OstoCredentials.ps1.
Copy both files onto the DC2 server into the following folder (create it if it does not already exist):
📌Note: We use C:\temp\ because that is the same location the standard migration already downloads its files to.
Open PowerShell with administrator privileges, then run the following command and press Enter:
This navigates to the folder where the two scripts were copied. Once inside the OstoScripts directory, you are ready to run the required commands.
Migration Procedure
Step 1 - Save the Credentials
When: Before you delete the OSTO database. Do this as the very first step.
Open PowerShell and run:
📌Note: Replace CustomerName_OSTO with the actual OSTO database name for the customer.
What to expect: The script creates a file in C:\temp\OstoBackup\. You should see a success message. If you see an error, do not proceed - contact the development team.
Step 2 - Perform the Live Migration
Follow the standard Live Migration process. Nothing changes here; complete every step exactly as you normally would.
Step 3 - Restore the Credentials
When: Right after Update.ps1 finishes, and before the customer opens ConQuest.
Open PowerShell and run:
📌Note: Replace CustomerName_OSTO with the actual OSTO database name for the customer.
What to expect: The script reports how many credentials were restored. If you see an error, contact the development team.
Step 4 - Wait
The system automatically finishes setting things up in the background. This can take up to 30 minutes. No action is needed from you.
Step 5 - Clean Up
Delete the backup file — it contains sensitive information:
Step 6 - Notify the Customer
Let the customer know that Live Migration is complete. They do NOT need to change any OSTO settings — everything will continue to work as before.
If You Forgot to Save Before Deleting the Database
⚠️Warning: The old credentials are gone and cannot be recovered.
In this case:
Let the customer know they need to regenerate their OSTO credentials.
They can do this from ConQuest Q-Series: Options → On-Screen TakeOff → select “On another Server or user's PC”.
After the new credentials appear (this may take up to 30 minutes), they need to update their local OSTO configuration file (DatabaseSettings.xml) with the new SQL User and Password.
The configuration file location can be found in the Application Discovery Configuration Folder Guide on the ConQuest wiki.
⚠️Important: These steps are only needed if the customer installed Hybrid OSTO during Test Migration.