Current import processing (Import Type "Account Information with Single Note") evaluates each row in the CSV file individually against the existing database in regards to duplicates. I have a number of files where the file contains numerous rows for persons that EXIST in the database and DO NOT EXIST in the database. For the persons that exist, the index/matching works perfectly - a new person is not created and the Journal Note is created. But ... for those persons that do not exist, the import process creates an IDENTICAL person for each row with the same person data ... i.e. each upload is creating 1,000s of duplicate persons ... each of which has to be merged manually ... the import creates a massive amount of work following each upload. It would be a huge benefit if the import had the capability of doing the matching for existing persons, just as it does now AND for it to create a new person for the first instance of the person in the file and to match any subsequent instance of the person in the file ... which would create no duplicates at all. I doubt I'm the first person to experience this problem and for my data (I'm uploading Journal Notes using the Import Type "Account Information with Single Note"). I'm happy to discuss the problem/use case/opportunity with developers. Support chat already reviewed this and suggested that I submit an enhancement request on this site).