No it doesn’t. It’s always just a selection of data. So if exporting the “example csv”, you’re technically never exporting the whole dataset that would be available.
This has to practical reasons:
you normally just need an example, so e.g. 10 records usually are enough to get the idea
performance, the more data you fetch the longer the csv export would take
users are impatient
Yes, however, this is just a usability thing for you. It’s a bit different under the hood. The members column would allow you to define members during creation. That’s crucial where your users are already available.
This directly gets me to your 5th question:
Hell yeah it can matter depending on what you want.
If you’re planning to use domain specific alocation, your Organization has to be available before the user. Zammad does check for this alocation exactly once: During user creation.
I believe it shouldn’t be created. First- and Lastname are mandatory fields which you can’t supply via importing an Organization. This indirectly depends on question 2 and 5 I believe.
Yes, Zammad will either update an existing organization or create a new one!