How to Bulk Update Email Addresses in HubSpot

Email addresses are the primary identifier in HubSpot. They are how contacts are deduplicated, how emails are delivered, how forms match submissions to existing records, and how integrations sync data between systems. When email addresses need to change — because of a domain migration, a typo pattern, or a formatting standardization — the update needs to be done carefully. A mistake in the email field has outsized consequences compared to a mistake in almost any other property.

This guide covers the scenarios that require bulk email address changes, the risks involved, and how to execute them safely.

Here is what a bulk email domain replacement looks like with preview and rollback:

Why email addresses change

Corporate domain migrations

The most common reason for bulk email updates. Your company changes its domain from acmecorp.com to novacorp.com, or you acquire a company and need to move their employees from acquired.com to parentcompany.com.

Every contact record for employees at the affected company has an email ending in the old domain. Internal CRM records, partner contacts, and customer-facing employee entries all need updating.

Fixing import typos

A surprising number of email addresses in CRM databases contain systematic typos introduced during imports. Common ones:

• @gmial.com instead of @gmail.com
• @yaho.com instead of @yahoo.com
• @outlok.com instead of @outlook.com
• Double dots: [email protected]
• Missing TLD: user@company (no .com)

These are often imported from third-party lists, event registration platforms, or legacy CRM systems that did not validate email format on entry. A single import with a bad spreadsheet column can introduce hundreds of malformed emails.

Email provider migrations

When a company moves their email from one provider to another — say, from a legacy on-premises Exchange server to Google Workspace — the email domain sometimes changes. [email protected] becomes [email protected], or a vanity domain gets consolidated into the primary domain.

Standardizing email formatting

Email addresses are technically case-insensitive (RFC 5321 says the local part before the @ can be case-sensitive, but virtually no provider enforces this). In practice, having [email protected] and [email protected] in your database creates visual inconsistency in reports and can cause duplicate detection to fail in some tools.

Lowercasing all email addresses is a common standardization step, especially after merging data from multiple sources.

The risks of changing email addresses

Email updates carry specific risks that do not apply to other properties:

Deduplication conflicts

HubSpot uses email as the primary deduplication key for contacts. If you change Contact A's email to an address that already exists on Contact B, you have a conflict. HubSpot will not allow two contacts to have the same email address. Depending on how the update is applied, it may fail silently, merge the records, or throw an error.

Before running a bulk email update, verify that the new email addresses do not already exist in your database. For domain migrations, this usually is not an issue (if nobody in your database has the new domain yet). For typo corrections, it could be — fixing [email protected] to [email protected] might collide with an existing [email protected] contact.

Marketing email impact

Contacts in HubSpot are subscribed or unsubscribed based on their email address. If you change a contact's email address, HubSpot treats the new address as the contact's email going forward. The contact's subscription status follows the contact record, not the email string. This means:

• Marketing emails will go to the new address (good — that is what you want)
• The contact's opt-in history stays intact (good)
• But if the new email address was previously used by a different contact who unsubscribed, there could be compliance implications (bad)

Form submission history

Historical form submissions are linked to the contact record, not the email string. Changing the email does not retroactively update form submission data. If you search form submissions by email, the old email will still appear in historical submissions.

Integration sync

If HubSpot syncs contacts with Salesforce, Intercom, Mailchimp, or other platforms, an email change in HubSpot may trigger sync events. Depending on the integration, this could update the email in the connected system (desired), create a duplicate in the connected system (undesired), or break the sync mapping if the integration uses email as the matching key.

Review your active integrations before running bulk email changes and understand how each one handles email updates.

How to update email addresses safely

Step 1: Export and analyze

Before changing anything, export the contacts whose emails you plan to update. In HubSpot, create a list filtered by the email pattern you want to change (e.g., email domain contains "acmecorp.com") and export it to CSV.

In the spreadsheet, review:

• Total count of affected contacts
• Are there contacts in this list who should NOT have their email changed? (External partners with legitimate @acmecorp.com addresses, for example)
• Are there contacts with multiple email addresses? (HubSpot supports additional email addresses on contact records)

Step 2: Check for collisions

For each email you plan to create (the new email after replacement), verify it does not already exist in HubSpot. For a domain migration, this means checking whether any contacts already have emails on the new domain. If they do, you need to decide: merge the records, or skip the update for those contacts.

Step 3: Notify affected teams

Tell your marketing, sales, and customer success teams that email addresses are about to change. They should:

• Pause any email campaigns scheduled to send during the update window
• Be aware that contacts may temporarily appear with old email addresses in their views
• Know not to manually edit email addresses during the update (to avoid conflicts)

Step 4: Run the replacement

Using SearchReplace, select Contacts as the object type and Email as the property.

For a domain migration:

• Search mode: Substring
• Find: @acmecorp.com
• Replace with: @novacorp.com

The preview shows every contact whose email contains @acmecorp.com with the proposed new email. Review the list for any contacts that should be excluded (right-click to open them in HubSpot if you need to check their record).

For typo corrections:

• Search mode: Exact match or Substring depending on the typo
• Find: @gmial.com
• Replace with: @gmail.com

For case standardization using regex:

• Search mode: Regex
• Find: [A-Z] (matches any uppercase letter)

Note: full case conversion (lowercasing an entire email) is best handled with a regex replacement that uses a lowercase flag, or by targeting specific known uppercase patterns.

Step 5: Verify

After the replacement completes:

1. Spot-check 10-15 contacts in HubSpot to verify their emails are correct
2. Send a test email to a few of the updated addresses to confirm deliverability
3. Check your integration dashboards for any sync errors triggered by the email changes
4. Verify that HubSpot's duplicate management did not flag any new duplicates

Step 6: Update related records

Email addresses do not only live on contact records. Check these locations for the old email pattern:

• Company records — Some company records have a "Company email" or similar property
• Deal records — Deal descriptions or custom properties referencing contact emails
• Ticket records — Tickets created via email may reference the old email in the subject or description
• Notes and activities — Call notes, logged emails, and task descriptions may contain the old email

Run separate find-and-replace operations on these object types if needed. Each one has its own preview and rollback.

Handling secondary email addresses

HubSpot contacts can have multiple email addresses. The primary email is the one used for deduplication and marketing emails. Additional emails are stored as secondary addresses.

When migrating domains, you may want to:

1. Add the new email as a secondary address first
2. Verify deliverability to the new address
3. Then swap the primary and secondary (making the new address primary)

This two-step approach gives you a safety net — if the new email bounces, the old one is still the primary. However, HubSpot's UI makes bulk management of secondary emails difficult. The API supports it, but it is not exposed in the standard import or list view editing tools.

For most domain migrations, a direct swap of the primary email is sufficient, especially when you have preview and rollback available. If the migration fails for specific contacts, you can roll back and address those individually.

Monitoring after the change

In the week following a bulk email change:

• Watch bounce rates — If marketing emails start bouncing at higher rates, some of the new email addresses may be invalid. The rollback window lets you revert if needed.
• Check integration health — Look for sync errors in your connected apps.
• Monitor form submissions — If existing contacts submit forms with their old email address, HubSpot may not match the submission to their record (since the record now has the new email). Consider keeping the old email as a secondary address to catch this.
• Review workflows — Any workflow that triggers on email address changes will have fired for every updated contact. Check that those workflow enrollments were handled correctly.

Email address changes are among the highest-stakes bulk operations you can run in a CRM. The combination of preview, targeted replacement, and one-click rollback is not just convenient — it is the minimum level of safety you should expect when modifying the field that identifies every contact in your database.