---
title: "Transferring site ownership "
date: "2025-11-25T21:44:09+00:00"
summary: "Securely transfer site ownership between organizations in Acquia Source. Streamline agency workflows and manage entitlements efficiently."
image:
type: "page"
url: "/acquia-source/transferring-site-ownership"
id: "a935078d-cb40-4e01-aceb-eab166ef166a"
---

Acquia Source allows organization administrators to securely transfer site ownership from one organization to another. This feature streamlines agency workflows, supports privacy during development.

### Use cases

The following table describes common scenarios for transferring site ownership:

**Scenario**

**Description**

****Agency handoff****

Agency partners develop sites privately and transfer them to client organizations upon completion.

****Sales transitions****

Internal teams or pre-sales create demo sites and transfer ownership to customers after purchase.

****Template acceleration****

Partners use agency templates to accelerate site builds, then transfer completed sites to clients.

### Prerequisites

Before initiating a transfer, ensure the following requirements are met:

*   ****Administrative permissions****: Only users with admin permissions can initiate or receive a site transfer.
    
*   ****Site entitlements****: The recipient organization must have an available site entitlement.
    
*   ****Valid recipient****: The recipient must have a valid, registered email address associated with an organization.
    

Transferring site ownership
---------------------------

### Step 1: Initiate the transfer

Note

Acquia DXP connectivity is invalidated after a site transfer for privacy reasons, and the recipient must manually authenticate each DXP integration after accepting the transfer.

1.  Log in to [Acquia Source](https://source.acquia.com/) to open the Sites Dashboard.
    
2.  On the **Sites** tab, locate the site that you want to transfer.
3.  Click the Kebab menu icon on the site card.
4.  Select **Transfer Ownership**.
5.  Enter the email address of the recipient organization and click **Continue**. 
    
    Note
    
    Acquia Source does not validate the recipient email address. The sender must ensure that the email address belongs to a valid organization and verify the transfer with the recipient. 
    
6.  Click **Transfer Ownership** to confirm the transfer request.

### Step 2: Recipient acceptance

1.  The recipient receives a notification through Sites Dashboard.
2.  The recipient must accept the transfer for it to complete. 
    
    If the recipient declines or does not respond, the sender can cancel the transfer.
    

### Step 3: Completion and entitlement changes

*   After the recipient accepts the invitation, Acquia Source moves the site to the recipient organization.
*   This action consumes the site entitlement for the recipient and frees the site entitlement for the sender.
*   All platform-level site management permissions transfer to the new owner.
    
    Note
    
    CMS roles and permissions remain unchanged after a transfer and the recipient must review and manage user access manually.
    
*   All transfer activity is logged in the **Activity Feed** for auditing and support.

Security and limitations
------------------------

*   ****Audit trail****: All transfer activity is logged in the **Activity Feed** for auditing and support.
    
*   ****Domains****: Public and internal domain names are not transferred; recipients must configure these manually.
    
*   ****Entitlement errors****: If the recipient lacks an available entitlement, the transfer cannot proceed and an error message will display.
    
*   ****Regional restrictions****: Acquia Source does not support transferring sites across AWS regions because subscriptions are not multi-region aware. AWS regions operate as independent, physically separated hubs.