This page is for admins who make Buttons.

A transfer copies a Button from the OneClick of one Pipedrive company to the OneClick of another Pipedrive company.
For example, you make and test a Button in a sandbox company, and then you transfer it to your production company.

- The **source company** has the Button.
- The **target company** gets the copy.

The Button in the source company does not change. A transfer works for all Button types.

## Make a transfer-enabled API key in the target company

Do these steps in the OneClick of the target company.

1. Click **Settings** at the bottom of the OneClick Panel.
2. Click the **Settings** tab.
3. Click **API Keys** in the menu at the left.
4. Click **Create New API Key**.
5. Type a name for the key in **Label**.
6. Turn on **Allow button transfers from other organizations**. OneClick shows a warning: the source company sees the
   label of this key in its transfer history.
7. Click **Create**. The list shows the key with **(Transfers allowed)** after its label.
8. Click the copy icon at the right of the key. OneClick copies the key to the clipboard.

Keep the key secret. Each person who has the key can transfer Buttons to your company. To stop this, click **Delete**
at the right of the key.

## Transfer the Button from the source company

Do these steps in the OneClick of the source company.

1. Open the Settings and click **Edit** on the Button. See [Manage Buttons](/docs/buttons/manage-buttons).
2. Click **Transfer** in the menu at the left. A new Button has no **Transfer** item. Save the Button first.
3. Paste the key in **Target Organization API Key**.
4. Click **Transfer Button**. OneClick shows **Button successfully transferred to** and the name of the target company.

![The Transfer section of the Button editor. Target Organization API Key has a key, and Transfer Button is available.](https://res.cloudinary.com/zimple/image/upload/f_auto,q_auto/oneclick-docs/buttons/transfer-a-button/transfer-api-key.png)

You cannot undo a transfer. To remove the copy, delete it in the target company.

**Transfer History** shows each transfer of the Button: the target company, the label of the API key, the person
who transferred it and the date.

## Examine the copy in the target company

The copy is in the Buttons list of the target company, on the same tab as the original: **Panel** or **Floating
window**. It has the name of the original with "(transferred)" at the end. If a Button with this name is already in
the list, OneClick adds a number, for example "(transferred 1)". The copy is not in a group.

The **Button** section of the copy shows **Transfer Origin**: the source company, the API key, the person who
transferred the Button and the date.

Some settings belong to the source company. OneClick does not copy them. Before you use the copy, do these checks:

- **Headers.** OneClick does not copy the header values. Each header has the value "Set your own value", and no
  header is confidential. Type the correct values and make the headers confidential again.
- **Limit visibility.** OneClick removes the pipelines, the stages, the users and the groups. The scopes stay. Set the
  limits again. See [Limit visibility](/docs/buttons/limit-visibility).
- **Pipedrive custom fields.** A custom field of the source company is not in the target company. Select the correct
  field in the target company again.
- **Filter fields and user fields.** OneClick clears the allowed filters and the default values of filter fields, and
  the default values of user fields. Set them again.
- **Signed link.** OneClick does not copy the secret of a Signed link. Make a new secret.
- **Interface variables.** OneClick does not copy the values of confidential Interface variables. Type them again.

## Errors

| Message                                    | Cause                                                                              |
| ------------------------------------------ | ---------------------------------------------------------------------------------- |
| **Invalid API key**                        | No OneClick API key has this value. Copy the key again.                            |
| **API key does not allow button transfers** | The key does not have **Allow button transfers from other organizations**. Make a new key. |
| **Cannot transfer to same organization**   | The key belongs to the source company. Use a key of the target company.            |
| **Too many transfer!**                     | One company can do a maximum of 30 transfers to the same target company in 24 hours. |