No documented safe way to migrate LFS objects BETWEEN/WITHIN backends

• What product or feature(s) affected? LFS
• What docs or doc section affected? https://docs.gitlab.com/ee/administration/lfs/

In the case of cleaning up mistakes, changing organization, or changing providers, there should be a way to change LFS backend data from one place to another without breaking links or losing anything. There only exists migrations to move from local to remote, and back. There's nothing to say how one could safely reorganize or move anything. Moving through local disk to get it done is infeasible as soon as LFS fulfills its namesake.

In my specific case, LFS is in the root of an s3 bucket, and I'd prefer it be one level down in a subkey. I could just copy all the "folders" into it, but I doubt the database would accept that and it's likely to break. Maybe the migration code already handles this, but there's no indication at all whether that's the case.