# Copy data between entities

Sometimes data isn’t just relevant to one entity. For example, the industry value could be relevant to the company and the job. Having this type of information readily available can save time and help you get a clearer view of opportunities, such as easily seeing how many jobs you have open in a specific industry.

**But how often does this information actually get copied between records?**\
\
We know manual data entry is time consuming, and we also know that incomplete data impacts your reporting and integrations that rely on data, such as Bullhorn Automation. And that’s why we added the copy functionality to Kyloe DataTools.

<details>

<summary><strong>Fix it with Kyloe DataTools</strong></summary>

**Automatically copy information between associated records**. This could be populating invoice formatting from company to placement, bill rates from job to placement, copying placement information to candidate record, among others!

</details>

<details>

<summary><strong>How will it impact your business?</strong> </summary>

This one is not only a massive time-saver, but also enables your team to work smarter. In addition to the improvements to efficiency, you’ll also benefit from more insightful reporting and be able to make more informed decisions.&#x20;

</details>

#### Interactive demo

{% embed url="<https://app.arcade.software/share/DwmCnKcDmA1RWpJYplId>" %}

{% hint style="success" %}
**You can run data updates over night with scheduled rules. ⏰**&#x20;

**And revert any unwanted changes within 30 days.  🔙**&#x20;
{% endhint %}


---

# Agent Instructions: 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:

```
GET https://help.kyloepartners.com/kyloe-datatools/data-management-playbook/gather-enrich-your-data/copy-data-between-entities.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.