Cloud migration proposal template

Yes. You can download the cloud migration proposal template as it is and fill it in yourself. You only need a Cobl account if you want Cobl to rewrite it with your own discovery notes and the client's application inventory, which you then review and edit before anything goes to the buyer.

The business reason to move, assessment findings, the target architecture, the approach per application group, migration waves and timeline, cutover and rollback, a cloud cost estimate, support after go-live, and pricing with a responsibility table. The part most proposals leave out is run-state support: the client is buying the next three years, not only the move.

Most partners split it into three parts: a fixed fee for the assessment, a fixed or capped fee per migration wave, and a monthly fee for managed services after go-live. Show cloud consumption separately, since the client usually pays the provider directly. If the client qualifies for a cloud provider funding program, state what it covers and its conditions.

Start from the assessment: current server sizes, utilization, storage and network traffic. Right-size each workload, price it with the provider's calculator, and state the assumptions, such as reserved capacity, growth and hours of use. Show the estimate as a range next to today's cost, so finance can see which inputs move the number.

Rehost moves an application to the cloud as it is, often called lift and shift. Replatform makes small changes to use managed services, such as moving a database to a managed database. Refactor changes the application itself to use cloud-native services. Each step costs more and takes longer, so the proposal should justify the choice for each application group.