For best performance your client stations should be in close proximity to the Sage server regardless of where it lies (ie have an application terminal server in the same network as the Pervasive server) Sage doesn't perform well if you add latency between the client and the server. 

We moved Sage to Azure a few weeks ago and have been happy with the move. We access via virtual remote desktops.This way we can always access Sage regardless of the status of the power/internet at the office.

We moved Sage to the Microsoft Azure cloud a year ago and has worked very well.  Access through RDP and a bit of a change from having an on premise server.  If you are using Timberscan this should be discussed with your Sage consultant and was a real issue early on because there was not enough resources allotted for Timberscan use.   

If you have a file server where you have other files that Sage needs to access or puts files that the Sage accesses this can create latency issues. We currently have that issue and once the files server is also in the cloud it will be awesome.  

Rebooting the server if they give you access is extremely fast so make sure you know how to reboot the server when it is in the cloud.