I have asked this question before and I'm sure someone posted that there was a legacy behaviour setting - if so I cannot find it.

Is there anyway up uploaded an existing folder/file structure into ss4 and have it parse it for inclusion into the file library (even if it means moving things out of folder roots?

Without this feature, the new abstracted system (I personally hate this abstraction filesystem) I regard as a major inconvenience. SS2 and 3 have always had the command admin/assets/doSync to do just this.

Personally I would rather see the file in use positioned just where it should be and the versioned ones abstracted.

Is there any way to turn this off? Is there anyway to import the filesystem contents?

The config.yml setting

File
migrate_legacy_file: true

does not accomplish this but merely imports the existing ss3 file tables as far as I can see.

I Like it

It is entirely with anybody's right to like it, but I don't.

It's not the versioning that's bad, it's the fact that the primary published version is abstracted and new files cannot be bulk uploaded and absorbed as part of the filesystem - as has been possible for the entire history of Silverstripe so far. For me that's a showstopper and will at the very least keep me on 3.x for the future. Perhaps even move.