> For the complete documentation index, see [llms.txt](https://help.peoplevine.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.peoplevine.com/products/control-panel-overview/membership-management-hub/merge-profiles.md).

# How to Merge Duplicate Profiles

### Before you begin (Prerequisites)

* **Permissions**: You must be an **Administrator**, **Supervisor**, **Manager**, **Support**, or **Account Rep**. See: [How to Manage Users and Permissions](/products/control-panel-overview/admin-overview/manage-roles-permissions.md).
* **Preparation**: You have identified two profiles for the same person and determined which one should be the surviving record.

### Instructions

1. Use the **Search** icon (magnifying glass) in the top navigation bar. Type the name or email of the profile you want to merge **from** (the duplicate that will be retired) and select their profile.

> Alternatively, navigate to [**CRM > View People**](https://control.peoplevine.com/customers), search by name or email, click **APPLY**, and click the person's **Name**.

> **Note (Pro Dash):** Navigate to **CRM > People > View People**.

3. On the left-hand sidebar, scroll to the **Admin Tools** section and click **MERGE PERSON** (blue button).
4. The **"Who are you merging them with?"** page opens. In the **Assign this merge to** search field, search for the surviving profile by name or email.
5. Select the surviving profile from the results and click **USE THIS PERSON**.
6. The **Confirm Merge** page shows both profiles side by side:
   * **Merge This Profile** (left) — the profile being retired, with name, email, and touchpoint count.
   * **Into This Profile** (right) — the surviving profile, with email and touchpoint count.
   * Each side has a **VIEW PROFILE** button to review before confirming.
   * The page states: *"All of their \[X] TouchPoints and Activities will be migrated too."*
7. Click **MERGE ACCOUNTS** to complete the merge.

> **Warning**: Merging is permanent and cannot be undone. Review both profiles using the VIEW PROFILE buttons before clicking MERGE ACCOUNTS.

> **Preventing accidental merges**: If several members' profiles combined on their own — sometimes sharing the same payment details — the forms or applications were likely submitted by more than one person on the same device, where each new entry was saved onto the previous person's profile. Prevent this by enabling **Kiosk Mode**. See: [How to Create a Form](/products/control-panel-overview/forms-overview/create-form.md).

### Best Practice

Choose the profile with the active membership and the most complete data as the surviving record. After merging, add a staff note to the surviving profile recording the merge and the retired Customer ID for reference.

### What Happens Next

* **On the member side**: The member continues using the surviving profile's email for portal login. All touchpoints and activities from both profiles are consolidated under the surviving record.
* **Next step**: [How to Search for a Member](/products/control-panel-overview/membership-management-hub/search-member.md) or [How to Edit a Membership](/products/control-panel-overview/membership-management-hub/edit-membership.md).

*Last updated: 2026-05-24*


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://help.peoplevine.com/products/control-panel-overview/membership-management-hub/merge-profiles.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.