Partner Merge User Consolidation
by Odoo Community Association (OCA) https://github.com/OCA/partner-contact , Therp BV https://github.com/OCA/partner-contact| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Lines of code | 47 |
| Technical Name |
base_partner_merge_user_consolidation |
| License | AGPL-3 |
| Website | https://github.com/OCA/partner-contact |
Partner Merge User Consolidation

This module extends the standard Merge Contacts wizard in Odoo (base.partner.merge.automatic.wizard) so that user accounts are also consolidated when you merge duplicate contacts. Odoo allows you to merge two (or more) contacts into one. This is great for deduplication.
However, when both of those contacts are linked to different users (res.users), Odoo does not merge or clean up those users. After the merge you can end up with:
- Multiple logins pointing at the same final contact.
- Confusing access rights: which login should this person actually use?
- Compliance issues: inactive/old accounts still exist and could still log in.
This module fixes that:
When you merge contacts and Odoo finishes the normal merge:
- If the resulting contact has 0 or 1 linked users:
- Nothing extra happens.
- If the resulting contact has 2+ linked users:
- The module chooses one user account to keep:
- The account with the most recent login date (field login_date, which reflects the last res.users.log record).
- If nobody has ever logged in, it falls back to the most recently created user.
- That “kept” user is:
- Forced to stay active.
- Explicitly linked to the surviving contact partner.
- All other users are archived:
- They are set inactive.
- Their login is scrambled to a unique value like __merged_user_<id>_oldlogin so they can no longer authenticate and so their old login can be reassigned if desired.
- Security groups are merged:
- Any groups on the archived users are added to the kept user.
- Odoo’s standard res.users write() logic will automatically:
- add all implied groups,
- normalize mutually exclusive role groups,
- enforce “internal vs portal vs public” constraints.
- The module chooses one user account to keep:
Table of contents
Bug Tracker
Bugs are tracked on GitHub Issues. In case of trouble, please check there if your issue has already been reported. If you spotted it first, help us to smash it by providing a detailed and welcomed feedback.
Do not contact contributors directly about support or help with technical issues.
Credits
Authors
- Therp BV
Contributors
- Nikos Tsirintanis <ntsirintanis@therp.nl>
Maintainers
This module is maintained by the OCA.
OCA, or the Odoo Community Association, is a nonprofit organization whose mission is to support the collaborative development of Odoo features and promote its widespread use.
Current maintainer:

This module is part of the OCA/partner-contact project on GitHub.
You are welcome to contribute. To learn how please visit https://odoo-community.org/page/Contribute.
Please log in to comment on this module