Resolve Google Admin Console restore error: Address or Name Conflict
The restore failed because the address or name is already being used by another object in the destination account.
Applies to: Users, groups, org units, custom schemas, admin roles, calendar resources, buildings, features
What this error means
Another user, group, alias, or administrative object already uses the required value.
Why this error occurs
Google allows only one owner for an address or name within an account. The same address cannot belong to a user, a group, and an alias at the same time, and names must be unique among objects of the same kind.
Unlike error AP1026, where the object you are restoring already exists, this error means a different object is holding the value you need. An address held as an alias is the case most often missed, because an alias does not appear as a separate entry in the Admin console's user list.
Resolution
Step 1: Find what is holding the address or name
| Object being restored | Where to look |
| User or user alias | Menu > Directory > Users. Search for the address. If nothing is found, the address may be an alias on another account: open the likely user and check User information > Email aliases. Also check Directory > Groups, since a group may hold the address. |
| Group or group alias | Menu > Directory > Groups, then Directory > Users as above. |
| Org unit |
Menu > Directory > Organizational units. Two org units under the same parent cannot share a name. |
| Custom schema | Menu > Directory > Users > More options > Manage custom attributes. Requires super administrator. |
| Admin role | Menu > Account > Admin roles |
| Calendar resource, building, or feature | Menu > Directory > Buildings and resources |
Step 2: Decide what happens to the existing object
- If the existing object should stay: restore the item under a different address or name.
- If the existing object is no longer needed: rename or delete it, then initiate the restore again.
Before you rename or delete anything, note the following:
- Renaming a user's primary address changes the address they sign in with. Google keeps the old address as an alias on that account, which means it will still hold the address and the conflict will remain. Remove the alias if you need the address free.
- Deleting a group removes its membership and any access it grants.
- Renaming an org unit does not move its users, but it may affect policies or scripts that refer to the org unit by name.
Step 3: Initiate the restore again
Once the address or name is free, initiate the restore again for the affected object.
Verify the resolution
Open the restored object using the path in the table above and confirm it appears with the expected address or name. Then confirm that the restore finishes without error AP1028.
If the error continues
Confirm that the listed prerequisite or configuration change applies to the correct destination account. If the error continues, contact SysCloud Support with the error code, job ID, affected object, raw Google message, and failure time.