Hi. I've been testing and retesting for a few months and keep running into anomalies in export/import. Some of the issues are known: imports won't accept the "Work" field names and will default to home or other. Even if you have completely correct contacts, export the contact to use the export excel as a template, delete the data from the excel but keep the system-produced headers, then populate with new contacts, the import still doesn't accept work address or allow you to map to work addresses during the import. The result is the user is required to manually change every single contact by hand--every single contact. Other issues I am running into are full exports munging headers and data so the fields under a particular header are populated with data that belongs under another header. I've seen this occur when custom fields contain a word that is part of a system field. Clearly the string match coding for export/import is too fuzzy and should be tightened up. So I'm suggesting: 1) at least offer professional services to make a global change so all contact email and physical addresses can be changed to "Work" (product isn't working as advertised), and 2) fix the string matching code so export/import works correctly, and 3) fix the field mapping during import. And find a way to truly delete all contacts and associated data so "old data" doesn't persist. If I delete a contact, then import the contact later (same email), some data persists from the original contact, such as "Notes". So imaging testing for weeks and entering test notes and then finding out you have to go to a new database/new account if you want to get rid of a bunch of persistent notes that say things like "test 01". Finally, it would be great if you had a way to bulk import tags...Being forced to use a new database/account due to the persistence of old data means manually entering tags every time...ouch.
... View more
