Skip to main content

Merging Data & Conflicts

Merging data and managing conflicts

Updated over a year ago

Ecanvasser Contact Merge will allow you to import and merge new files without a Contact ID. To do so efficiently, it is best to familiarize yourself with the different options to do so.

When you upload any file after your first import, you can assign column headings as you had previously. In doing so, you will want to ensure that you include:

  • First & Last Name (and Date of Birth if possible)

  • All Address/House information (including Precinct)

When you select Import, you will be presented with two options:

  • New

  • Merge

New

This is appropriate whereby the import of your new file is not expected to conflict in any way with your existing data - all contacts contained therein will simply be added as new contacts.

An example of when this would be if you had been using Ecanvasser for some time as a candidate for the local council, but then wished to continue to use the same campaign for a run at a regional assembly or national parliament. You might have already had Precinct 1 uploaded to your campaign, and now wish to add Precincts 2 through 6.

Merge

Inversely to the above, in this situation your boundaries haven't changed at all, so you'll expect a lot of conflicts. 

This is appropriate when you're updating a single file that you expect to mostly overlap. Where it's particularly useful is if you receive an updated Contact File for your area every month/year.

In this case, in situations whereby:

  • A name and address from the new file match those of the new file, no action will be taken

  • A contact is present on the new register, and no contact of that name was present on the old register, they will be created and added

  • A contact is present in the new register, and a contact of the same name existed in the old register but at a different address, a conflict will arise

Understanding Conflicts

When your data import has been completed, you may see a notification that indicates that a conflict has arisen. Click on the notification to view the conflicts page.

A conflict will occur when you selected "Merge" as your import method and when the data from your import file is very similar to the data that you have already imported however there isn't enough information to be certain that it is the same data therefore you will need to determine which version is correct - the contact information previously imported or the version that you have imported now.

Down the left-hand side of the screen, you will see all conflicts from your recent merge. When you click on any of these, you will be presented with potential resolutions on the right-hand side.

For example: Barry O'Brien lived in House A in your first data import. However, in your second data import, Barry O'Brien does not live in House A, however, Barry O'Brien lives in House B in your second import.

When you select Barry O'Brien on the left-hand side, you must choose whether to merge him into the previous record (all data will be kept, and the old Barry O'Brien will move house), or simply to enter our Barry O'Brien as a new contact, while also keeping the old entry.

This does involve some level of discretion, as it is impossible for any system to automatically know if two Contacts are the same based solely on name and address. You can however take a few steps to ensure such conflicts are resolved in as accurate a manner as possible:

  • Cross-reference household occupants - if you check and see that the Oldbury O'Brien lived with a Terry O'Brien; and that this is the same but both are at a different address in the new file, you can say with a high-level degree of certainty that you should merge these contacts

  • Check if you have contact information for the old version of Mr. O'Brien; perhaps you can contact him to confirm his current address

  • Members of your local organization can use local knowledge to help point you in the right direction

Once you resolved conflicts as outlined above, you'll have to make some tougher judgment calls as to how to proceed with the remaining few outliers:

  • Keep both the old and new Barry O'Brien and potentially have a duplicate entry

  • Merge the old into the new and potentially have interaction data attached incorrectly

  • Insert the new Barry O'Brien, and delete the old one

Deleting Old Contacts

Once you've completed your merge, you might have a few stragglers from your old file still in your database that you wish to remove (for example, if you took the third option in the above paragraph).

Clearing up your database is simple - all contacts in your Ecanvasser campaign are tied to a Contact File, specifically the newest file they were present on. As such, if you'd like to identify the potential duplicates, those who have moved out of the area, etc. and delete, simply:

  • Navigate to the Contact tab

  • Filter for your Old Contact File

  • Select All Contacts

  • Bulk Delete

Effectively what you're doing in this situation is deleting all of the contacts who have been removed from the electoral register since you last updated (usually due to a death, or a person having moved and re-registered outside of your area).

If you wish to be a bit more cautious, feel free to add additional filters to exclude certain contacts. For example, you might want to filter for Raised Issue - Yes also, to ensure no Issue gets deleted along with its contact, and this will also allow you another opportunity to check in with a contact to confirm if they have or have not moved!

Check out our handy De-Duplication Tool for confirming and merging when a contact is a duplicate in your database.

If you have any additional questions contact support@ecanvasser.com

Did this answer your question?