> For the complete documentation index, see [llms.txt](https://docs.keeper.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.keeper.io/enterprise-guide/keeper-msp/migration-of-mcs/mc-to-msp.md).

# MC Transfers Between MSPs

Transferring MCs Between MSPs

## Overview

Use Keeper Commander CLI to transfer one or more Managed Companies (MCs) between MSPs.

{% hint style="warning" %}
**Please first contact Keeper's Support team to initiate your MSP or MC transfer.**<br>

MSP Americas & APAC: <mspteamna@keepersecurity.com>\
MSP EMEA: <MSPTeamEMEA@keepersecurity.com>

After approval, use Keeper Commander to request a transfer of your MC.
{% endhint %}

**Scenario:** The Sending MSP starts the transfer. The Receiving MSP accepts it. Keeper Security reviews it. The Sending MSP completes it.

**Command reference:** [Commander CLI and SDK](/enterprise-guide/keeper-msp/commander-cli-sdk.md)

## Terminology

| Term              | Definition                                                                       |
| ----------------- | -------------------------------------------------------------------------------- |
| **MSP**           | Managed Service Provider — a Keeper Security tenant that manages other companies |
| **MC**            | Managed Company — a Keeper Security tenant that is managed by an MSP             |
| **Sending MSP**   | The MSP that currently owns the MCs being transferred                            |
| **Receiving MSP** | The MSP that will take ownership of the MCs                                      |

#### Example Accounts Used in This Guide

Replace these examples with the administrator names and email addresses in your environment.

| Role                | Admin Name            | Admin Email                       |
| ------------------- | --------------------- | --------------------------------- |
| Sending MSP Admin   | `sending-msp-admin`   | `sending-msp-admin@example.com`   |
| Receiving MSP Admin | `receiving-msp-admin` | `receiving-msp-admin@example.com` |

## Prerequisites

* Keeper Commander CLI is installed and configured.
* You are the **Principal Admin** for the Sending or Receiving MSP.
* You have the Receiving MSP administrator's name and email address.

## Step 1 — Sending MSP: Initiate the Transfer

The Sending MSP admin logs in to Commander and sends a transfer request to the Receiving MSP.

**1. Log in to Commander as the Sending MSP admin:**

```
Email: sending-msp-admin@example.com
Password: <your password>
```

**2. Initiate the transfer:**

```
mc-transfer join-msp --target-name "receiving-msp-admin" --target-email receiving-msp-admin@example.com
```

**3. Verify the transfer request was sent:**

```
mc-transfer status --target-name "receiving-msp-admin" --target-email receiving-msp-admin@example.com
```

The status should show the transfer request is pending acceptance by the Receiving MSP.

<figure><img src="https://4290574019-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LO5CAzpxoaEquZJBpYz%2Fuploads%2FyimXCchfdTQ3NQO9DjLb%2FStep%201%20-%20Sending%20MSP%20Initiate%20the%20Transfer.jpg?alt=media&amp;token=48109380-0ae7-4a2c-9dbd-3e48da73a178" alt=""><figcaption></figcaption></figure>

## Step 2 — Receiving MSP: Accept the Transfer

The Receiving MSP admin logs in and accepts the inbound transfer request.

**1. Log in to Commander as the Receiving MSP admin:**

```
Email: receiving-msp-admin@example.com
Password: <your password>
```

**2. Check the incoming transfer request:**

```
mc-transfer status --target-name "sending-msp-admin" --target-email sending-msp-admin@example.com
```

**3. Accept the transfer:**

```
mc-transfer accept-mc --target-name "sending-msp-admin" --target-email sending-msp-admin@example.com
```

**4. Confirm acceptance:**

```
mc-transfer status --target-name "sending-msp-admin" --target-email sending-msp-admin@example.com
```

The status should show that the transfer is accepted and awaiting legal approval.

<figure><img src="https://4290574019-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LO5CAzpxoaEquZJBpYz%2Fuploads%2FSsOWdJ1GTBFfk9bJIQ2i%2FStep%202%20-%20Receiving%20MSP%20Accept%20the%20Transfer.jpg?alt=media&amp;token=eb9983b1-ab3d-4757-9e56-247b383dec7e" alt=""><figcaption></figcaption></figure>

## Step 3 — Legal Approval

After both parties agree, Keeper Security's legal team emails both MSPs.

* Provide any information Keeper requests.
* Keeper approves or denies the transfer.
* Keeper emails both parties with its decision.

{% hint style="info" %}
There is no action required in Commander during this step. Wait for legal approval before proceeding.
{% endhint %}

## Step 4 — Sending MSP: Complete the Transfer

After Keeper approves the transfer, the Sending MSP administrator completes it in Commander.

**1. Log in to Commander as the Sending MSP admin:**

```
Email: sending-msp-admin@example.com
Password: <your password>
```

**2. Confirm legal approval status:**

```
mc-transfer status --target-name "receiving-msp-admin" --target-email receiving-msp-admin@example.com
```

**3. Perform the transfer:**

```
mc-transfer perform --target-name "receiving-msp-admin" --target-email receiving-msp-admin@example.com
```

The Managed Companies are now transferred to the Receiving MSP.

<figure><img src="https://4290574019-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LO5CAzpxoaEquZJBpYz%2Fuploads%2F9fcpIoZgQniuj9QyzXkG%2FStep%204%20-%20Sending%20MSP%20Complete%20the%20Transfer.jpg?alt=media&amp;token=1cd7e20e-b12c-4fd9-8070-09cad15f7815" alt=""><figcaption></figcaption></figure>

## How to Cancel a Transfer

If you need to cancel a pending transfer **before** legal approval, the Sending MSP admin can run:

```
mc-transfer cancel --target-name "receiving-msp-admin" --target-email receiving-msp-admin@example.com
```

Cancel the transfer **before** Keeper approves it. This command cannot reverse a completed transfer.

## Command Reference Summary

| Step              | Who Runs It   | Command                                                                                   |
| ----------------- | ------------- | ----------------------------------------------------------------------------------------- |
| Initiate transfer | Sending MSP   | `mc-transfer join-msp --target-name "<receiving-admin>" --target-email <receiving-email>` |
| Check status      | Either party  | `mc-transfer status --target-name "<other-admin>" --target-email <other-email>`           |
| Accept transfer   | Receiving MSP | `mc-transfer accept-mc --target-name "<sending-admin>" --target-email <sending-email>`    |
| Complete transfer | Sending MSP   | `mc-transfer perform --target-name "<receiving-admin>" --target-email <receiving-email>`  |
| Cancel transfer   | Sending MSP   | `mc-transfer cancel --target-name "<receiving-admin>" --target-email <receiving-email>`   |


---

# 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.keeper.io/enterprise-guide/keeper-msp/migration-of-mcs/mc-to-msp.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.