> For the complete documentation index, see [llms.txt](https://docs.fieldmotion.com/fieldmotion-api-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.fieldmotion.com/fieldmotion-api-docs/customers/_merge.md).

# \_merge

Moves the jobs, contracts and files from one customer to another, then deletes the customer which the data was copied from.

### Parameters

#### from

The ID of the Customer you wish to move the jobs, contracts and files from, and which will then be deleted.

#### to

The ID of the Customer you wish to move the jobs, contracts and file to.

### Example

```
FM_api('Customers_merge',[
  'from'=>'683068',
  'to'=>'683069'
  ]
);
```

### Results

#### On Success

```
{"ok":1,"warnings":[]}
```

It is possible to receive a warning here if the removed Customer is also linked to another database (e.g Quickbooks), so it will need to be manually removed there in such case.

#### On Failure

If the "from" parameter does not have a set value or has a value less than 1:

```
{"error":"missing or invalid parameter: from"}
```

If the "to" parameter does not have a set value or has a value less than 1:

```
{"error":"missing or invalid parameter: to"}
```

If the "from" and "to" parameters have the same value:

```
{"error":"parameters must have different values: from, to"}
```

If neither parameters match the IDs of existing Customers OR only 1 of the parameters matches the ID of an existing Customer:

```
{"error":"both customers must exist in order to merge them"}
```


---

# 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://docs.fieldmotion.com/fieldmotion-api-docs/customers/_merge.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.