Yes: merging consolidates two accounts into one. The duplicate is removed, and its data moves into the account you keep, a process most platforms describe as permanent once confirmed. Because of that, merges typically need admin rights, and you should check identities carefully before you confirm anything.
TL;DR:
- Most platforms move messages, memberships, assigned work, and contribution histories, but identity provider links, payment credentials, and some tokens often remain behind.
- Merges usually require site administrator rights, and accounts linked through SSO or SCIM may need identity provider changes or support before they can proceed.
- Verify ownership, compare roles, and export credentials or records that will not transfer, because many platforms make a confirmed merge permanent.
- Credentials from the removed account may be deleted or transferred depending on the platform, so have the person sign in afterward and test access.
Table of Contents
- What happens to your data when you merge accounts
- Who can merge accounts and what permissions are needed
- How to prepare: an audit checklist before you merge
- Step-by-step: running the merge, UI and support routes
- What changes after the merge: logins, access and membership
- Limitations, common mistakes and how to avoid them
- Cleaning up duplicates without losing trust
- FAQ
- Sources
- Managing fair access once your records are clean
What happens to your data when you merge accounts
A merge does not simply delete a duplicate profile. It moves most of the content tied to that profile into the account you are keeping, then removes the empty shell. Vendor documentation describes this as consolidating both data and permissions before the duplicate account disappears for good.
What usually transfers:
- Messages, posts and any content the person created or owns
- Group and team memberships
- Items assigned to that person, such as tasks or tickets
- Contribution histories, including edits, comments and activity logs
What often does not transfer: some identity provider bindings, SCIM or SSO provisioning links, payment tokens and certain stored credentials. These tend to stay anchored to the system that issued them rather than following the person.
Permissions generally consolidate into the union of both accounts’ roles. When the two accounts hold different privilege levels, the higher one usually wins in the merged result.
Who can merge accounts and what permissions are needed
Most platforms restrict merging to site administrators or a specific “merge users” permission rather than leaving it open to any member. Ordinary account holders typically cannot merge their own duplicates without help.
- A dedicated admin permission (often separate from general content moderation rights) is usually required
- ID-based merges, cross-site merges or bulk CSV operations often have to be run by the platform’s own support team rather than through a self-serve menu, as Atlassian’s merge documentation sets out for its enterprise cases
- Accounts provisioned through SSO or SCIM may block a standard merge entirely until an identity-provider-side step runs first
If you manage a workspace tied to an external identity provider, check whether your platform flags SCIM-linked accounts as unmergeable through the normal admin screen before you start.
How to prepare: an audit checklist before you merge
A rushed merge is the easiest way to lose records you needed to keep. Running through a short checklist first catches most of the common failure points.
- Verify account ownership using a unique identifier such as a work email or employee ID, and confirm the person actually wants the merge
- Compare roles on both accounts; many systems, including Dust’s admin governance tools, require roles to match before a merge will proceed
- Export or archive anything that typically does not transfer, including payment details, linked identity-provider settings and API tokens
- Decide which account to keep based on active login credentials, the preferred email or username, and whichever profile has the most recent activity
- Create a rollback record: export key content and logs, and if your platform offers a sandbox, test the merge there first
Pro Tip: Build a simple export spreadsheet listing profile fields, membership numbers and contribution IDs for both accounts before you merge, so you can check afterwards that everything expected actually arrived.
Step-by-step: running the merge, UI and support routes
Most platforms offer either a self-serve admin screen or a support-run bulk process, and the two follow a similar logic even though the interfaces differ.
Self-serve UI flow:
- Locate both accounts in the admin panel
- Select the duplicate and the account you intend to keep
- Choose the merge option and confirm which is the keeper and which is the source
- Review the merge preview screen, which typically lists what will move
- Swap keeper and source if the preview shows the wrong account would survive
- Confirm the merge once the preview matches what you expect
Support or CSV flow for bulk operations:
- Build a CSV mapping each source account to its target keeper account
- Check encoding and make sure required ID fields are present, since Atlassian’s CSV template guidance notes that missing identifiers cause rows to fail
- Submit the file to platform support where self-serve bulk merging is not available
- Monitor the job and download the results log once it completes
Some systems also merge accounts automatically when a new login credential matches an existing email address, a behaviour YouTrack documents for its own platform. Before confirming any merge, check which fields the preview says will be preserved, whether roles are merging as expected, and any warning about credentials being deleted rather than carried over.
What changes after the merge: logins, access and membership
Once the merge completes, the keeper account becomes the single record for that person, and the removed account no longer exists as a separate login.
- Content, message history, group memberships and assigned records move into the keeper account
- Some identity-provider bindings, SCIM provisioning links, payment credentials and certain API tokens stay behind and do not follow the merge
- Keeper account credentials continue working as before. What happens to the removed account’s credentials varies: some systems delete them, while others transfer them into the keeper so the person can still log in with either set, as YouTrack’s documentation describes for its own auto-merge behaviour
- Advise the affected person to sign in to the keeper account, re-link any connected apps, and check that group memberships and access levels look correct
A quick post-merge checklist for the user helps catch anything that did not move cleanly: sign in, re-link integrations, confirm memberships, and test access to anything they use regularly.
Limitations, common mistakes and how to avoid them
Most merge failures trace back to a handful of predictable causes, and each one has a straightforward fix.
- Merges are generally irreversible, so export anything you might need and double-check identities before confirming
- Most platforms only let you merge two accounts at a time; for several duplicates, merge them in sequence, combining the result with the next one each time
- Cross-site accounts and anything provisioned through SCIM often need a separate linking step or a support-run path rather than the standard admin screen
- Align roles on both accounts first, since mismatched roles commonly cause a merge to fail or produce unexpected privilege changes
- Automatic merges triggered by matching email addresses are convenient but can also mask accidental account splits caused by typos or email aliases
Pro Tip: When a platform offers automatic merging based on matching credentials, pause and check that the two accounts genuinely belong to the same person before accepting the result.
Cleaning up duplicates without losing trust
The technical steps matter less than how you handle the people attached to the accounts. Tell members before you merge anything, and confirm with them afterwards that their history and access look right. An audit trail, even a simple export of key fields before you start, saves far more time than it costs when something does not land where expected.
Running merges during low-activity periods, and testing on a non-production environment when one exists, turns a risky one-off operation into a routine piece of admin housekeeping.
— Simon
FAQ
Can you merge two accounts into one?
Yes, most platforms let an administrator combine two accounts into a single profile, moving data and permissions into the account you keep before deleting the duplicate. This is typically described as a permanent operation, so confirm identities and export anything you might need first.
Can I still merge Fortnite accounts in 2026?
This article covers account merging for membership, workspace and CRM platforms rather than consumer gaming accounts, so specific game-account merge rules fall outside what we can confirm here. Check the relevant game publisher’s own support pages for current policy.
How do I merge users in a membership or workspace system?
Most admin panels let you select the duplicate account and the account you want to keep, choose a merge option, review a preview of what will transfer, and then confirm. For bulk operations, platforms such as Atlassian use a CSV mapping that support teams run on your behalf.
What happens when I merge two accounts?
Content, messages, group memberships and assigned records generally move into the keeper account, while some identity-provider links, payment credentials and certain tokens often stay behind. Vendor documentation lists exactly which items move for each platform, so check the specific system you use before relying on defaults.
Sources
- Merge User Accounts | AMS Help Center
- Merge user accounts | Atlassian Support
- Merging user accounts — YouTrack / JetBrains
- Merging user accounts — Dust (support docs)
Managing fair access once your records are clean
Tidying up duplicate profiles solves one problem: knowing who your members actually are. A separate problem shows up the moment a popular tee time goes live and every member tries to book the same slot within seconds of release.
That is the gap we built BallChute to close. Rather than a fastest-finger scramble, we give golf clubs an online waiting room where members join a queue and get a fair, orderly turn to pick their preferred time, with no advantage for whoever happens to be fastest on a mouse. Clubs set their own rules and time limits, so committees stay in control of how releases work, and completed tee sheets come out the other end without the usual chaos.
We offer plans with monthly and annual pricing, and every plan includes a 14-day free trial so you can see how a release behaves with your own members before committing to anything.
If your club is still fielding complaints every time a popular slot opens, try BallChute free for 14 days and see what an orderly booking queue does for your next release.