[bfirsh]

The nice thing about using Docker is that everything is drop-in compatible. You can push your images to a provider such as Tutum or Google Cloud and they'll be able to run. If you've written any software that used the Docker remote API on Orchard, you can just point that are your own Docker daemon and it'll keep on working.

[webmaven]

If that were really true, the migration instructions would be more along the lines of "change the endpoint URL to your new provider", or "push this one button and authenticate", instead of https://www.orchardup.com/docs/moving

That said, kudos to the Orchard team for making it as easy as they did, I'll just stress again that the fear that migrating would be even more involved was what stopped me from trying their service in the first place.

There are several ways of addressing that fear:

1. Be so big that you know the service is unlikely to be shut down or acquired (that just leaves the usual lock-in concerns over future price hikes and the like, which isn't going to happen until the market stops growing).

2. Ensure that a fluid marketplace of drop-in replacement competitors exists (an Open Source release of the backend helps with this)

3. Document how easy it is to switch away from the get go, not just when you're shutting down: see https://web.archive.org/web/20140209113413/https://orchardup... and http://www.joelonsoftware.com/articles/fog0000000052.html