Bulk-edit sales records: 4 checks before saving changes

Apply the same correction to several sales records while checking selection, old values, update behavior, and required-field exceptions.

• Verify selection scope: In HubSpot, selecting the checkbox at the top left of the table or board selects all records on your current page or pipeline HubSpot.
• Understand overwrite behavior: For text or single-select properties, a bulk edit overwrites the existing value in the property for the selected records HubSpot.
• Note required-field exceptions: Pipedrive’s required fields feature does not stop deals from progressing if fields are updated through import, bulk-editing, API, automations, or third-party integrations Pipedrive.
• Check save constraints: If you changed data for a required column, it needs to contain data otherwise you won't be able to save your changes Microsoft.
• Save a pre-change copy: Export current values before applying corrections to maintain a record of original data for review.

Before saving a bulk correction, check four things: the selected records, a saved copy of the old values, whether the change replaces or appends values, and which required-field checks apply to that update path. These checks are editorial recommendations, not a vendor-certified recovery procedure.

Selection determines which records receive the correction. Before touching any field, verify that the interface is showing exactly the records you expect to modify. The mechanism for selecting records varies by platform, and each has specific prerequisites or scope limitations that affect what gets included.

To select all records on your current page or pipeline, select the checkbox at the top left of the table or board, according to HubSpot. According to HubSpot, in table view, to select all of the records in the view, click the Select all [number] [records] link. The number displayed in the link text indicates the count of records that will be affected.

Pipedrive approaches selection through filtering before any editing action begins. According to Pipedrive, before making changes, use filters to narrow down the items you want to work with. You must actively define the scope using filters prior to initiating the edit.

Microsoft Power Apps requires specific administrative privileges before the selection mechanism is even available. According to Microsoft, your administrator must grant you the Bulk Edit miscellaneous privilege to edit multiple rows. Without this permission, the option to select multiple rows for bulk editing may not be accessible or functional. Once granted, the process involves navigating to the view page containing the list of rows. According to Microsoft, to edit multiple rows, go to view page with the list of rows and select two or more rows. Note that Microsoft labels this bulk-edit page pre-release and subject to change.

The table below summarizes how each tool documents the selection step for bulk editing. Each row reflects only the specific selection method and scope stated in that publisher's documentation.

According to HubSpot, the selection control targets the current page or pipeline view. According to Pipedrive, filtering is the recommended precursor to bulk changes. According to Microsoft, the process requires navigating to the row list view first. According to Close, the documented bulk operation applies specifically to Leads.

These selection methods define the initial scope of the records targeted for the update. They do not describe the update behavior, such as whether values are replaced or appended, nor do they detail required-field enforcement. The selection step is distinct from the save action. Verify that the filtered or selected set matches the intended correction scope before proceeding to the next check.

For context on how stage changes might interact with these records, see Open, won, and lost stage rules in 4 sales tools. If the correction involves deal values, review Weighted deal amount: 5 fields to check HubSpot, Pipedrive to ensure the field definitions align with your forecast calculations.

Export the current values of the records you plan to change before you apply the bulk correction. This pre-change copy lets you verify the old values if the update behaves differently than expected or if a required-field exception alters the result. Treat the export as a record of what was there, not as a guaranteed rollback mechanism, because the export file captures field values at the time of download.

When you initiate an export in HubSpot, note that download links to export files will expire after 30 days, according to HubSpot. If you do not download the file within that window, the link will no longer be valid, and you will need to run a new export. Plan your bulk edit so that the export is downloaded immediately after generation. HubSpot also limits export volume: you can complete up to 300 exports within a rolling 24-hour window, and up to three exports simultaneously, according to HubSpot. If you are testing multiple field combinations or record subsets, space out your export requests to stay within these concurrent and rolling-window limits.

File format affects what you can capture. For XLS and XLSX files, there is a limit to the number of columns that can be exported: 256 for XLS and 16,384 for XLSX, according to HubSpot. If your sales records include many custom properties, check whether the XLS format will truncate your column set. Use XLSX if you need to preserve a wider range of fields in your pre-change copy.

In Close, the export link behaves differently. For your privacy, this link will expire automatically after 7 days, according to Close. The shorter expiry window means you should download the Close export file immediately after generating it. Do not assume the link will remain available for a week if you delay the download; the system enforces the 7-day limit automatically.

When applying a correction to multiple records, the system may overwrite existing data or add to it. You must identify which mode is active before saving. In HubSpot’s “Bulk edit records” documentation, the behavior depends on the property type and the specific option selected.

For text or single-select properties, the standard bulk edit action overwrites the existing value in the property for the selected records according to HubSpot. There is no automatic merging of the old and new values in this default state.

If your goal is to add new values while keeping the current ones, you must explicitly change the update behavior. To add the selected values while maintaining the existing values, select “Append to current value(s)” according to HubSpot.

The distinction matters because a single misconfiguration can corrupt your pipeline data. If you intend to fix a typo in a company name, you need the overwrite behavior. Checking this setting prevents the accidental deletion of historical data during a bulk correction.

Review the property type you are editing. This check ensures your correction aligns with your data management strategy.

Required-field rules vary significantly by update path, so you must verify which checks apply to your specific bulk-edit method before saving. The bulk-edit interface itself enforces the requirement, preventing the save if the field is empty. Understanding these exceptions prevents failed saves or unexpected data gaps.

Pipedrive required fields will not stop deal progress According to Pipedrive, the required fields feature currently will not stop deals from progressing if the fields are updated through import, bulk-editing, API, automations, or third-party integrations.

Pipedrive: automation triggers and undo limits When using the bulk-edit feature in Pipedrive, the “Run automations” option is selected by default, and changes can’t be undone after confirmation, according to Pipedrive. This creates a two-part risk: first, your bulk change may trigger downstream automations (such as email sequences or task creation) that you did not intend to activate for this specific correction. Second, because the changes are final upon confirmation, you cannot rely on a native “undo” button to reverse a mistake. You must save a pre-change copy of the old values before confirming the bulk edit, as covered in Check 2.

Pipedrive: activity scheduling limit The same Pipedrive documentation notes that you can add up to 100 activities at a time, according to Pipedrive. This is a limit on the number of activities you can schedule in a single bulk operation, not a limit on the number of field updates or records you can edit. Do not confuse this activity cap with a batch limit for field changes.

Microsoft Power Apps mobile access restriction You can't edit multiple rows with Power Apps mobile, according to Microsoft. If your workflow involves applying corrections while away from your desk, you cannot use the mobile app to perform bulk edits. This restriction applies to the bulk-edit feature specifically, but the multi-row correction workflow is not supported there.

Suppose a list shows 50 records and you mean to correct 10 of them. Export those 10 rows first and save the file on your computer. Select only those 10 records. For one text field, enter the corrected text, which overwrites the old text on each selected record. Leave every other field as it is. Confirm zero required fields are empty on the rows you are changing. Only then save the 10 updates. This walkthrough uses round figures to show the order of checks. It is not a record from a live pipeline.

Export the current values, download the file, confirm the selected records, and check whether the edit overwrites or appends before you save.

Does selecting the page select every matching record?

In HubSpot, selecting the checkbox at the top left of the table or board selects all records on your current page or pipeline, according to HubSpot. Confirm that your view filters match the exact set of records you intend to modify before proceeding.

Will a bulk edit replace existing field values?

For text or single-select properties, a bulk edit overwrites the existing value in the property for the selected records, according to HubSpot. The system replaces the previous data with the new value you provide during the update. Verify the update mode you are using to ensure it aligns with your correction intent.

Do required fields stop every bulk update?

Pipedrive states that the required fields feature won’t stop deals from progressing if the fields are updated through import, bulk-editing, API, automations, or third-party integrations, according to Pipedrive.

Can I bulk-edit sales records on mobile?

Microsoft documentation explicitly states that you can't edit multiple rows with Power Apps mobile, according to Microsoft. This limitation applies to the bulk edit functionality within that specific mobile environment.

What should I save before applying a correction?

Export your current values to create a pre-change copy before applying any bulk corrections. Download links to export files will expire after 30 days, according to HubSpot. Ensure you download and store the file immediately after generating the export link to retain access to the data.