“Oh, let’s just move that to Azure….”
That’s somewhat like saying “Oh, let’s drive that car to Hawaii.” Not as easy as it sounds. First, you’d have to convert the car into a boat.
Of course converting any workload into a virtual machine (VM) is much simpler. But that’s not all that’s involved in migrating workloads to Azure. You also need to be sure your workload is cloud-ready, compliant with Azure configuration specifications, and a cost-effective use of an Azure VM. Then you can start putting on your sunblock and getting ready to say “Aloha Azure!”
The Carpenter’s Rule
While we’re on the topic of building boats, it’s important to always remember the age-old Carpenter’s Rule when considering which workloads to migrate to Azure. “Measure twice, cut once!”
There are many considerations to take into account when measuring. Most companies prefer to migrate non-critical VMs to less expensive cloud resources. Since they’re on the other side of an internet connection and subject to the unpredictable nature of internet latency it is preferable to put VMs that won’t be adversely impacted by that latency in the cloud, as well as those that don’t require frequent connections to other resources.
Operating system is another consideration. Is the workload you wish to migrate running an operating system that is supported on Microsoft Azure?
Azure VM sizes are respectably liberal, but you will want to be sure that the VM you want to migrate doesn’t exceed 16 cores, or the maximum 112GB allowable memory.
Still have workloads running on physical servers? Here’s where you’ll need to convert that car into a boat, or in this case the physical server into a virtual machine. Just as soon as someone claims you can convert any physical server workload into a VM, someone comes up with one you can’t. Be skeptical and be safe.
Assessment – Worth the Time, Effort, and Money
You made the decision to move to Azure to enjoy many benefits and values, so when you’ve entered your subscription there’s a tendency to want to rush. Resist the temptation.
Take the time to create a plan that is consistent with your goals in using Azure. Perhaps its cost-effiency, or the ability to scale beyond your own data center’s limits easily. Perhaps it’s the flexibility and accessibility.
Whatever the goal, take the time to create a comprehensive inventory of the workloads to be moved and examine each one to determine its best destination, and any processes required to properly prepare it for migration. The savings in time, effort, needless frustration, and wasteful, costly, unnecessary resource consumption will more than return on your investment.
Consult with the Experts
To best assure an accurate and effective assessment, engage the experts at Hanu Managed Services to assist. Their experience with preparing and migrating any workload from any platform in any language to Azure will make your migration projects go flawlessly.