My reply was to use the standard fields for k2 and fetch them out for display on the website in some manner, not to export them.
I have not used user extended fields for k2, but i think thats what they are for. If they are stored in one field it would be the same way k2 stores its extra fields and would have to be seperated into first and last either before displaying them on the site or after exporting the field...with excel etc, there should be a delimiter to work with. In php you basically put the field into an array and refer to the elements of the array on the fly.
Other products like jomsocial will probably give you this ability built in and the users will be gathered by them, and then synced with jomla and k2 users