The Answer of M$Copilot : a { text-decoration: none; color: #464feb; } tr th, tr td { border: 1px solid #e6e6e6; } tr th { background-color: #f5f5f5; }

As far as I can tell, OpenProject does not provide a native "user merge" feature. The administration documentation describes how to create, edit, lock, unlock, and delete users, but I could not find any documented way to merge two existing accounts. [openproject.org], [openproject.org]

In your situation, I would expect the recommended approach to be:

• Identify which account should remain the authoritative account.

• Reassign memberships, work package assignments, ownership, and other references where possible.

• Lock or delete the duplicate account once all relevant data has been transferred.

Since you are on OpenProject 17.6.0, it is also worth noting that later releases mention fixes for duplicate users created during Jira imports, which suggests that duplicate-user scenarios are known, but I have not found any indication of an account merge capability. [newreleases.io], [community-...cripts.org]

If a complete merge is possible, it is likely to require either:

• a Rails console operation,

• a custom migration script,

• or direct database manipulation performed by an administrator.

I would therefore recommend asking the OpenProject community whether there is a supported migration procedure for consolidating duplicate accounts while preserving work package history, comments, memberships, and audit trails.

Personally, I would also add this sentence to your forum post because it is probably the most important part of the question:

"My primary concern is preserving historical data (comments, work package history, activities, memberships, and assignments) while consolidating duplicate user accounts into a single identity."