Acquia Source allows organization administrators to securely transfer site ownership from one organization to another. This feature streamlines agency workflows, supports privacy during development.
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 |
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
Log in to Acquia Source to open the Sites Dashboard.
The recipient must accept the transfer for it to complete.
If the recipient declines or does not respond, the sender can cancel the transfer.
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.
If this content did not answer your questions, try searching or contacting our support team for further assistance.
If this content did not answer your questions, try searching or contacting our support team for further assistance.