We have a client who has been very happy with Appian on the Cloud for a good length of time, but is now questioning whether all the data being generated by our app and the app itself shouldn't be hosted on their own servers. I know it's not typical to start Cloud and then later go self-managed, but that's what the powers that be are seriously considering. We have recommended against, but they have what they consider to be compelling arguments to pursue hosting the app themselves.
About the only guide we have to go on is the guide for going from On-Prem to Cloud (in reverse?), but I wonder if anyone else has ever had to perform this operation and can steer us clear of some of the pitfalls they discovered during Migration. What we've been asked to deliver is a guide on how to Migrate the Cloud hosted app to their own server, along with everything we'll need to have in place before we begin.
This, thankfully, is just in research phase, but research on this exact procedure lacking, so any comments would be appreciated. If anyone has documentation of a VERY strong case for not doing this and sticking with Appian Cloud, that could also be beneficial.
Discussion posts and replies are publicly visible
You've probably taken this angle already but just in case...if they want the data (rather than the app) internalized for other processing/purposes then there is the option of the Enhanced Data Pipeline which is designed to ship cloud-based data to internal infrastructure.
Moving Appian from Cloud to On-Premise loses more than it gains imo. Hopefully by splitting the "data requirements" from the "application/service" requirements will give you better ammunition for the argument for staying on Cloud.
Hi, lets say that the client wants to move it all, not only data, what is the procedure for this move?
I'm guessing that a full disk backup and full DB backup would suffice and restore on prem, then changing hostnames/URLs in config files. Am I wrong?