I managed to import my contacts from my Samsung Android 13 device after converting the .vcf file, seeing ā3 errorsā reported on import.
Any idea where to see details like line numbers within the file, where some issue was detected?
I also downloaded it again after import. When comparing it to the initial imported vcf file, I now have 9 āBEGIN:VCARDā less!
Analysis showed, that the import truncates notes with when a comma is detected in it - apparently you need to escape commas in values with a backslash before importing the .vcf file!
Well, the rules are clear regarding how to format values in a VCARD format.
But Samsung does not care. Also ā\nā as a line break within notes or addresses is not allowed in VCARD 2.1, the format Samsung produces.
Of course, I can use some advanced editing of the exported file using some regular expressions to fix that stuff. But it is just so bad how difficult it is to move away from Google without loosing parts of your data - and donāt expect it to get better for calendar entries either.
Well, it turned out to be not the fault of Samsung!
It was my fault using some Python script referenced in the forum to
convert VCARD2.1 to VCARD3.0 format. This is faulty!
Using an Android mobile both contact apps from Samsung and from Google
export to VCARD2 format, while importing to the Murena cloud/eCloud only
can deal with VCARD3 format.
The solution was to use Googles web interface
āhttps://contacts.google.com/ā; in the upper right corner next to the
printer symbol there is the symbol to export contacts; use option āvCard
(for iOS contacts)ā to export to VCARD3 formatted file.