The reality is there are significantly more variables than you think. If you break down some of those processes and compare, you start to understand the scope of the task to price a move to the cloud and ongoing costs.
Let’s take an example – changing the location of physical servers to a new room might entail evaluating power supply, networking, air conditioning, and then moving the servers. Whereas a move to the cloud requires you to think about every aspect of running the server, the predicted demand and expectations of performance. Each and every one of these decisions will almost always impact on the cost in one way or another too.
In a simplistic description, it’s more than just going back to the drawing board to reassess infrastructure. You must consider everything you need to do that and how much of it you will consume to do that.
Think about cooking. If you were planning to cook a Sunday roast, in the physical world, you would work out how many you’re cooking for and go out to buy your meat and veg and then you’d go home to start cooking.
In a cloud environment, you have nothing in place – no oil, spices, trays, foil, utensils, cooker, power source or even the kitchen. In the cloud, you must build from a blank canvas.
Next, you consider your ongoing costs. How often are you cooking and need the power switched on? How often will you have guests, and will they eat more than expected?
Moving from a physical to cloud infrastructure for even one application or service means everything you took for granted is gone and you must start from the very beginning, crafting an architecture that achieves the required performance today, with the versatility to scale for tomorrow.
It now starts to become clear that a pricing tool will never be able to deliver a complete answer. And in fact, it’s not going to help you manage your costs going forward either.