Salesforce Dictionary - Free Salesforce GlossarySalesforce Dictionary
Full Mass Transfer Records entry
How-to guide

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.

By Dipojjal Chakrabarti · Founder & Editor, Salesforce DictionaryLast updated May 19, 2026

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.

See the full Mass Transfer Records entry

Mass Transfer Records includes the definition, worked example, deep dive, related terms, and a quiz.