 <p>It seems there is a bug in the current open source Parse code that keeps the files pointing to a parse server instead of your new heroku or other specified server. </p> <p>A suggested fix is mentioned here where you can strip out the parse URL for your own. </p> <blockquote> <p>stripping out the "<a href="http://files.parse.com" rel="nofollow">http://files.parse.com</a> / OLDapidecrypted and replacing with my info</p> </blockquote> <p><a href="https://github.com/ParsePlatform/parse-server/issues/308" rel="nofollow">https://github.com/ParsePlatform/parse-server/issues/308</a></p> <p>Edit: It seems Parse Dashboard (<a href="http://blog.parse.com/announcements/introducing-the-parse-server-dashboard/" rel="nofollow">http://blog.parse.com/announcements/introducing-the-parse-server-dashboard/</a> ) is now available which may help debug the issue but also I think they are setting up a migration for parse files. </p>