Go-Live for the Enterprise Migration

Data Synchronization


Auto-Failover to Replicated Environment

Leading up to a go-live event, WSM’s engineers will prepare go-live scripts, to, for example, address connection string changes, activate cron jobs or scheduled tasks, etc.

WSM’s engineers will lower TTL values on any domains that will be pointed to the new environment as part of a go-live event to ensure timely DNS propagation

Your WSM project manager will work with you to schedule either one or multiple go-live events, depending on your business goals and objectives. These go-live events usually occur during preset maintenance windows and often during off-hours.

WSM will work with you to determine the best go-live scenario for your business goals and objectives; for example performing data synchronizations for databases, and content added during the course of the migration process, or, depending on the migration maintenance window allowable, we could recommend performing a ‘fail-over’ type go-live event.

In an auto-failover replication, portions of your workloads, databases and other services fail-over to a replicated environment which will ultimately become your new production cloud, physical or hybrid environment at the completion of the go-live event.

10 business days post-migration support  

WSM includes 10 business days post-migration support that begins after the Go-Live event is completed successfully.  During this period of time our migration and expanded solutions team are available to address items that may come up after all of your workloads are made live.