# Removing Duplicate Accounts After Schema Update

**URL:** <https://community.sailpoint.com/discuss/t/removing-duplicate-accounts-after-schema-update/36293>\
**Category:** Administration & Troubleshooting\
**Tags:** accounts-entitlements, workday\
**Created:** [June 4, 2025, 4:30pm UTC](https://community.sailpoint.com/discuss/t/removing-duplicate-accounts-after-schema-update/36293 "2025-06-04T16:30:35Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Divya\_B7](https://avatars.discourse-cdn.com/v4/letter/d/e9a140/32.png) [@Divya\_B7](https://community.sailpoint.com/discuss/u/Divya_B7)\
**Post date:** [June 4, 2025, 4:30pm UTC](https://community.sailpoint.com/discuss/t/removing-duplicate-accounts-after-schema-update/36293/1 "2025-06-04T16:30:35Z")

</div>

I had to change the account Name and account ID in the schema of an authoritative source. After doing this change and re-aggregating the source, duplicate accounts are created for the users- one with the old attributes and one with the new. How can I remove these duplicate accounts and ensure that only the accounts with the latest account ID and Name attributes are retained?

---

<div class="post-metadata">

**Author:** ![REKHABHUSE](https://avatars.discourse-cdn.com/v4/letter/r/ebca7d/32.png) [@REKHABHUSE](https://community.sailpoint.com/discuss/u/REKHABHUSE)\
**Post date:** [June 5, 2025, 6:57am UTC](https://community.sailpoint.com/discuss/t/removing-duplicate-accounts-after-schema-update/36293/2 "2025-06-05T06:57:40Z")

</div>

you can achieve this by following 2 steps

1) Run zero account aggregation (Change the configruation parameters in aggregation that 0 records are fetched into SailPoint)

→ This will remove all old accounts

2) Restore the configuration and run the aggregation

This will bring in new accounts.

---

<div class="post-metadata">

**Author:** ![cinilsunny](https://sea3.discourse-cdn.com/sailpoint2/discuss/user_avatar/community.sailpoint.com/cinilsunny/32/17819_2.png) [@cinilsunny](https://community.sailpoint.com/discuss/u/cinilsunny)\
**Post date:** [June 5, 2025, 10:34am UTC](https://community.sailpoint.com/discuss/t/removing-duplicate-accounts-after-schema-update/36293/3 "2025-06-05T10:34:40Z")

</div>

Ideal way is to first clean up existing data by providing a query which returns empty result and by selecting delete data 100% during aggregation and then change the schema.

or was it cleaned up but still creates again using both old and new schema accountid?

---

<div class="post-metadata">

**Author:** ![TomNimmo](https://sea3.discourse-cdn.com/sailpoint2/discuss/user_avatar/community.sailpoint.com/tomnimmo/32/1060_2.png) [@TomNimmo](https://community.sailpoint.com/discuss/u/TomNimmo)\
**Post date:** [June 5, 2025, 1:42pm UTC](https://community.sailpoint.com/discuss/t/removing-duplicate-accounts-after-schema-update/36293/4 "2025-06-05T13:42:37Z")

</div>

You’ll also have to adjust the [Account Deletion](https://documentation.sailpoint.com/saas/help/accounts/loading_data.html#disable-account-deletion) setting on the source and then don’t forget to change it back!

 ![enable_accnt_deletion.png](https://cdck-file-uploads-global.s3.dualstack.us-west-2.amazonaws.com/sailpointsbx2/original/2X/5/5093ccc29e436d88ab53d7bba20472d6d4e70384.png)