# Migrate\_from\_s3 problems

**URL:** https://meta.discourse.org/t/migrate-from-s3-problems/119064
**Category:** Bug
**Created:** [May 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:** 16

<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: [August 10, 2020, 11:49pm UTC](https://meta.discourse.org/t/migrate-from-s3-problems/119064/16 "2020-08-10T23:49:13Z")

</div>

Since my PR fixing the silent data corruption that is `migrate_from_s3` never got so much as a glance, can `migrate_to_s3` at least be documented as a one-way street?

Right now, it’s frankly a trap for young players.

@cvx @zogstrip What’s your preference? Look at the PR or just remove `migrate_from_s3` entirely and be honest about the fact that it’s a one-way street?

---

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