Getting your stuff to the cloud isn’t hard with the right plan. After all, with respect to migrations, the cloud is not too different from your on-premise or managed servers. The Azure management portal makes it relatively easy to spin up a new SQL Azure instance or a virtual machine intended to be used as a database server.
Once your infrastructure is established, the open source community has developed a migration wizard that makes it easy to convert and publish your database, found here. This alleviates the need to check for compatibility issues, automatically scripts your database to be created in Azure, and can even execute your scripts for you on your Azure SQL instance.
You can continue using the migration wizard as you develop, but I would suggest only using it for the initial migration. After you’ve migrated, I would use Microsoft’s SQL Server Data Tools (SSDT). SSDT will allow you to check for compatibility issues, allow you to fix them, and compare and publish your changes right from Visual Studio. You could even go a step further and create a TFS Build process that deploys changes and alerts you when it finds issues with compatability. SSDT can be found here.
If you have any questions related to cloud migrations, or would like to talk about other things involving development and architecture, please contact me here, via my website.