Salesforce Dictionary - Free Salesforce GlossarySalesforce Dictionary
DictionaryMMass Transfer Records
AdministrationBeginner

Mass Transfer Records

Mass Transfer Records is the Salesforce Setup tool that lets administrators reassign record ownership in bulk from one user to another.

§ 01

Definition

Mass Transfer Records is the Salesforce Setup tool that lets administrators reassign record ownership in bulk from one user to another. The tool addresses a recurring administrative need: when a sales rep leaves, when accounts are reorganized between territories, when a manager redistributes deals, ownership changes are often required for hundreds of records at once. Without bulk transfer, ownership changes happen one record at a time, which is impractical for any organization beyond the smallest. Mass Transfer Records supports Account, Lead, and a small set of other objects, with filter criteria to scope the transfer precisely.

The tool changes the OwnerId field on each matching record and optionally cascades to related records based on transfer rules. Cascading is important: transferring an Account often should also transfer its Opportunities, Cases, and Contacts; transferring a Lead does not have downstream effects. The tool exposes the cascade options as checkboxes during setup. Workflow and triggers fire on the OwnerId change, so any logic that depends on owner runs for every transferred record.

§ 02

How Mass Transfer Records works

Supported objects

Mass Transfer Records supports Accounts, Leads, and Custom Objects. Other standard objects (Opportunities, Cases) cannot be transferred through this tool directly; they cascade from Account transfers if the appropriate option is selected. For direct mass ownership change on Opportunities or other objects, Data Loader is the standard alternative.

Cascading transfers

When transferring an Account, the tool exposes options for cascading the transfer to the Account's Opportunities, Cases, related Contacts, and other child records. Each cascade option is independent. This is the most powerful feature of the tool: a single Account transfer can move dozens of related records to the new owner in one operation, preserving the parent-child ownership relationship.

Filter criteria

Filter by current owner, record name patterns, and various other fields depending on the object. The most common filter is current owner: move all records owned by User A to User B. The tool also supports filters on standard fields like Type, Industry, and custom field values for finer targeting.

Triggers and workflow fire

Ownership changes through Mass Transfer fire all standard automation: Apex triggers, Workflow Rules, Flows, Process Builder. For high-volume transfers, this can stress governor limits. Bulk transfers of 10,000 records with heavy trigger logic may take significant time or hit limits; plan for the volume.

Preview before transfer

The tool shows a preview of matching records before transfer. Confirm count and sample. The preview is the last safety check; ownership transfers are reversible but recovering 10,000 wrong transfers is operationally painful.

Permission requirements

The tool requires the Transfer Record permission for the relevant object plus the source user permissions. Different objects have different transfer permissions. System administrators have Transfer Record by default; non-admin users with the permission set can also use the tool for the objects they have transfer rights on.

Data Loader as alternative

For bulk ownership change on objects not supported by Mass Transfer Records (Opportunity, Case, etc.), use Data Loader: extract records, update OwnerId, upload through Update operation. The Data Loader path supports any object and unlimited volume; the trade-off is the manual extract-edit-upload cycle versus the wizard-driven Mass Transfer UI.

§ 03

Run a Mass Transfer with cascading

Running a Mass Transfer involves choosing the source user, configuring cascade options, previewing, and executing. The steps below cover the standard offboarding scenario.

  1. Confirm the scenario

    Verify the records and the source/target users. For an offboarding, confirm the target is the right successor.

  2. Open Mass Transfer Records

    Setup > Data > Mass Transfer Records. Choose the object type (Account, Lead, or Custom Object).

  3. Pick source and target users

    Source: the user currently owning the records. Target: the user inheriting them.

  4. Configure cascading

    For Accounts, decide which related records cascade: Opportunities, Cases, Contacts, etc. Default to cascading for offboarding scenarios.

  5. Set additional filters

    Optionally narrow by record type, industry, or other fields. Useful when only a subset of records should transfer.

  6. Preview matching records

    Click Find. Review the count. Confirm the preview matches expectations before proceeding.

  7. Execute and monitor

    Run the transfer. For large volumes, monitor for governor limit failures; very large transfers may need batching.

Key options
Source userremember

The current owner whose records will be reassigned.

Target userremember

The new owner receiving the records.

Cascade Opportunitiesremember

Transfer the source user's Opportunities along with the Accounts.

Cascade Casesremember

Transfer related Cases. Default off; review carefully for support workflows.

Cascade Contactsremember

Transfer related Contacts. Typically defaults on for Account transfers.

Gotchas
  • Triggers fire on transfer. Bulk transfers with heavy automation can hit governor limits; plan for batching.
  • Cascade settings can be over-broad. Cascading Cases on Account transfer may move support tickets that should stay with the original support team.
  • Only specific objects are supported directly. Opportunities and Cases need to cascade from Account or use Data Loader.
  • Transfer is reversible but operationally painful for thousands of records. Verify the preview carefully.
  • Workflow Rules on the target may fire based on owner change. Review workflow design before bulk transferring to a new owner.
Was this entry helpful?
Help us write better definitions. Quick reactions or detailed edit suggestions.

About the Author

Dipojjal Chakrabarti is a B2C Solution Architect with 29 Salesforce certifications and over 13 years in the Salesforce ecosystem. He runs salesforcedictionary.com to help admins, developers, architects, and cert/interview candidates sharpen their fundamentals. More about Dipojjal.

§

Test your knowledge

Q1. What is the primary benefit of Mass Transfer Records for Salesforce administrators?

Q2. In which area of Salesforce would you typically find Mass Transfer Records?

Q3. Why is understanding Mass Transfer Records important for Salesforce admins?

§

Discussion

Loading…

Loading discussion…