When you discover that a person in your database has two records (what we call a duplicate), you will want to merge the information from one record to the other. This merge process occurs only after someone has verified which two records are duplicates, decides which record to keep and which information is correct. The normal rule of thumb is that you keep the older record or the one which has church membership information, such as Decision, Baptism, Etc. or the one which is in the correct family. However, that is your decision to make.
The merge process is done using the Merge Controller, located under Other Management on the Person page. A user must have the Manager role (your Admin can create this role if it is not in your database) or be an Admin in order to access this link.
IMPORTANT NOTE: If the duplicate record has Contributions, Enrollments, etc., the Admin must complete the Part 2 process (using the Merge Fields and Move Related Records button) in order to move these items prior to deleting the record.

The Merge Controller has 2 parts.
Part 1
Once the duplicates have been identified, the person who has the Manager user role (see Note re roles below) decides which Basic information to move to the other record and then actually moves that information using the Merge Controller. This basic information is what is one a person’s Basic tab as well as their family address.
Part 2
Once the Basic Information has been merged, the Admin uses the Merge Controller to complete the process by moving the Enrollments, Attendance, Registrations, Contacts and Contributions and then deleting the duplicate record.
NOTE: The Merge Process does NOT move Membership or Related Families information. That must be handled using the normal process. Also, if the record you are keeping is not in the correct family, you will need to do that the normal way.
Merge Process – Part 1:
Once the duplicates have been identified, and the Manager knows which record to keep, he can start the merge.




Sample Email:
Subject: Duplicates
Admin,
Please complete the merge and delete the following:
http://test.bvcms.com/Merge?PeopleId1=864401&PeopleId2=896300
http://test.bvcms.com/Merge?PeopleId1=45811&PeopleId2=78945
2nd Sample Email:
Subject: Duplicates
Admin,
Please complete the merge and then delete the From Record for each of the following sets of records:
From Record = # 914448 To Record= # 906576
From Record = # 91578 To Record= # 458
HELPFUL HINT: On the Merge Controller page, the People ID #s for each of the records is a toggle link which will open a new tab for each person’s record. This allows you to keep 3 tabs open and move back and forth from the Merge Controller to viewing the full record for each person if you need to verify any information that is not included in the Merge Controller.
After receiving notification from the Manager, the system Admin will complete the Merge/Delete process as follows:
NOTE: If you are using the URL as described above, you will skip steps 1-3, as you will already be on the Merge Controller page with the correct records.

Note about roles.
Your System Admin should assign the Manager role to the person who will be responsible for moving this basic information. For most churches, this will probably be the New People Manager.
For some churches, this entire process outlines above will be handled by one person - identifying the duplicate, merging the basic information, merging the Enrollments, Contributions, etc. and ultimately deleting the duplicate record. If that is the case in your church, that person must have the Admin role.
However, these tasks can be divided so that one person (who does not have to be an Admin) can do the first part of the process – that is, identify the duplicate records and merge the basic information (Name, Contact Info, etc.). That person needs the Manager role in order to use the Merge portion of the Merge Controller.
The next part of the process must be done by the Admin. That is the final merging of Enrollment, Contributions, etc. and the deleting of the duplicate record. This can be done in one step. See above.