Learn more about the Manage Duplicate feature

Modified on Thu, 16 Dec, 2021 at 6:53 AM

The Import Feature in Hushly allows you not only to create data but also update existing field data without creating duplicate records for your existing accounts, account reps, and account visitors. 


When you import the file, select an option under Manage Duplicates, and you need to specify what the system should do when it encounters a duplicate record during import. The duplicate rule allows the user to select which information source wins, and these duplicates are found using their unique identifiers 


There are three settings.

  1. Skip will use record information that is already in.
  2. Update will only update the missing record information from the sources.
  3. Overwrite will update all record data with data from the source, except when the source field is blank.

Account  

The Name and Domain fields of an Account are its unique identifiers. If any of the unique identifiers in the imported data match those in the system, the end result will depend on your manage duplicate selection.


Skip: The matching record would be marked as failed with the reason "Duplicate Record".


Update: The matching record would be marked as "passed".  

  • Account fields with existing data in the System would not get updated by the field values in the imported file.
  • Account fields with blank data only would get updated with the data from the imported file.

Overwrite: The matching record would be marked as "passed". 

  • All the Account field values would be overwritten with the data from the imported file.
  • Account fields with existing data would not be overwritten by a blank value in the imported file.

  • When the Domain field matches an existing Account, then the Account Name field can be updated.


Account Reps 

The Email field of an Account Rep is its unique identifier. If the unique identifiers in the imported data match those in the system, the end result will depend on your manage duplicate selection.


Skip: The matching record would be marked as failed with the reason "Duplicate Record".


Update: The matching record would be marked as "passed".  

  • Account Rep fields with existing data in the System would not get updated by the field values in the imported file.
  • Account Rep fields with blank data only would get updated with the data from the imported file.

Overwrite: The matching record would be marked as "passed". 

  • All the Account Rep field values would be overwritten with the data from the imported file.
  • Account Rep fields with existing data would not be overwritten by a blank value in the imported file.
  • When the Email fields matches, existing Account Rep names can be updated.


Account Visitors

The Invitee ID and Email fields of an Account Visitors are its unique identifiers. If any of the unique identifiers in the imported data match those in the system, the end result will depend on your manage duplicate selection.


Skip: The matching record would be marked as failed with the reason "Duplicate Record".


Update: The matching record would be marked as "passed".  

  • Account Visitor fields with existing data in the System would not get updated by the field values in the imported file.
  • Account Visitor fields with blank data only would get updated with the data from the imported file.

Overwrite: The matching record would be marked as "passed". 

  • All the Account Visitor field values would be overwritten with the data from the imported file.
  • Account Visitor fields with existing data would not be overwritten by a blank value in the imported file.
  • When the Email field matches, the existing Invitee ID can be updated.




Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons

Feedback sent

We appreciate your effort and will try to fix the article