---
title: "Ability to Merge Customers"
slug: "ability-to-merge-customers"
updated: 2025-08-29T09:51:09Z
published: 2025-08-29T09:51:09Z
canonical: "zenoplesupport.aqore.com/ability-to-merge-customers"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://zenoplesupport.aqore.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Ability to Merge Customers

## Added Customer Merge Utility

This feature introduces a new Customer Merge utility report within the Zenople RMS module. It enables users to consolidate duplicate customer records by merging all data from an inactive (bad) customer into an active (good) one. The update focuses on data integrity, providing robust validation to prevent accidental data loss and ensuring a complete audit trail of the merge operation. This utility is essential for maintaining a clean and accurate customer database.

The listed entities are merged from inactive to active customers:

- Contacts
- Tasks
- Comment
- Invoice (Include exception in Report)
- Transaction (Include exception in Report)
- Assignment, Assignment Schedule
- Jobs, (Scheduled, Temp, Direct Hire).
- Documents
- People
- Address
- Markups
- WC Code
- Job Position
- Shift
- Organization Payment
- Customer Adjustment
- Customer Requirement
- Customer Exclude
- Customer Candidate
- Job Candidate
- Revenue Opportunity
- Purchase Order

### Feature Overview

- A new "Customer Merge" utility has been added to the RMS module. To access the customer merge utility, go to RMS and select the utility icon in report category in top bar.
- The report interface includes two input parameters:
  - Active Customer ID
  - Inactive Customer ID
- The report generates a detailed output log showing the success of the merge for each entity and lists any exceptions that require manual review.
- A backend process has been created to transfer all related entities from the inactive customer to the active customer. This includes Contacts, Tasks, Jobs, Assignments, Documents, and all other listed data.
- **Contact Deduplication:** Specific logic has been added to handle contact conflicts. If a contact from the inactive customer already exists for the active customer, the moved contact is set to Inactive instead of creating a duplicate.
- **Bad Customer Handling:** The system now displays customer names identified as "bad" with a zzz prefix (e.g., zzzPepsi) in the backend processing logs.
- **Audit Logging:** A comment is automatically added to both the active and inactive customer records post-merge: *"#InactiveCustomerName(#InactiveCustomerID) merged into #ActiveCustomerName(#ActiveCustomerID) by #MergedUserId"*

### Exceptions

The following exceptions and validations are implemented to ensure a safe merge process:

**Invalid Customer ID:**

- **Validation:** The system verifies that both provided Customer IDs exist in the database.
- **Exception Message:** If invalid, the process halts and an exception toaster is displayed: **"Customer ID #CustomerID is invalid."**

**Child Department Exists:**

- **Validation:** The system checks if the inactive customer has any child departments.
- **Exception Message:** If child departments are found, the process is blocked and a severe exception message is shown: **"Bad Customer #ID, #Name, has child departments please move or transfer the departments first before merging."**