The key to a successful cloud migration? Accurate discovery of your applications and technology - no guesswork allowed. With Tidal, you can complete this step faster than ever, automatically.

Tidal provides you with an automated assessment of your software usage, defects, vulnerabilities, and more. You’ll know exactly what to expect before your cloud migration.

I recently had a cloud migration client who was at the beginning stage of their discovery phase and looking to jump straight to “which database platforms should I be using in the cloud?” - a tall ask you might say, but following the three steps below they were able to discover and analyze all of their database servers in just two weeks.

Google “CSO role description” and you will get 9 million results, none of which will sufficiently describe why it has been both challenging and enormously fulfilling for me at Tidal Migrations. Quite simply, a CSO role is uniquely tailored to the company it belongs to. So while Deloitte has this article about the six faces of a CSO, I wanted to share how my role came about and what it means to be a CSO at Tidal.

Migrating your DNS to a cloud-based service like Amazon’s Route53 service can be a daunting task. With dns-tools, you can test your DNS records before and after the migration to ensure that everything made it across in one piece. If you are migrating from a BIND DNS server, see our blog post here. Follow these four steps to migrate from a Windows DNS Active-Directory integrated server to Route53.

Data center and cloud migrations often require changing IP addresses of your servers and application end points. These changes require careful planning and precise execution in order to minimize downtime. Typically, this is executed by manually searching your DNS server’s configuration for each server that is migrating.

Moving workloads to the cloud has many benefits, and one that is often overlooked is the opportunity to modernize your network. In a traditional “perimeter-based” architecture, users and devices are authenticated and authorized on a device-by-device basis when connecting remotely via VPN.

Migrating your DNS to a cloud provider like Amazon’s Route53 service can be a daunting task. Thankfully, with dns-tools you can test your DNS records before and after the migration to ensure that everything made it across in one-piece. This is the three steps we follow when migrating to Route 53: Follow along below and in just 10 minutes you’ll know if everything will migrate smoothly for you.