@simon @luis_in_brief I agree. The problem is that we've distributed the URL to that content far and wide. There are a couple of options:
1) use http redirects to bounce from old server to new server (depends on old server remaining up)
2) send out notifications that image X has moved from old server to new server (noisy, especially for a big account)
3) content addressing. If you try to get an object from old server and it fails, retry it from IPFS or something similar. (public stuff only)