A key part of cloudstep's ability to properly model the cost of transition to public cloud is the planning tools. Before you can understand the cost of migration you need to understand how you'll get there. We start with a blank planning board and arrange our plan into Waves (when we will do things) and Intents (how we will migrate them).
Every Application in the model will already either be SaaS, IaaS or on-premises. Before we migrate anything in each Wave we need to understand what the starting point is. Drag Applications from the Browser onto the grid into the appropriate starting point.
Once you've arranged the starting point you need to make decisions about how you'll treat each application and importantly when. Try to balance the migrations appropriately since you can't do everything at once. Its also important to understand the affinity each application has with others (usually because they are on similar or related server). This will ensure that the right apps are migrated together. You can tell the planning tool a bit of detail about your migration effort too:
You can drag/drop plans anywhere on the board and when you're ready move to the next step and implement the plan.
You can click the Implement button at any point. If the model is complex it can take some time to complete. As its going through you'll see a lot of messages pop up. This shows that the model has been busily doing its thing creating costs and objects, moving things around and setting the model up to reflect what you've decided.