The website is on a UserVoice platform that has a different privacy policy from our other sites. You may view the details at

Merging duplicate ORCID iDs

The ORCID Registry is designed to prevent duplicate iDs from being created by only allowing one ORCID record per email address, and checking for duplicates based on name when you register. For more information about these steps see Create an iD.

Despite the controls we have in place, there will be times when a duplicate will be unintentionally created. For these situations, the ORCID Community team can help users with multiple records to mark one ORCID iD as a primary one, and the other iD as deprecated. 

Because ORCID identifiers are designed to be persistent, obsolete iDs will be deprecated, not deleted. The record associated with a deprecated iDs contains only a pointer to the primary record. Accessing a deprecated ORCID record redirects the requester to the primary record, both in the user interface and the API. An example of a deprecated record can be seen at

Also of note:

  • Access granted by a user on a record that has been deprecated does not transfer to the related primary record. Members will need to request that the user re-grant authorization with their primary ORCID iD.

  • ORCID relies on individuals to report duplicate records. We will assist users with combining their own records. We will also take into consideration reports from the community about potential duplicates or incorrect data. In either case, users should contact the ORCID Community team to report an issue and include the ORCID identifiers of the records in question. In the event that data in a record may need to be corrected, we will follow our published Dispute Procedures.

  • Once combined, ORCID records cannot be restored to their original state. For this reason we are conservative about deprecating records, and require proof of ownership and authorization from the iD holder before apparent duplicates are managed.

Feedback and Knowledge Base