I think you need to catalog just what you're paying for with your current provider. If you're running on bare metal machines and performance is your requirement

I think you need to catalog just what you're paying for with your current provider. If you're running on bare metal machines and performance is your requirement, you're going to require more vertical scaling on AWS. If you are paying for boxes that are underutilized, then, you might find running on AWS to be cheaper. You also have the advantage of AWS scaling and the ability to do things you probably cannot do with your existing host. First and foremost, if you're moving to AWS, make sure you can split your services into multiple availability zones. A lot of people got burned when they put their entire company in separate deployments within the same availability zone. Is price your only motivation to move? If so, ask your current provider to renegotiate. Have quotes from two competing providers so show them that you have investigated other providers that appear to offer a better deal. I don't know what your company does, but, unless you have a ton of hardware you're really not utilizing, simply moving to the cloud isn't a silver bullet for cost savings. Things don't run the same way and there is definitely a different paradigm to implementation. You will likely spend a lot of your cost savings, if any, in re-engineering your current processes to better fit the cloud. Are you hiring people at your company to maintain the AWS installation? Your current programmers/engineers are going to need to deal with things in a different light. If you just hire a consultant to transition, when things break, is your current team going to have enough insight into how things work to be able to diagnose or fix things when things go wrong? There are things to outsource, but, if your current team doesn't understand AWS, the first time you have a problem, you're going to be back on the phone with the consultant that moved it.