Critical System Flaw in Contact Record Update Process via CSV Import
A
Anthony CRM Admin
This is to address a significant malfunction within your current CSV import protocol that requires immediate rectification. The GHL system presents itself as equipped to handle contact record updates through CSV imports. However, it falls short when processing critical data such as email or phone number changes.
Upon the execution of an import intended to update these fields, the system fails to replace the existing data. Instead, it erroneously adds the new information to the "Additional Email" field, thereby preserving the outdated contact information. This is not merely an inconvenience; it constitutes a fundamental defect in your data management process.
This error has substantial repercussions for our operations. Consider the case where a client needs to update the email domain for over 1300 contacts. The expectation is for a swift update via import. Yet, your flawed system compels us to resort to manual editing — a method that is inefficient, time-consuming, and prone to human error.
Let me be unequivocally clear: this is a serious flaw that demands an immediate solution. Clients depend on the accuracy and efficiency of your system for their business operations. The inability to reliably update contact information undermines our service and our clients' trust.
Immediate action is necessary to correct this issue. We need a robust system that updates existing contact information accurately without manual intervention. I expect a prompt update on the measures being taken to resolve this critical problem.
Log In
P
Pallavi Kothari
Merged in a post:
Ability to Update Primary Email On Import
A
Anthony Ricciardo
The inability to update the primary email upon an import is a significant flaw in the system, in my opinion. Take this use case: 2500 contacts with an email @testcase.com. The organization updates their emails so that the .com email no longer is active and their email has changed to @testcase.org.
What is the solution to update all the contacts with the new primary email upon import? The option seems to be there, but when you perform the import, the new email is simply appended to the contact as an additional email.
Its obviously not possible to manually change the primary email for all 2500 contacts AND if it was intended to update the contacts with an 'additional email', then that option would have been selected.
Additionally, the option to delete all the contacts and re-import them is seriously flawed. The entire point of maintaining the contacts is so that notes, conversation history, and opportunity stages don't become lost in the export import process.
Please, this is a necessary, common sense ability to update your own contacts. If someone makes a mistake, you can simply revert back or re-import the list to correct it.
A
Anthony CRM Admin
Even if this was an expected or intended consequence, there is a separate field for 'Additional Emails'. So, if the user wanted to update or add an additional email, they would choose that field in the mapping when importing. Otherwise, it an import should have an intended circumstance to update the primary email via import.