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

# Enterprise to MSP

Transfer a standalone Enterprise to an MSP as a Managed Company.

## Overview

Use Keeper Commander CLI to transfer a standalone Keeper Enterprise tenant to an MSP as a Managed Company (MC).

{% 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 Enterprise.
{% endhint %}

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

**Command reference:** [Commander CLI and SDK](/en/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 managed by an MSP                     |
| **Enterprise**    | A standalone Keeper Security tenant (not currently managed by any MSP)           |
| **Receiving MSP** | The MSP that will take ownership of the Enterprise as an MC                      |

#### Example Accounts Used in This Guide

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

| Role                | Admin Name            | Admin Email                       |
| ------------------- | --------------------- | --------------------------------- |
| Enterprise Admin    | `enterprise-admin`    | `enterprise-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 Enterprise or Receiving MSP.
* You have the Receiving MSP administrator's name and email address.

## Step 1 — Enterprise: Initiate the Transfer

The standalone Enterprise admin logs in to Commander and sends a request to join the MSP.

**1. Log in to Commander as the Enterprise admin:**

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

**2. Initiate the transfer request:**

```
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 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%2FZmzpfGZBYIFnbSQk1w7R%2FStep%201%20-%20Enterprise%20Initiate%20the%20Transfer.jpg?alt=media&amp;token=e61099d9-b8e2-4cb2-8b63-881b7614bd57" alt=""><figcaption></figcaption></figure>

## Step 2 — Receiving MSP: Accept the Transfer

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

**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 "enterprise-admin" --target-email enterprise-admin@example.com
```

**3. Accept the transfer:**

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

**4. Confirm acceptance:**

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

The status should now reflect that the transfer is accepted and pending legal approval.

<figure><img src="https://4290574019-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LO5CAzpxoaEquZJBpYz%2Fuploads%2FQrWj3Tq8Jxcl6sjjFlzm%2FStep%202%20-%20Receiving%20MSP%20Accept%20the%20Transfer.jpg?alt=media&amp;token=df1873e7-d98c-4206-bae7-2e71be238426" alt=""><figcaption></figcaption></figure>

## Step 3 — Legal Approval

After both parties agree, Keeper emails the Enterprise and Receiving MSP administrators.

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

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

## Step 4 — Enterprise: Complete the Transfer

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

**1. Log in to Commander as the Enterprise admin:**

```
Email: enterprise-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 Enterprise is now a Managed Company under the Receiving MSP.

<figure><img src="https://4290574019-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LO5CAzpxoaEquZJBpYz%2Fuploads%2Fyl0pQbGkAppbi4TQCWoL%2FStep%204%20-%20Enterprise%20Complete%20the%20Transfer.jpg?alt=media&amp;token=8779c2a3-8e1d-44b3-92bf-2943dc4f10f0" alt=""><figcaption></figcaption></figure>

## How to Cancel a Transfer

The Enterprise cannot cancel a submitted request. Only the Receiving MSP can cancel the transfer.

To cancel, the Receiving MSP admin must:

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

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

**2. Cancel the transfer:**

```
mc-transfer cancel --target-name "enterprise-admin" --target-email enterprise-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 | Enterprise         | `mc-transfer join-msp --target-name "<msp-admin>" --target-email <msp-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 "<enterprise-admin>" --target-email <enterprise-email>` |
| Complete transfer | Enterprise         | `mc-transfer perform --target-name "<msp-admin>" --target-email <msp-email>`                 |
| Cancel transfer   | Receiving MSP only | `mc-transfer cancel --target-name "<enterprise-admin>" --target-email <enterprise-email>`    |

{% hint style="warning" %}
**Important:** In this scenario, only the Receiving MSP can cancel the transfer. The Enterprise cannot cancel an outbound request it has already submitted.
{% endhint %}


---

# 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://newdocs.keeper.io/en/enterprise-guide/keeper-msp/migration-of-mcs/enterprise-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.