Hello @GregorSondermeier, and thanks a lot for your feedback!
This first iteration of our take on data management is indeed aimed at developers.
But as developers you could have always exported and imported on SQL level already
Well yes, and no. Doing raw SQL dump & restore offers you a 1:1 mapping of your data but ignores business rules associated with Strapi & prevents doing data transformation (+ it doesn’t transfer local media files). On top of that, not every developer wants to deal with the DB and instead wants an easy and documented way of dealing with their app data.
Finally, as discussed in this video, Data Import Export is only the first release of a much more ambitious vision, in which you’ll be able to transfer Strapi data not only between a strapi instance and a file but from anything to anything (and also build custom data providers using a simple programmatic API: json, csv, live APIs, hooks, other CMS, etc…).
I had assumed (my fault) that it is a feature for content editors. I don’t know, go into the content manager
For now, it isn’t, but this is something we definitely want to iterate on & add in the future. We were focusing on the developer experience for the moment, but we won’t let anyone behind 
select one content-type, select one or multiple entites of that content type and click a button to download an export of these entities. Go somewhere else and import these entities. Basically like this plugin, but natively.
yep, also planned 
I’m really sorry to be so negative
Don’t be, it only means we need to communicate more about our vision & goals, so thanks for the opportunity.
I hope I was able to help you understand our vision better, and don’t hesitate to ask more questions if you have some.
Have a nice day!