Merging Email Lists After Company Acquisitions
Your company just acquired another business. Along with the product, team, and customers comes their email database. Maybe it is 50,000 contacts. Maybe it is 500,000. Either way, you need to merge it into your system without destroying your sender reputation in the process.
This is where companies regularly make expensive mistakes. They dump the acquired list into their existing email platform, blast a "welcome to the new brand" message, and watch their bounce rates spike and their domain reputation crash. The acquired database was built under different standards, verified at different times, and may contain contacts who have not heard from the old brand in months or years.
Pre-Merge Assessment
Before merging anything, assess the quality of the acquired database:
Age of the data. When was the database last actively used? Email data decays at 22-30% per year. A database that has been dormant for 12 months could have 25% or more invalid addresses.
Verification history. Was the list ever verified? When? Using what tool? If it was verified two years ago with a tool that does not resolve catch-all addresses, a significant portion may be undeliverable.
Engagement data. Pull engagement metrics from the acquired company's email platform. What percentage of the list was engaged in the last 90 days? 180 days? Never? This tells you how much of the list is actually active.
Source quality. Where did the contacts come from? Organic signups have different quality profiles than purchased lists or scraped data. If you cannot determine the source for a large portion of the database, treat it as high-risk.
Compliance posture. How was consent collected? Under what privacy policy? If the acquired company's privacy policy did not cover transfer of data to your company, you may have GDPR or CAN-SPAM obligations to address before sending.
Verification Before Merge
Run the entire acquired database through verification before importing anything into your system. This is non-negotiable. The cost of verification is tiny compared to the cost of a domain reputation crash.
Remove all invalid addresses. Flag all catch-all addresses for specialized verification through CatchallVerifier. Identify and handle role-based addresses per your policy. Remove disposable addresses. Flag risky and unknown addresses for careful handling.
For the catch-all segment specifically, the acquired database likely has a significant percentage (15-40% in typical B2B databases) of catch-all addresses. Running these through CatchallVerifier before merging means you import only deliverable addresses, rather than importing a large uncertain segment that could generate bounces.
Gradual Migration Strategy
Do not send to the entire merged list at once. Introduce the acquired contacts gradually:
Week 1-2: Send to recently engaged contacts only. Start with contacts from the acquired database who engaged within the last 30 days. These are the most likely to be valid and interested. Send a clear transition email explaining the acquisition and what to expect.
Week 3-4: Add the 31-90 day engagement tier. Expand to contacts who engaged within the last quarter. Monitor bounce rates and complaints closely. If bounce rates exceed 2% or complaints exceed 0.1%, pause and investigate.
Week 5-8: Cautiously add older engagement tiers. If metrics look good, gradually add contacts who engaged in the last 91-180 days. Continue monitoring. These older tiers will have higher invalid rates even after verification, because engagement does not guarantee the address is still active.
180+ day unengaged: Re-engagement campaign. For contacts who have not engaged with the acquired brand in over 6 months, run a re-engagement campaign before adding them to regular sends. This segment has the highest risk of spam traps and invalid addresses.
Brand Transition Communication
The first email to acquired contacts is critical. It sets expectations and prevents confusion that leads to spam complaints.
Be transparent about the acquisition. Tell recipients that the company they signed up with has been acquired by your company. Explain what this means for their subscription: what content they will receive, how frequently, and from what sender address.
Provide a clear opt-out. Make it easy for anyone who does not want to continue under the new brand to unsubscribe. Yes, you will lose some contacts. That is far better than the spam complaints you will get from confused recipients who do not recognize your brand.
Use the acquired brand's sending infrastructure initially if possible. If the acquired company sent from marketing@oldcompany.com, send the transition email from that address. Switching to your brand's email address immediately means recipients will not recognize the sender, which increases spam reports.
Technical Merge Considerations
Data mapping. The acquired database probably uses different field names, formats, and conventions than yours. Map fields carefully: their "Company Name" might be your "Organization." Their "Job Title" might need to split into your "Title" and "Department" fields.
Deduplication. Run cross-database deduplication before merging. Some contacts will exist in both databases (they were customers or prospects of both companies). Merge these duplicates using the rules discussed in our deduplication guide, keeping the most complete and recent data.
Consent records. Preserve the consent history from the acquired database. When the contact opted in, what they opted in for, and under what privacy policy. You may need this for GDPR compliance, especially if regulators ask about the legal basis for processing contacts from the acquired company.
Suppression list merge. Import the acquired company's suppression list (unsubscribed, complained, bounced contacts) into your suppression system. Just because someone unsubscribed from the old brand does not mean they want to hear from the new brand. Respect their previous opt-out.
Monitoring Post-Merge
For at least 8 weeks after beginning the merge, monitor these metrics more closely than usual:
Bounce rate by segment (new vs existing contacts). Spam complaint rate by segment. Domain reputation on Google Postmaster Tools. Engagement rates for acquired contacts vs existing contacts. Blacklist status.
If any metric moves in the wrong direction, pause sends to the problematic segment immediately. Investigate, clean further, and resume only when you are confident the issue is resolved.
A well-executed list merge preserves the value of the acquired database while protecting your existing sender reputation. A poorly executed one can take weeks or months to recover from. Take the time to do it right.
