Transfer an Organization Between Accounts
Huntress Managed Endpoint Detection and Response (EDR) supports seamless account transfers when a new partner or MSP takes over client management.
In this article:
Overview
This guide walks partners through transferring a customer organization from one Huntress partner account to another.
For Huntress Managed Endpoint Detection and Response (EDR), existing Agents do not need to be uninstalled or reinstalled. Huntress coordinates the transfer internally to minimize operational disruption.
Before You Begin
Before submitting a transfer request, collect the following details:
The customer organization name in Huntress
The sending partner account name and details
The receiving partner account name and details
The specific organization or organizations you want to transfer
Written approval from an authorized Admin for both the sending and receiving accounts
The preferred date for the transfer
Relevant context regarding current Huntress products, billing dates, or contract schedules
Transfer Process
Reach out to your Huntress Channel Account Manager (CAM) or Account Manager when both parties are ready to schedule the move.
Provide your CAM with the customer name, account details, partner approvals, and target transfer date.
Huntress verifies written authorization from authorized Admins for both partner accounts. Huntress might request end-customer confirmation if necessary.
Your CAM coordinates timing and submits the transfer request through internal workflows. Submit requests close to your target transfer date so account details stay current.
Huntress moves the organization to the receiving account. Your CAM will keep you updated and notify you when the transfer is complete.
-
Log in to the receiving partner account to perform the following checks:
Confirm that the organization appears in the correct account.
Verify that Agents and expected telemetry are present.
Review policies, exclusions, users, and notifications.
Confirm the operational health of integrations and services.
Transferred Data and Settings
For Managed EDR transfers, Huntress automatically moves the following items:
Agents associated with the organization
Related incident reports
Telemetry collected from Agents
Organization-level settings, including Managed Antivirus policies and exclusions
Organization users
Managed SIEM data tied to moved Agents
Note: Account-level exclusions and configurations do not transfer automatically.
Service and Integration Considerations
Important: Review this section before making any changes, and do not take action until you consult your CAM.
Integrations for Microsoft 365, Microsoft Defender for Endpoint, and Managed Security Awareness Training (SAT) sub-accounts require specific handling during an account transfer:
Identity and Third-Party Integrations: Disconnect identity integrations, such as Huntress Managed Identity Threat Detection and Response (ITDR), from the sending account before the move. Reconnect them under the receiving account after the move.
Managed Security Awareness Training (SAT) Sub-Accounts: Map SAT sub-accounts to their corresponding Huntress organization before initiating the move. For example, if Partner A has an SAT company named "Supermarket," map it to the "Supermarket" organization before transferring from Partner A to Partner B.
Additional Guidance: Your CAM will walk you through the specific requirements for your environment and help coordinate any additional tasks.
Frequently Asked Questions
Do we need to uninstall and reinstall Huntress Agents—or start from scratch?
No. For Managed EDR organization transfers, existing Agents remain installed. Your CAM will confirm the best approach for your environment.
Who must approve the transfer?
Written approval is required from authorized Admins for both the sending and receiving partner accounts. Huntress might request additional customer confirmation when appropriate.
Can the transfer happen immediately?
No. Transfers require coordination, authorization, and validation before completion. Share your preferred date early to ensure proper planning.
What should we do if an integration is not working after the transfer?
Integration behavior can vary by data source type. Many SIEM API and HTTP Event Collector (HEC) sources are configured at the account level, so do not assume they transfer with an organization; your CAM or Huntress Support can confirm whether you need to remap or reconnect them. For operating system and syslog sources, verify the collector and source mappings after the move.
Historical SIEM data is generally retained during an organization move, but older logs might not be immediately searchable in the destination account and could require rehydration. The destination account also needs an active SIEM trial or subscription for the data to move over. If a source stops reporting, contact your Account Manager or Huntress Support with the organization name, affected source type, and error details.
What happens if we uninstall and reinstall the Huntress Agent?
Reinstalling is generally not needed for a Managed EDR organization transfer because existing Agents remain installed. Uninstalling an Agent can interrupt endpoint protection until reinstalled, so only do this if your CAM confirms it is required for your environment.
Next Steps
Contact your Huntress Account Manager or CAM with the customer organization name, current and receiving partner details, required approvals, and preferred transfer date to initiate the process.