Database migration is where we assist in taking your HoleBASE database and turn this into an OpenGround compatible database. This is then transferred over to the Cloud and made accessible to you through the OpenGround Cloud Launcher.
Please note that this process is only for HoleBASE users migrating to OpenGround. This process is not currently available for gINT users.
Essentially the process is that we will ask you to backup your current HoleBASE database, then upload it to somewhere we can download them so we can then do the migration (we can provide a FTP link if needed). We then restore and test the database, migrate it, test the Cloud database and then give you access. The process from downloading the database, to giving you access normally takes between 2-48 hours, with the majority being done within the day. We would therefore suggest, you instruct your users to not edit data in the desktop database after producing the database backup (we will not take away your desktop access, but any data that changes will need to be managed and then handled with the data that has been migrated to cloud).
The above image shows the steps required in the migration process and is explained in detail below;
Agree Date
The first step is to agree a date when the migration should happen. With some notice, the OpenGround team can usually try and negate the amount of downtime needed by planning around your organisations needs but please note that all manual processes may need to be done during working hours. It is also important at this stage to ensure that the correct user has been noted as the OpenGround Administrator.
Backup
The next step, on the date agreed, is for a backup of the HoleBASE database to be undertaken. Note that there are 4 databases for HoleBASE that will be on the same server. Full instructions for how to backup the database can be found here;
If multiple databases are to be merged together (ie, moving multiple offices' HoleBASE databases into one OpenGround instance), then a copy of all of these databases will be required at the same time.
Upload
The HoleBASE database backup will then need to be uploaded to somewhere that a member of our team can then download them from. If your organisation has facility to do this, then we will be more than happy to work with you to use that service. However, if this isnt possible, then we can arrange for a temporary secure link for you to upload your database to. Depending on the size of your database, we will probably offer a Sharepoint location for this.
Download
This is where the OpenGround team will take over and start to process the database. In this step, they will download the database from the location provided in the previous step.
Restore and Testing
In this step, the OpenGround team will restore the database and connect through to it using HoleBASE. This is to ensure that a valid database has been sent through and that there are no issues before attempting to do the database migration.
Processing
In this step, the OpenGround team will run a series of automated tools to 'Cloudify' the HoleBASE database and get it ready to be used online.
Upload
In this step, the OpenGround team will arrange for a secure transfer of the converted database to the secure Azure servers that the backend OpenGround services run on.
Creation
In the next step, the database is then processed and ran through more tools to make it available.
Testing
Once complete, the database will then be made available to a member of the OpenGround team to test and quality check.
Handover
This is where the member of the OpenGround team will inform you that the whole process is completed and that your database is now available. They will at this stage ensure that any administrator users that were stated in the cloud setup form will receive an access welcome email from the system.
Give Users Access
The final stage is then to give the rest of the users in your organisation access to the cloud. This is detailed further in the OpenGround Users page.