How duplicates are found
Two or more people are shown together as a group when they have:
The email and phone compared are each person’s main ones. People who are archived or deleted are not checked. Names are not compared on their own, and there is no near-match: “Jon” and “John” are not a match.
A person can appear in more than one group, once for their email and once for their name and phone. When nothing matches, the page says No likely duplicates found.
Each group lists its people by name, with their email (or no email). Click a name to open that record and check before you merge.
Merging two people
Beside each person in a group is a button for every other person in it, reading Keep this, merge followed by the other person’s name. The person on that row is the one you keep; the named person is merged into them. You are asked to confirm first.What moves to the person you keep
Their history. Everything the merged-in record was attached to becomes the kept record’s:- donations, and anything they fulfilled from your wish list;
- adoptions, applications, placements, contracts they signed, and animals they surrendered or took home;
- their foster home, affiliations and housing;
- volunteer bookings and qualifications;
- the email they were sent or sent you, as recorded in the communications log, and their communication preferences, including an opt-out;
- notes and tags, and their email addresses, phone numbers and addresses: where the record you keep has a main one of its own, it stays the main one and theirs come along as extra ones;
- tasks assigned to them, tasks about them, and work recorded against their name;
- the transports they drove, whole runs as well as single legs, and the animal records naming them as the vet who altered an animal;
- what they approved or decided for somebody else: hours signed off, a qualification granted, a cancellation answered, a form submission decided, an auction lot collected;
- documents and files kept on their record;
- the pets on their pet food pantry record, and their pantry visits;
- the pets of their own on their record, which a clinic books in, with their bookings;
- conversations linked to them in the inbox, and any submission linked to them;
- any checklist still running on them, unless the kept record already has that same checklist open, in which case it stays on the archived record with the rest.
What does not move
How they sign in. A login, its password, its recovery codes and the roles that go with it stay exactly where they are. Merging two people who look alike is not a way to give one of them another’s access, and if the two records really are one person with a login, invite them again from Settings → Team. So a merge that would archive the record somebody signs in with, into a record that has no sign-in, is refused with the reason: merge the other way, keeping the record they sign in with. Who did what, on the records that exist to say so. Sign-in history, the settings history and support access keep the name they were recorded under. An audit line that changed when somebody tidied a duplicate would not be an audit line. Anything done by the system rather than by a person. Where an approval or a decision was made automatically, the record says so and keeps saying so: a merge only ever rewrites the name of the person being merged in. Notices already sent. A notice in somebody’s bell names the person as they were written: Kim assigned you a task about Adah Rogers. Its link keeps pointing at the record named in it, which still opens. The kept record’s own details. Beyond what moves to it above, it is not changed by the merge: its name, its main email, phone and address and its custom fields stay as they were. The one exception is Do not adopt: if the record merged in was marked, the record you keep is marked too. Before you merge, compare the two and add to the one you keep anything it is missing.A few things can only exist once for a person: one communication preference per channel, one place on a booking, one tag of the same name, one foster home. Where the kept record already has one, the merged-in record keeps its own rather than overwriting it, and you can read it on the archived record.
What happens to the other record
It is not deleted. Its status is set to Archived, so it leaves the duplicates page, and it keeps everything that did not move. It remembers the record it was merged into, so when an import from RescueGroups brought it in, the next import updates the record you kept and leaves the archived one archived. You can still find it in the people list by filtering on Status archived.Merging does not touch sign-ins. If the merged-in person can sign in to RescueConsole, they still can: remove their access under Settings → Team & volunteers → Team members if they should not.

