Hello All! - I am working in a new v12.1 site to replace an existing v8.17 site. The v8 site (as well as the new site) uses AWSS3 file storage for media, though the sites themselves are not hosted on AWS. This is all working fine. My question is this... The old site has thousands of media items already in the S3 bucket. Even though the new site is pointed at the same bucket and uploading correctly, the existing items are not available/visible in the CMS. I think this makes sense as the new site has no reference to these old items. SO - I'm not sure if the right question to ask is about importing, or listing the media directory, or seeding the database? The important bit is that the existing files can not change name or path. Thanks -Roger

Hi, uSync should be able to do this. If you have uSync.Content edition installed on the source site it will generate config files for all the media, Moving these files over to a V12 site with uSync installed and when you import the media it will put all the references to the locations in (it won't change them to any new format)

Awesome thanks Kevin! I will check it out. Always a little scary messing with thousands of clients files 😨, but it sounds straightforward.

Yes, I would do this on a test Umbraco site that is pointing to aws too first, won't do any harm and will tell you if a basic import will work

Does the fact that the source site is currently hosted on umbraco cloud change anything? Since I typically use Umbraco S1 to keep the sites in sync, is Usync still a good fit there?

🤔 technically uSync will run on Cloud - but i would turn all the syncing on save / import stuff off in the confitg - and then just run the export. you don't want uSync and Deploy getting into a fight.