How to Mass Update Records in Salesforce?

Changing five Salesforce records by hand is easy enough. But what happens when that list hits 500 or 5,000?

The same job turns slow, repetitive, and risky. So how do you update multiple records in Salesforce?

Salesforce offers a few routes to bulk update records, each built for a different scale. List views handle small edits, up to 200 records at a time. Data Import Wizard covers CSV updates up to 50,000 records. Data Loader takes over from there, supporting files as large as 5 million records. Flow and Apex step in when the same batch update needs to run again without manual input.

Here, we’ve explained how to mass update records in Salesforce, where each method works best, and what to check before changing live data. If you’re handling large-scale data changes or need help choosing the right approach, Salesforce consulting can also help you plan and execute bulk updates safely.

When Should You Mass Update Salesforce Records?

A Salesforce mass update makes sense when many records need the same type of change.

Typical examples include:

• Reassigning Leads or Accounts after a territory change
• Correcting inconsistent picklist values
• Updating Lead statuses after a campaign
• Moving Opportunities to a different stage
• Changing close dates across an active pipeline
• Applying a new Record Type
• Fixing data after a migration
• Filling incomplete fields across older records

Bulk editing saves time, but the bigger payoff is consistency. Reports run on exact field values and sales teams don’t always spell things the same way twice. “Closed Lost,” “Closed-Lost” and “Lost” read as the same outcome to a rep. Salesforce reads them as three different values unless the field is locked down.

Always export the original records before a large update. There’s no single undo button that covers every kind of bulk record update in Salesforce.

Salesforce Mass Update Methods Compared

The right method for bulk update records in Salesforce are compared below:

How to Mass Update Records Using Salesforce List Views

List views are the quickest option when the records are already visible in Salesforce and the same field value applies to all of them. The process breaks down into three steps:

Enable Inline Editing

Start in Setup.

Search for User Interface, then confirm that inline editing and enhanced lists are enabled. The user also needs edit access to the object, record and field.

In the list view, hover over the target cell. A pencil icon means the field is editable. A lock icon means it isn’t.

Create or Select a List View

Open the relevant object, such as Leads, Contacts or Accounts.

Choose an existing list view or create a new one. Add filters that isolate the exact records involved in the update.

Skip the broad views like “All Opportunities” when you’re making a live change. A tighter filter makes the final selection easier to check before you commit to it.

Add the target field as a visible column before proceeding.

Select and Update the Records

Select the records you want to change.

Click the pencil icon on one selected row, enter the new value and apply it to all selected records. Review the marked changes, then click Save.

Refresh the page after saving. List-view filters don’t always reapply immediately, so a record can stay visible even after the new value no longer matches the filter.

Limitations of List View Mass Editing

List views containing multiple Record Types don’t support inline editing. Filter the view to one Record Type first.

Formula fields, auto-number fields, roll-up summaries and several compound fields are also locked. Some Opportunity fields carry additional restrictions.

For anything beyond 200 selected records, switch to a CSV-based method built for genuine bulk operations.

How to Bulk Update Records Using Data Import Wizard

Data Import Wizard suits teams that want a browser-based tool without installing Data Loader. This runs in four stages, from export to final import:

Export the Salesforce Records

Create a report containing the records that need to change.

Include the Salesforce Record ID and every field involved in the update. Export the report as a CSV file.

Keep the untouched export in a separate folder. Don’t edit the only copy you have.

Prepare the CSV File

Strip the file down to what the update needs:

• Salesforce Record ID or another supported matching field
• Fields being changed
• New values
• Clear column headings

Check picklist spelling, date formats and blank cells. A blank value can behave differently from an omitted column, so remove fields that aren’t part of the update.

Salesforce recommends testing with a small CSV file first.

Start the Data Import Wizard

From Setup, enter Data Import Wizard in the Quick Find box.

Open the tool and click Launch Wizard. Select the relevant standard or custom object, then choose Update existing records.

The options shown depend on the object, edition and user permissions.

Map and Import the Fields

Upload the CSV file.

Salesforce maps some columns automatically, but automatic mapping still needs a manual check. Similar field names can point to different destinations, particularly in customised organisations.

Resolve every unmapped field, review the summary and click Start Import.

The job status appears in Recent Import Jobs or under Bulk Data Load Jobs in Setup.

Data Import Wizard Limitations

Data Import Wizard accepts up to 50,000 records and doesn’t cover every Salesforce object.

Opportunity updates often move to Data Loader instead. Permissions create another common obstacle. A user can’t import a value into a field they can’t edit.

Required fields, validation rules and Record Type settings can also stop individual rows.

How to Bulk Update Records Using Salesforce Data Loader

Data Loader is the stronger option for large-scale data changes and unsupported objects and it’s the tool most admins reach for when a true salesforce bulk record update is needed. Setting this up takes the steps:

Download and Open Data Loader

Download Data Loader through Salesforce Setup.

The client application runs on Windows and macOS. Sign in to the correct production or sandbox environment before selecting an operation, since the two often look identical once you’re inside them.

Prepare the Update File

Build a CSV containing the Salesforce ID and only the fields that need modification.

Check:

• Record IDs
• Owner IDs
• Picklist values
• Date formats
• Boolean values
• Field headers

Run ten or twenty rows first. A clean test catches mistakes before they reach the full dataset.

Run the Update Operation

Open Data Loader and select Update.

Choose the object, upload the CSV and map each column to its Salesforce field. Save the mapping when the same format will be used again.

Choose an output folder, then start the operation.

Review the Success and Error Files

Once the job finishes, Data Loader drops two CSV files into the output folder, one for records that succeeded and one for records that didn’t.

Open both. The success file confirms what went through. The error file is the one worth reading closely, since it explains why the rest didn’t. An invalid ID, a failed validation rule, a missing required value, or a locked record.

Fix only those failed rows and run that smaller file again. Re-uploading everything wastes processing time and muddies the audit trail, which is part of good data administration once updates run at real volume.

Update vs Upsert in Data Loader

Use Update when every record already exists and the Salesforce ID is available.

Use Upsert when records are matched through a Salesforce ID or external ID. A match updates the existing record. No match inserts a new one.

Picking Upsert by mistake can quietly create new records instead of only modifying the ones you meant to touch.

How to Mass Update Record Types in Salesforce

Record Type changes require two IDs, the record ID and the new Record Type ID. Four steps get the change safely into Salesforce:

Export Record IDs and Existing Record Types

Create a report containing both fields, then export it as a CSV.

Keep the existing Record Type column in the backup. It gives you a route back if the update needs to be reversed.

Find the New Record Type ID

Open the target Record Type in Salesforce Setup.

Copy its ID from the Record Type detail page or URL, then place that value in a Record Type ID column in the working CSV.

Upload the Updated Record Type IDs

Run the file through Data Import Wizard or Data Loader.

Map the record ID and Record Type ID carefully. Test a few rows before processing the full group.

Check Required Fields and Page Layouts

A new Record Type can point to another page layout with different required fields.

Most failed Record Type updates trace back to this gap. The CSV changes the Record Type, but the existing record is missing a value the new layout or a validation rule now requires.

Check those dependencies before upload.

How to Automate Mass Record Updates With Salesforce Flow

Flow removes the need to repeat the same administrative task each week or month, turning a manual batch update into something that runs on its own. Here’s how you can automate:

Use a Scheduled Flow

A schedule-triggered flow starts at a defined time and processes records that match set conditions.

Salesforce caps a single scheduled flow at 250,000 interviews. The wider 24-hour limit is 250,000 interviews or the number of qualifying user licences multiplied by 200, whichever is greater. Each retrieved record creates an interview.

Keep the entry criteria narrow. Pulling every record and filtering later burns through interviews and makes troubleshooting harder than it needs to be.

Use a Record-Triggered Flow

A record-triggered flow runs when a record is created or updated.

It fits ongoing rules rather than one-time cleanup. For example, the flow can stamp a follow-up date when an Opportunity enters Negotiation.

When Apex Is More Suitable

Use Batch Apex when the process involves complex logic, large datasets or controls that become difficult to manage in Flow.

Test the job in a sandbox first. Large updates can fire validation rules, triggers, emails and related-record automation in ways that are easy to miss during development.

Which Salesforce Mass Update Method Should You Use?

For a quick change across fewer than 200 selected records, use a list view.

Data Import Wizard is the practical middle option for supported objects and files up to 50,000 records. Data Loader handles larger datasets, Opportunities, custom objects and jobs that need detailed error logs.

Flow suits recurring rules. Apex handles developer-led batch processing.

Object support, permissions and existing automation often decide the final choice as much as record count does, which is really the core of good record management in Salesforce.

Frequently Asked Questions

How do I mass update records in Salesforce? 

Use list-view inline editing for a small batch, Data Import Wizard for supported CSV updates or Data Loader for larger and more complex jobs. Flow and Apex handle recurring updates.

Can I update multiple Salesforce records at once?

You can, through list views, CSV imports or automation. Which one fits best comes down to the object involved and how many records you’re touching.

Can I mass update Salesforce records without Data Loader?

List views and Data Import Wizard don’t require it. Once a Flow is active, it can also handle recurring changes without any manual upload at all.

Can I mass update Opportunity records in Salesforce? 

Yes. List views work for supported editable fields. Data Loader is the usual choice for CSV-based Opportunity updates involving several fields or a large dataset.

What is the difference between Data Import Wizard and Data Loader? 

Data Import Wizard runs in the browser and accepts up to 50,000 records. Data Loader is a separate client application that supports all standard and custom objects and files up to 5 million records.

Can I undo a Salesforce mass update? 

There’s no universal undo command for every bulk update. Restore the original values from the backup export.

Why did some records fail during the bulk update? 

Usually it traces back to invalid values, missing permissions, a validation rule, a locked record or a field mapped incorrectly. The error file will name the specific reason, so check it before rerunning anything.