To alleviate the pattern of shutting down systems maybe you should fix your design process for services. Instead of having a healthy discussion when a service will be EOL you should ask a different question . Is this service going to be able to be able to be supported in the long run ?

Maybe APIs should have standard ways of accessing the information so that transisions can be seamless. Right now your API offerings make people distrust how long you will support any API.

I have had long healthy discussions about using google APIs but it's becoming harder and harder to advocate your products (which are great) when everyone perceives that you will shut things down.