I did not have to do this, but I would say that there are no automatic migration tools. So yes, you have to collapse yourself.
My approach would be to batch migrate using cron.yaml , keeping track of which files were migrated so you can serve them differently (according to this page ). Cloud storage provides you with an md5 hash after creating an object that you could use to verify that each file’s migration was error-free before deleting a copy of Blobstore (you can calculate a similar hash while the file is in transit).
Regarding libraries:
- The Google Cloud Storage Client Library uses a revolving download feature to “stream” a file, which will make things smoother in memory. I believe it is fairly reliable (unlike the legacy API / Google Cloud Storage APIs / Files API).
- The JSON API client is at a lower level.
boto not optimized for use in GAE, but rather on the desktop, and you don’t want to leave Google Cloud to migrate ($$$).- As far as I know, Blobstore allows you to send files from GCS and upload files to GCS, but not write files from your application as such.
Ezequiel muns
source share