> For the complete documentation index, see [llms.txt](https://learn.withessential.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://learn.withessential.com/customers-and-work/properties/merge-duplicate-properties.md).

# Merge duplicate properties

Combine two records for the same location under one customer. Choose which property to keep, review the records and contact roles, then archive the duplicate.

> **Where to find it:** **Customers → Properties → open a property → More actions (⋮) → Merge Property**.

You need the **Merge & Split Customers** role permission. Both properties must belong to the same customer, and the surviving property and customer must be active.

## Merge the records

1. Open the duplicate property and choose **Merge Property** from **More actions**.
2. Search for the **Property to keep**. The picker includes other properties under this customer.
3. Check the direction. **Switch Direction** swaps which property is kept and which is archived.
4. Select **Next** to review the records being combined and the surviving property's billing address.
5. Review contact roles. Existing roles are retained, with the surviving property's primary contacts selected by default. To change a priority, remove its role chip and select that role again. A primary priority already held by another contact is unavailable until that contact is made secondary. Each existing role needs a priority before you can merge.
6. Select **Merge**. Essential opens the surviving property.

## What is kept

The surviving property keeps its address, billing settings, phone number, and office. Its notes and access information are kept, with the duplicate's information appended and labeled by its original address.

Asset groups move together with their existing assets, schedules, and service history. Jobs, quotes, invoices, subscriptions, tasks, inspection reports, files, and other supported linked records move to the surviving property. Existing financial amounts and document contents are preserved.

Source-only custom fields, custom prices, and rate sheets move over. When both properties have the same setting, the survivor's value wins. Existing survivor rate sheets retain pricing precedence. The review identifies overlapping settings before you merge.

The duplicate is archived and disappears from property lists. Already-deleted records and frozen audit history remain with the archived record. The survivor's timeline records the merge. Merging cannot be undone in the app.

## When a merge needs another review

If either property changes after you select **Next**, Essential stops the merge. Select **Back**, review the latest data, and try again.

Properties with unfinished automated outreach, or a source property with Compliance Engine registrations, filings, or job approval forms, need support to reconcile those records before merging. The dialog explains the blocker and leaves both properties unchanged.

To combine records under different customers, first [move the property to the correct customer](/customers-and-work/properties/move-a-property-to-another-customer.md).

Related: [Use Customer Billing or set Property Billing](/customers-and-work/properties/property-billing-profile-the-customer-default-or-its-own.md), [merge or split customer accounts](/customers-and-work/customers/merge-or-split-customer-accounts.md).


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://learn.withessential.com/customers-and-work/properties/merge-duplicate-properties.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.