Hi @Convly and thanks for your reply!
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).
Ok, the transfering of local media files is indeed important and was not possible on the SQL level previously. Could you elaborate about the “business rules associated with Strapi”? Do you mean Strapi internal stuff, like settings, admins and users?
Pseudo EDIT: As I’m writing this reply I’m also watching the community call recording and reading the documentation.
Ok I see, certain instance-specific data like users and tokens are not part of the exported data. That’s very good indeed!
yep, also planned
That’s also good to hear! It wasn’t clear to me from the announcement in the newsletter and the blogpost that this feature will receive multiple iterations with more and more features being added.
Don’t be, it only means we need to communicate more about our vision & goals, so thanks for the opportunity.
And just by your explanations, I now understand your motivation behind it better. So thanks a lot!
However, to give some more (hopefully constructive) feedback:
I tend to get a little overwhelmed by the potential sources of information about Strapi. There is the Forum, Discord, the community calls, the blog, the documentation, the feature request page, github. It feels a little decentralized and important information tends to get overlooked.
Now that I’ve actually found and read the export/import documentation, I understand a lot better.