> 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/jobs/merge-duplicate-jobs.md).

# Merge duplicate jobs

Combine two jobs for the same work at one property. Choose which job to keep, review the records being combined, then archive the duplicate.

> **Where to find it:** **Scheduling > Jobs > open a job > Job actions (⋮) > Merge job**.

You need the **Merge & Split Customers** role permission. Both jobs must be at the same property, and the job you keep must be open.

## Merge the jobs

1. Open the duplicate job and choose **Merge job** from **Job actions**.
2. Search for the **Job to keep** by job number or visit type. The picker lists other jobs at this property, newest first.
3. Check the direction. **Switch Direction** swaps which job is kept and which is archived.
4. Select **Next** to review the records being combined.
5. Select **Merge**. Essential opens the surviving job.

## What is kept

The surviving job keeps its job number and closure history. Visits move to it with their schedules, technicians, clock records, inspection reports, and service history.

Job files, linked quotes, invoices, and purchase orders, manual labor entries, and tasks linked to the job move to the surviving job. **Parts, Labor & Items** rows, cost items, and manual revenue are combined; the same planned item's quantities are added together. Quote and invoice amounts are unchanged. If you use invoice field rules, draft invoices whose fields follow job fields are refreshed from the surviving job; the review lists them.

If only the archived job has expected hours, its estimate carries over. If both jobs have estimates, the surviving job’s estimate is kept; the review flags different estimates.

Source-only custom field values carry over, including into a field that is blank on the surviving job. When both jobs have a value for the same field, the surviving job's value wins. Personal to-dos linked to the archived job open the surviving job. If a file, quote, invoice, or purchase order is already linked to both jobs, it stays linked to the surviving job once. The review lists these overlaps before you merge.

Each job keeps at most one job summary. If only the archived job has one, it moves to the surviving job with its share link. If both have one, the surviving job's summary is kept.

The duplicate is archived and disappears from the Jobs list. Already-deleted records remain with the archived job. The surviving job's timeline includes the archived job's history and records the merge. Merging cannot be undone in the app.

## When a merge needs another review

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

Essential also stops the merge, leaving both jobs unchanged, when:

* Either job has a project, even if the project is turned off. Project records and billing cannot be combined through job merge.
* A technician is clocked into one of the archived job's visits. Have them clock out first.
* The job you want to keep is closed. [Reopen it](https://learn.withessential.com/customers-and-work/jobs/close-or-reopen-a-job.md) first.
* The archived job has parts reserved or used, or other inventory activity. Switch direction to keep that job instead, or contact support if both jobs have parts.
* Both jobs have a job summary and the archived job's summary has been shared. Switch direction to keep that job, or contact support.
* Invoice lines record the archived job as their source for revenue accounting (used with job-based revenue account rules). Switch direction to keep that job, or contact support.
* An item is planned in one job's **Parts, Labor & Items** but recorded as used on the other job's completed visit. After merging, invoices would bill only the recorded usage, so record the actual usage on the planned job's visit or remove the planned row first.
* The archived job's visits or linked tasks have unfinished automated outreach, such as a pending visit reminder. Contact support to reconcile that outreach before merging.
* Customer workflows are still queued or running for the archived job, for example one waiting for approval. Wait for them to finish, or contact support.

Related: [Close or reopen a job](https://learn.withessential.com/customers-and-work/jobs/close-or-reopen-a-job.md), [merge duplicate properties](https://learn.withessential.com/customers-and-work/properties/merge-duplicate-properties.md), [why can't I delete a job?](https://learn.withessential.com/customers-and-work/jobs/why-cant-i-delete-a-job.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/jobs/merge-duplicate-jobs.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.
