HubSpot Email Domain Migration: Update @company.com Across All Contacts

Email domain migrations happen for plenty of reasons. A company acquisition merges two domains. A rebrand retires the old domain in favor of a new one. A startup graduates from a generic Gmail address to a proper corporate domain. Or a legal entity restructures and the email domain changes with it.

Whatever the reason, when email addresses change, your CRM has to change with them. And in HubSpot, that's not as straightforward as it should be.

Email is the primary identity key in HubSpot. It's how contacts are deduplicated, how form submissions are matched to existing records, how email tracking works, and how many integrations identify records across systems. Changing an email address isn't just a property edit — it can affect associations, deduplication logic, email delivery, and integrations.

This guide covers how to plan and execute an email domain migration in HubSpot, the pitfalls to watch for, and how to handle it at scale.

Here is what swapping an email domain across your entire contact database looks like:

Understanding how HubSpot uses email addresses

Before changing any email addresses, you need to understand how HubSpot treats them.

Primary email. Every contact in HubSpot has a primary email address. This is the main identifier used for deduplication, form submission matching, and email delivery. When you update a contact's primary email, HubSpot doesn't delete the old address — it moves it to the "Additional emails" field. This is important: it means old emails aren't lost, but they do stay on the record.

Additional emails. Contacts can have multiple email addresses. These are used for deduplication — if someone fills out a form with any of their listed emails, HubSpot matches them to the existing record. After an email migration, the old domain addresses will sit in the additional emails field unless you explicitly remove them.

Company domain. Separate from contact emails, every company record has a "Company domain name" property. HubSpot uses this for automatic company-to-contact association. If you change a contact's email domain without updating the company's domain, the auto-association logic may create unintended results.

Email delivery. HubSpot sends marketing emails to the primary email address. If the old domain is still active and forwarding to the new domain, there may be no immediate issue. But if the old domain is being decommissioned, any contacts still using the old email will bounce.

Planning the migration

A successful email domain migration in HubSpot requires planning across several dimensions.

Scope assessment

First, determine the scope. How many contacts need their email addresses updated? Common scenarios:

• Your company's employees. If you're migrating your own company's domain, you might have 20-200 internal contacts in HubSpot that need updating. This is usually manageable manually.
• A client or partner company. If one of your key accounts is changing domains and you have hundreds of contacts at that company, you'll need a bulk approach.
• An acquired company. Post-acquisition, you may need to migrate thousands of contacts from the acquired company's domain to the parent company's domain.

To find all affected contacts, filter your contacts list by "Email contains @olddomain.com." Note the count — this determines whether you need a manual, CSV, or tool-based approach.

Timing

Coordinate the email migration with the actual DNS and mailbox migration. The ideal sequence:

1. New domain mailboxes are provisioned and forwarding is set up from old to new
2. Email addresses in HubSpot are updated
3. Old domain forwarding continues for 3-6 months to catch stragglers
4. Old domain email addresses are removed from HubSpot records

Don't update HubSpot email addresses before the new mailboxes are active. If you send a marketing email to an @newdomain.com address that doesn't exist yet, the bounce will hurt your sending reputation.

Communication

Notify your team before making bulk email changes. Sales reps who have active conversations with contacts at the affected domain need to know that email addresses are changing. Otherwise, they'll see unfamiliar addresses on records they're working and assume something is wrong.

Executing the migration: three approaches

Manual editing (1-50 contacts)

For small numbers, manual editing is feasible. Open each contact, click the email address, enter the new address, and save. HubSpot will automatically move the old address to "Additional emails."

Time estimate: 1-2 minutes per contact, or up to 100 minutes for 50 contacts.

Risk level: Low for small batches, but error-prone for anything larger.

CSV export and import (50-5,000 contacts)

The CSV approach involves:

1. Export: Filter contacts by "Email contains @olddomain.com" and export the list. Include at minimum the Record ID, Email, First Name, and Last Name columns.
2. Edit: In your spreadsheet, use find-and-replace to change "@olddomain.com" to "@newdomain.com" in the Email column.
3. Import: Re-import the CSV with "Update existing contacts" selected. Map the Record ID column to HubSpot's Contact ID for reliable matching.

Critical warning: When importing, make sure you map to the contact's Record ID, not their email. If you match by email, HubSpot will look for contacts with the new email address — which don't exist yet — and create duplicates instead of updating existing records.

Time estimate: 30-60 minutes regardless of record count, plus verification time.

Risk level: Medium. Column mapping errors can create duplicates or overwrite the wrong fields.

Bulk search and replace (any volume)

A purpose-built tool handles this more safely:

1. Select Contacts as the object type and Email as the property
2. Search for "@olddomain.com"
3. Replace with "@newdomain.com"
4. Preview every change — verify that the right contacts are affected and the new email addresses look correct
5. Apply the changes

Time estimate: 5-10 minutes regardless of volume.

Risk level: Low. The preview step catches errors before they're committed, and rollback is available if anything goes wrong.

Handling edge cases

Email domain migrations always surface edge cases that weren't obvious during planning.

Contacts with multiple email addresses. A contact might have both a personal email ([email protected]) and a work email ([email protected]). You only want to change the work email. Make sure your search is specific enough to avoid changing non-matching addresses.

Contacts at sub-domains. If the old domain had sub-domains ([email protected], [email protected]), decide whether those sub-domains are also migrating. Your search pattern needs to account for this — searching for "olddomain.com" will match both "olddomain.com" and "mail.olddomain.com."

Distribution lists and aliases. Addresses like [email protected] or [email protected] might be distribution lists rather than individual contacts. These may need different handling depending on whether they exist as contacts in HubSpot.

Bot and system addresses. Integrations sometimes create contacts with system email addresses ([email protected], [email protected]). Decide whether these should be migrated, deleted, or left as-is.

Existing contacts at the new domain. If some contacts already have @newdomain.com addresses (perhaps they were early adopters of the new domain), make sure your migration won't create conflicts or duplicates.

Post-migration checklist

After updating email addresses, verify these items:

Company associations. Check that contacts are still associated with the correct company records. If the company domain property also needs updating (see our guide on updating company domains), do that as a separate step.

Active workflows. Review any workflows that filter by email domain. A workflow that enrolls contacts where "Email contains @olddomain.com" will stop matching after the migration. Update the filter criteria.

Active lists. Same as workflows — any active list filtered by the old email domain needs updating.

Email subscriptions. Marketing email subscriptions are tied to the email address. When you update a contact's primary email, HubSpot carries the subscription status to the new address. Verify this by checking a few records' subscription pages.

Integrations. Any tool that syncs with HubSpot using email as a matching key needs attention. Salesforce, Outreach, Marketo, and similar tools may need their own migration or re-mapping.

Bounce monitoring. After the next marketing email send, monitor bounce rates for the new domain addresses. If the new mailboxes aren't fully provisioned, you'll see bounces that need immediate attention.

Additional emails cleanup. After a grace period (typically 3-6 months), consider removing the old @olddomain.com addresses from contacts' additional emails fields. This prevents old-domain form submissions from matching to existing contacts after the old domain is decommissioned.

Timeline for a clean migration

An email domain migration doesn't have to be stressful. With the right planning and tools, it's a focused operation that takes a morning instead of a week.

---

Migrating email domains in HubSpot? SearchReplace lets you preview every change before it happens and roll back with one click if anything looks off.