# Photo migration path for our MSP site

**URL:** <https://community.transloadit.com/t/photo-migration-path-for-our-msp-site/17530>\
**Category:** Transloadit\
**Created:** [April 1, 2025, 3:15pm UTC](https://community.transloadit.com/t/photo-migration-path-for-our-msp-site/17530 "2025-04-01T15:15:05Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![tonyhansen](https://yyz2.discourse-cdn.com/flex032/user_avatar/community.transloadit.com/tonyhansen/32/1354_2.png) [@tonyhansen](https://community.transloadit.com/u/tonyhansen)\
**Post date:** [April 1, 2025, 3:15pm UTC](https://community.transloadit.com/t/photo-migration-path-for-our-msp-site/17530/1 "2025-04-01T15:15:05Z")

</div>

We are a small MSP using PHP. Photos our users currently upload are stored on-server (the process managed by standard PHP methods) and their meta info is inserted (or updated) to the database. A background task makes various thumbnail sizes, copies them to an s3 bucket and updates the database of their s3 availability there. Our system has become bloated by multi-megabyte, uncropped pictures. We need to:  
-Enable users to crop as part of the upload process  
-Downscale and compress for better storage efficiency  
-Notify users of most wasteful pictures already uploaded and give them the tools to crop, rotate and compress.  
-Automated scan the photo database to auto-compress (and maybe auto-crop) the old photos.  
I am guessing this is a common migration path to your system. Is there a step-by-step dealing with this?