> For the complete documentation index, see [llms.txt](https://docs-vnext.kiflo.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs-vnext.kiflo.com/leads-deals/leads/copy-values-when-converting-lead-to-deal.md).

# How to copy values when converting a Lead to a Deal?

When you convert a lead into a deal, you can copy the values from the Lead to the Deal to avoid inputting the same information twice. We will show you how to do that!

## Copy values when converting a Lead to a Deal

Copying values when converting a Lead to a Deal is extremely simple. Follow these easy steps to get started:

First, you need to have the same properties on the Lead and Contact entity

* Go to **Account** and then click **Properties**
* Add missing Leads properties that you want to copy to the Contact entity. Ensure the Internal name is the same as the Lead entity. Otherwise, the value won’t be copied.

Once done, when you will convert a Lead to a Deal, the properties in the Lead matching the Contact’s internal name properties will be copied to the Deal. No more dual input!


---

# 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-vnext.kiflo.com/leads-deals/leads/copy-values-when-converting-lead-to-deal.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.