# Migrate\_from\_s3 problems

**URL:** <https://meta.discourse.org/t/migrate-from-s3-problems/119064>\
**Category:** Bug\
**Created:** [30 במאי,‏ 2019,‏ 7:28am UTC](https://meta.discourse.org/t/migrate-from-s3-problems/119064 "2019-05-30T07:28:49Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![mcdanlj](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/mcdanlj/32/131829_2.png) [@mcdanlj](https://meta.discourse.org/u/mcdanlj)\
**Post date:** [30 במאי,‏ 2020,‏ 12:45am UTC](https://meta.discourse.org/t/migrate-from-s3-problems/119064/3 "2020-05-30T00:45:45Z")

</div>

I recently opened a new PR to allow migrating fewer posts at a time (such as testing one at a time) and added tests for the task.

[https://github.com/discourse/discourse/pull/9933](https://github.com/discourse/discourse/pull/9933)

It feels like it makes sense to start with posts, since you want to rebake posts to change the URL in the cooked post after each migration; migrating all the uploads and then starting the rebakes would leave the site very broken for potentially a long time for a large site (I need to migrate about 100GB from S3 to local, so I care). But what I wrote might help start writing a `migrate_uploads_from_s3` task that would be run after migrate\_from\_s3 in order to clean up uploads that weren’t part of posts.

@zogstrip What’s the current status of “We’re working on…” — is this still in flux or is this migration now worth paying attention to?

---

_[View the full topic](https://meta.discourse.org/t/migrate-from-s3-problems/119064)._
