Skip across the chapter
Quota Playbook

Sales record reassignment: 5 checks before rep exits

Quota Playbook Editorial Team · Published · 12 min read

Reassign open records to active users before deactivating the leaving rep to prevent orphaned deals.

Direct answer: Reassign open records before deactivating the user

When a user leaves an organization, deals, contacts, tasks and other activities pending under their ownership are best transferred to existing active users in the CRM, according to Freshworks. HubSpot advises that before removing a user, you should reassign any records owned by the user, as noted in HubSpot documentation. HubSpot recommends reassigning a user's records before removing that user. Freshworks recommends transferring pending records to existing active users. In Pipedrive, deactivated users retain ownership of their deals and contacts. Without reassignment in Pipedrive, deals and contacts stay assigned to the deactivated user. The transfer process preserves attribution and ensures the deal pipeline remains intact for the remaining team. Verify that every open record has a new owner before you proceed with the deactivation step. This prevents data loss and maintains workflow integrity for the sales team.

Key takeaways for how to reassign sales records when a rep leaves

  • Record ownership: Transfer pending deals, contacts, and tasks to existing active users before the departing user leaves, as recommended by Freshworks.
  • Activity history: Verify if any deals or contacts are currently owned by the user prior to deactivating their account, a step suggested by Pipedrive.
  • Deactivation status: Reassign any records owned by the user before removing them from the platform, according to HubSpot.
  • Data retention: Close deletes an organization's lead data by default 91 days after organizational deactivation or cancellation.
  • Workflow integrity: Use bulk reassignment processes that move all records owned by the selected user regardless of state, as described by Microsoft.

Vendor-specific transfer behaviors reference table

Different platforms handle record ownership differently when a user exits. The table below summarizes the specific behaviors for each vendor based on their documented procedures.

Publisher Record Ownership Behavior Source
Freshworks Deals, contacts, and tasks pending under a leaving user's ownership are best transferred to existing active users in the CRM. Freshworks
Close Removing a user does not delete their activity; their name remains next to all Activities on Leads. Close
HubSpot You should reassign any records owned by the user before removing them. HubSpot
Pipedrive Deactivated users retain ownership of their deals and contacts, which remain in the account assigned to that user. Pipedrive
Microsoft The Reassign Records tool moves all records owned by a selected user or team regardless of state. Microsoft
Pipedrive Leads, deals, and contacts owned by a deleted user remain assigned to that deleted user unless ownership is transferred during deletion. Pipedrive

Pipedrive retains ownership after deactivation, while HubSpot recommends reassignment before removal. For instance, Pipedrive explicitly notes that records stay with the deactivated or deleted user unless you transfer them during the process. Microsoft offers a bulk tool that handles all records for a user or team, moving them regardless of their current state. In contrast, Close retains the historical activity attribution to the removed user, meaning the name stays visible on leads even after the account is gone. Freshworks recommends transferring pending items to active users to maintain workflow continuity. HubSpot advises reassigning records prior to the removal step to ensure no data is left unmanaged.

Check your specific platform's documentation to confirm whether records auto-reassign or require manual action.

Step-by-step: Pre-exit audit of owned records and activities

Before removing a departing rep from your system, you must verify five specific ownership checks to prevent data loss or broken processes. These checks cover record ownership, activity history, deactivation status, data retention, and workflow integrity.

1. Verify record ownership Start by identifying every deal and contact currently assigned to the departing user. Prior to deactivating a user in your Pipedrive account, we suggest first seeing if there are any deals or contacts currently owned by that user, according to Pipedrive. If you skip this step, those records do not automatically move to another team member. When a user is deactivated, all of the deals and contacts that they own remain in the account, but also remain owned by that deactivated user, as stated by Pipedrive. As a recommended workflow, arrange reassignment to an active colleague before deactivation.

2. Review activity history Record ownership remains with the deactivated user in Pipedrive, while notes remain visible in deal or contact detail views unless an admin deletes them. Review record ownership separately from retained notes and activity attribution.

3. Confirm deactivation status Determine whether you are deactivating or deleting the user, as the consequences differ. In HubSpot, historical activities such as property changes and content updates remain available when deactivated users are reactivated. Pipedrive covers both deactivation and deletion, recommending an ownership review before deactivation and describing transfers during deletion. Freshworks provides guidance for the deletion process, noting that you must check dependencies before removing the user entirely Freshworks. Choose the correct status based on your retention policy and ensure the user is not deleted until all manual transfers are complete.

4. Assess data retention Understand how long data remains accessible after the user leaves. Pipedrive confirms that deals and contacts remain in the account even after deactivation, meaning the data is not immediately purged Pipedrive. However, if you choose to delete the user, the handling of associated data may differ. It takes up to 30 days to completely delete the data from all the third party sub-processors and internal platforms, according to Freshworks. Do not assume that deleting a user immediately removes all associated data; some platforms retain historical activities or purge after a delay.

5. Check workflow integrity Before deleting a User, check all Workflows, Reports, Sales campaign and Views, where you may have included “Owner” or “Created By” condition and have the particular User you are deleting in conditions, as reported by Freshworks. If these automated processes reference the departing user, they may fail or behave unexpectedly after the user is removed. Review these dependencies now to ensure your team’s reporting and automation continue to function correctly for the remaining staff.

Handling closed deals and attribution integrity

When a rep leaves, you must decide whether closed deals move to the new owner or stay with the departed user. Microsoft’s documentation for the Power Platform admin center states that the bulk reassignment process moves all records owned by the selected user or team regardless of state Microsoft. This means if you use that specific bulk tool, your closed-won and closed-lost opportunities will transfer to the target user or team. You cannot filter this action to exclude closed records using that method.

To manage attribution integrity, you need to know which tool you are using. Microsoft instructs admins to use the Reassign Records tool in the Power Platform admin center to reassign all records from one user to yourself, a team, or another user Microsoft. If your goal is to keep historical attribution on the original rep for closed deals, the bulk reassignment tool described by Microsoft does not offer a toggle to skip closed states. You must verify if your specific CRM instance offers a separate, granular transfer option that allows you to select only open opportunities. If you only have access to the bulk tool, closed deals will change owners.

Review your reporting requirements before running any transfer. If your quota reporting relies on the "Owner" field for closed deals, moving those records will shift the credit to the new owner. If your reporting relies on a separate "Original Owner" or "Creator" field, the attribution may remain intact even if the "Owner" field changes. Check your dashboard definitions to see which field drives your closed-deal metrics.

Unlinked communications and notes follow different retention paths depending on the platform and the specific record type. Managers must distinguish between data tied to an active object and data that exists only in a user’s personal history.

Pipedrive specifies that emails not shared or linked to any deal, lead, project, organization, or person will be deleted if the user is deactivated for more than 30 days, as reported by Pipedrive. This rule applies specifically to unlinked email data. Check email sharing and record links before deactivation. Emails neither shared nor linked to a deal, lead, project, organization or person are deleted when the user has been deactivated for more than 30 days.

In contrast, Pipedrive states that all notes added by deactivated users will remain visible in the detail view of a deal or contact unless deleted by an admin user, according to Pipedrive. This means that while unlinked emails may vanish after 30 days, notes attached to deals or contacts persist indefinitely. An admin must manually delete these notes if they wish to remove them from the record. The distinction is critical: notes are treated as part of the deal or contact history, whereas unlinked emails are treated as temporary user data.

Close handles user removal differently regarding activity visibility. If you remove a User, the platform does not delete any of that user’s activity in Close, and you will still see their name next to all their Activities, including Calls, Emails, and Notes, on Leads, as published by Close. This behavior preserves the historical context of who performed the action. The user’s name remains attached to the activity even after the user account is removed. This ensures that the timeline of the lead’s progress remains intact, showing which individual made the call or sent the email.

User exit transfer checklist

Use this form to verify the five ownership checks before you deactivate a user. Complete each row as you audit the departing rep’s account.

For the record ownership row, confirm that pending items are moving to an active user. As reported by Freshworks, deals, contacts, tasks and other activities pending under their ownership are best transferred to existing active users in the CRM.

For activity history, record retained notes and attribution: ____, remembering that Close keeps the removed user's activity and name on leads. According to HubSpot, before removing a user, you should reassign any records owned by the user.

For deactivation status, record the intended account action and procedure: _; for workflow integrity, record conditions referencing the departing user: _. As reported by Pipedrive, prior to deactivating a user in your Pipedrive account, we suggest first seeing if there are any deals or contacts currently owned by that user.

For data retention, record applicable deletion rules: _; for record ownership, record the active recipient for pending items: _. According to Microsoft, this process moves all records owned by the selected user or team regardless of state.

Complete the worksheet before proceeding to the next step.

FAQ: How to reassign sales records when a rep leaves

What happens to open deals if I deactivate a user without transferring them?

According to Pipedrive, a deactivated user's deals and contacts stay in the account under that user's ownership. This means the records stay linked to the inactive profile rather than automatically moving to another team member.

Does deactivating a user delete their call history and notes?

In Close, removing a user preserves their past activity. As reported by Close, the platform does not delete any of that user’s activity, so you will still see their name next to all their Activities, including Calls, Emails, and Notes, on Leads.

Can I transfer records to a user who is already deleted?

Freshworks recommends existing active users as recipients for pending records. According to Pipedrive, leads, deals and contacts stay assigned to a deleted user unless transferred during deletion.

How long does it take for data to be purged after a user leaves?

The timeline varies by vendor. Close purges an organization’s lead data 91 days later by default after deactivation or cancellation. Meanwhile, Freshworks states it takes up to 30 days to completely delete the data from all third-party sub-processors and internal platforms.

Do I need to reassign records before or after removing the user?

HubSpot recommends reassigning owned records before removing the user. Pipedrive describes transferring ownership during deletion, with records otherwise remaining assigned to the deleted user. Freshworks states that deleting data across third-party sub-processors and internal platforms takes up to 30 days.

Sources

  1. Call handling: 9 rules to check before coaching
  2. Overtime errors for non-exempt sales reps: 5 fixes
  3. Check 8 sharing limits before sending coaching files
  4. Remote access rules for sales reps
  5. Final commission record

More plays