Unless all 3.5 have 4.1 versions when 4.1 goes live there should be same way to keep/migrate settings from the 3.5 profile for things like Amarok. Otherwise you need to build your music library from scratch.
This could be problematic. Programs change their names and configuration files are bit different, so somebody should need to make list of what we want to transport and what not.
isn't possibile to copy, as in the past for 3.x migrations, .kde3.5 to .kde4 and then leave every apps the responsability to keep or not old data?
Amarok 2.0 Beta 3 introduces a import-tool for the database/statistics from amarok 1.4.x See Release Announcement: http://amarok.kde.org/en/node/559
This is a pure upstream thing, we can't provide migration of kde3 configuration to kde4
