> 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-enterprise.md).
# MC to Enterprise
Transfer a Managed Company to a standalone Keeper Enterprise.
## Overview
Use Keeper Commander CLI to move a Managed Company (MC) from an MSP to a standalone Keeper Enterprise.
{% hint style="warning" %}
**Please first contact Keeper's Support team to initiate your MSP or MC transfer.**
MSP Americas & APAC: \
MSP EMEA:
After approval, use Keeper Commander to request a transfer of your MC.
{% endhint %}
**Scenario:** The MC starts the departure. The MSP does not accept it. Keeper Security reviews it. The MC 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 currently managed by an MSP |
| **Leaving MC** | The Managed Company that wants to become a standalone Enterprise |
#### Example Accounts Used in This Guide
Replace these examples with the administrator names and email addresses in your environment.
| Role | Admin Name | Admin Email |
| ---------------- | ----------- | ----------------------- |
| Leaving MC Admin | `mc-admin` | `mc-admin@example.com` |
| MSP Admin | `msp-admin` | `msp-admin@example.com` |
## Prerequisites
* Keeper Commander CLI is installed and configured.
* You are the **Principal Admin** for the departing Managed Company.
* You have the current MSP administrator's name and email address.
## Step 1 — MC: Initiate the Departure
The Managed Company admin logs in to Commander and submits a request to leave the MSP.
**1. Log in to Commander as the MC admin:**
```
Email: mc-admin@example.com
Password:
```
**2. Submit the leave request:**
```
mc-transfer leave-msp
```
**3. Verify the request was submitted:**
```
mc-transfer status
```
The status should show the departure request is pending.
## Step 2 — MSP: No Action Required
The MSP does **not** accept or approve the request. The process moves directly to legal approval.
{% hint style="info" %}
**For MSP administrators:** Keeper Security's legal team contacts you during approval. No Commander action is required.
{% endhint %}
## Step 3 — Legal Approval
After the MC submits the request, Keeper Security emails both administrators.
* Provide any information Keeper requests.
* Keeper approves or denies the departure.
* 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 — MC: Complete the Departure
After Keeper approves the transfer, the MC administrator completes it in Commander.
**1. Log in to Commander as the MC admin:**
```
Email: mc-admin@example.com
Password:
```
**2. Confirm legal approval status:**
```
mc-transfer status --target-name "msp-admin" --target-email msp-admin@example.com
```
**3. Perform the transfer:**
```
mc-transfer perform --target-name "msp-admin" --target-email msp-admin@example.com
```
The Managed Company is now a standalone Enterprise.
## Command Reference Summary
| Step | Who Runs It | Command |
| ------------------ | ----------- | ------------------------------------------------------------------------------ |
| Initiate departure | MC Admin | `mc-transfer leave-msp --target-name "" --target-email ` |
| Check status | MC Admin | `mc-transfer status --target-name "" --target-email ` |
| Complete departure | MC Admin | `mc-transfer perform --target-name "" --target-email ` |
{% hint style="info" %}
There is no `accept` step for this scenario — the MSP does not need to take any Commander action for an MC departure.
{% 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://docs.keeper.io/enterprise-guide/keeper-msp/migration-of-mcs/mc-to-enterprise.md?ask=&goal=
```
`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.
