When we moved, our jamf buddy and the Jamf could team kinda walked us though everything ... I think they wanted us to upgrade before we moved but not 100% sure I can't remember. Our database was garbage too and we didn't really have any issues. I also think that the could team checks the database before they import it.
This all depends on how you are moving ... I think there are two major types move the database, change the JSS url and then the machines get sent to hosted server or push a Quick add .pkg to your machines send them to the hosted server. We went with the 1st way as we need to keep the FV keys.
At the same time we changed how we image to that was changes to a lot of policies and process we also moved all out .pkgs to the hosted share so we had to change the polices to pull the files from there.
I don't remember much more than that, but I don't do anything complicated in my JSS ...
Jamf would walk you through the whole implementation. Since its jamf cloud you wouldnt have to manually install the JSS or setup databases etc as that would be handled for you. The admin guide can be found here: http://docs.jamf.com/10.3.0/jamf-pro/administrator-guide/About_This_Guide.html
"operational tasks post jamf cloud implementation" - The Jamf Pro guide is for Jamf Cloud, it's the same, one is hosted on premises, one in the Cloud, that's the only real difference.
What you wish to do with it afterwards depends entirely on your setup but as Santosh mentioned, those are the most common operational tasks.
There is no template like that as you have to cater it to your own environment and see what works for you. I suggest contacting JAMF and setting up a POC. I was able to setup a POC with JAMF prior to the contract. They walked me through everything and it gave me time to play around in the console and see what I could or could not do. I was given 10 licenses to play around with.