Halo will need the following information to proceed with the migration:
Hosted Halo Agent application URL
Hosted Halo End User Portal URL
Current on-premise SQL version
To ensure compatibility
Whitelisting for mailboxes, SMTP relay, AD connections etc
Integrations required by the customer for syncing
Stable (recommended) or Beta
On-Premise connections required
AD connections, PowerShell etc
Is Backup Encryption in use?
We will need a copy of the certificate, or this will need to be turned off for the backups transferred to Halo.
Phase 2: Timeline and Preparation
Once Halo has the above information, the customer will be provided with the requirements needed to complete the migration. The migration timeline will be provided, and a completion date will be established.
If the customer will use a non-Halo domain for any URL hosted by Halo, then DNS changes will be scoped out at this point. If the customer is using a non-Halo domain then an SSL certificate will be requested by Halo.
If an SSL certificate is required from the customer, then this will be requested at this point using AWS validation - Requires adding a record for each domain required, one for the web application and one each for the self-service portal(s). This can be a single wildcard if they sit under a shared domain.
Phase 3: UAT (Recommended)
A copy of the live database from the on-premise instance can be copied into Halo’s hosted instance and deployed as a UAT environment for testing. This is recommended so that the customer can observe the process and allows for smooth migration of production instances.
Phase 4: Production Migration
A full backup of the production database is taken and uploaded to an FTP site (this can be provided by Halo), and all backups are stopped on the on-premise server. Once the database is restored in Halo’s environment, a transactional backup can then be taken and uploaded to the same place. At this point, the current on-premise application will be turned off and email processing stopped. The customer can continue working on the on-premise application between the two backups, and service is only disrupted after the final backup takes place.
The process of the final backup, taking the database offline, uploading to the FTP site and restoration usually yields downtime of around 15 minutes to the main application. The reporting module in the Agent application could take longer with larger databases due to propagation through the database cluster.
Halo will deploy the instance into the hosted environment and run through tests on all services once the application is reachable to the customer. The services to be tested are:
Halo Agent Application
Halo End User Portal
Email Processing (inbound and outbound)
Halo Integrator (if applicable)
The Migration is complete once these tests are completed.