Scenario
Last updated on
Aug 3, 2026
Understand the constraints and workflows for moving domains involving encrypted directories or trust relationships
Standard domain transfers allow you to move domains directly from one directory to another within the same Admin Console. Encrypted directories and directories in trust relationships require special handling to preserve user access and prevent data loss.
Encrypted directories and trust relationships
Encrypted directories and directories in trust relationships introduce extra constraints that prevent direct transfers.
Encrypted directories use dedicated encryption keys to secure user assets. Adobe does not support moving domains directly into or out of an encrypted directory because the encryption key is tied to the directory itself. Transferring a domain requires re-encrypting all associated user assets with a different key, which can result in data loss or access issues.
Trust relationships enable multiple organisations to authenticate users against a single claimed domain. When a directory is trusted by other organizations, the trustees rely on the directory's identity configuration to authenticate users. Moving a domain without trustee coordination disrupts authentication and immediately locks users out of Adobe products and services.
Key considerations before migration
Before initiating any domain transfer involving encrypted or trusted directories, take the following precautions:
Export user data: Export a complete user list from all Admin Consoles involved in the migration. The export provides a snapshot of user accounts, assigned product profiles, and admin roles. The data is essential for rollback if issues occur during migration.
Plan for downtime: Users are logged out during domain transfers and can’t start new sessions until the migration completes. Schedule the migration during off-peak hours to minimize disruption.
Coordinate with trustees: If your directory is trusted by other organizations, notify the trustees before making changes. Establish new trust relationships before revoking old ones to prevent authentication failures.
Verify trust configuration: After migration, test user authentication from all trustee organizations to confirm that access remains intact.
Domain transfer scenarios and workflows
Encrypted or trusted directories fall into a few common scenarios, each with a recommended workflow. The table describes use cases to help you assess your environment and choose the best path.
|
|
Example |
Recommended workflow |
|
Move domains between directories in the same trust relationship |
Directory 1 and Directory 2 are configured in Console A. Both directories have a trust relationship established with Console B. |
Follow the standard domain transfer process. Because both directories share the same trust configuration, the transfer does not disrupt trustee authentication. |
|
Move domains between directories in different trust relationships |
Directory 1 is configured in Console A and has a trust relationship with Console B. A domain in Directory 1 must move to Directory 2 in Console A. |
|
|
Move a directory containing multiple domains to another Admin Console |
Directory 1 is configured in Console A. Directory 1 and its claimed domains must move to Console B for ownership transfer. |
Contact Adobe Customer Care for assistance with this type of migration. |
|
Move domains to or from an encrypted directory |
Directory 1 has encryption enabled. A domain from Directory 2 in the same Admin Console requires migration to Directory 1. |
Moving domains to or from an encrypted directory is not currently supported.
|
