A step by step guide to building a B2B email marketing list from your team's existing email and calendar history, covering mailbox selection, extraction, deduplication, segmentation, and export.
A common situation for B2B marketers is being asked to run a campaign, needing a contact list to run it against, and facing a choice between a CRM with limited coverage, a data vendor subscription, or a slower approach built on gated content and paid ads. In most organizations, a fourth option already exists but has not been organized: contact data generated by normal email activity across the sales, customer success, support, and leadership teams. This page walks through the process of extracting that data and turning it into a usable, segmented marketing list.
A ten-person sales team typically accumulates approximately 15,600 contacts over two years of normal email and calendar activity. Adding a customer success team's active accounts, a support inbox's inbound contacts, and a leadership team's external relationships increases that number further.
These contacts differ from a purchased list in one significant respect: each one reflects a prior interaction with the company, whether an email exchange, a meeting, a deal thread, or a support request. That existing relationship is what makes this data more useful for marketing than contacts acquired from a data vendor or a lead generation campaign.
The limiting factor is not contact volume. It is that the data is spread across individual inboxes, stored in an unstructured format, and not accessible to the team that would use it for a campaign.
A few structural reasons explain why this contact data is rarely captured on its own.
Each inbox functions as a separate data silo. One team member may have a prospect's email address from an initial exchange. A second, copied on a later thread, may have their phone number from a signature. A third, with an ongoing account relationship, may have their current title and company. None of these records are complete individually, and a marketing team typically has access to none of them.
Contact data in signatures is unstructured. Email signatures are free text blocks that vary by person, company, and email client, which makes extracting structured fields from them manually impractical at any meaningful scale.
CRM coverage has gaps by design. Even organizations with consistent CRM habits tend to miss contacts who were copied on a thread, attended a meeting without becoming a tracked opportunity, or reached out directly without going through a formal qualification process. These contacts are often relevant to marketing despite being absent from the CRM.
Individual exports do not solve a team-level problem. If each team member exported contacts from their own inbox separately, the result would be overlapping, inconsistently formatted records still requiring deduplication and enrichment before they could be used in a campaign.
The contacts produced by each team differ, and it is useful to map this before connecting mailboxes.
Sales team mailboxes tend to produce prospects, active leads, deal contacts, and referral sources, generally suited to product announcements, nurture sequences, and pipeline re-engagement campaigns.
Customer success mailboxes tend to produce active account contacts, renewal decision-makers, and expansion contacts, generally suited to onboarding content, upsell campaigns, and customer event invitations.
Support inboxes tend to produce contacts actively engaged with the product, generally suited to product feedback requests, feature announcements, and satisfaction surveys.
Leadership mailboxes tend to produce strategic partners, investors, and high-value relationships that rarely appear in a CRM, generally suited to executive communications and partnership announcements.
Shared inboxes, such as a general info or sales address, often contain inbound contacts who reached out directly but were never entered into a CRM as a formal record.
It is not necessary to connect every mailbox at once. Many organizations begin with the sales team's mailboxes, confirm the results are useful, and add customer success, support, and leadership mailboxes afterward.
Mailboxes on Gmail, Outlook, or Office 365 are typically connected through an OAuth authorization, which does not require sharing or centrally storing passwords. Each team member authorizes their own mailbox individually, and this process generally takes a few minutes per mailbox.
Because the connection is OAuth based, passwords are not stored by the tool performing the extraction. Relevant security baselines to confirm with any vendor include SOC 2 Type II certification, GDPR compliance, and encryption of data at rest and in transit. Organizations with strict data residency requirements should also confirm whether on-premises or region-specific processing is available.
Individual authorization means no administrator needs to manage access on behalf of colleagues, and each team member retains control over their own mailbox connection.
At this stage, a choice is generally available between a one-time historical scan, which can typically extend back several years, and continuous scanning, which checks for new contact activity on an ongoing basis. Most organizations use both: the historical scan surfaces existing contacts immediately, and continuous scanning keeps the list current afterward.
Once mailboxes are connected, extraction runs across every inbox at the same time. Signature parsing identifies full name, job title, department, company, direct and mobile phone numbers, LinkedIn profile, and location, building a structured record for each contact without manual data entry.
Deduplication runs across all connected mailboxes simultaneously. When the same contact appears across multiple inboxes with slightly different name formatting, different phone numbers captured at different times, or an outdated job title alongside a current one, these entries are resolved into a single record using the most complete data available from each source.
Email validation is applied at extraction, and addresses that appear invalid or likely to be spam are flagged before export, so the resulting list does not need a separate validation step later.
Because contact information changes over time, typically decaying at a rate of 22 to 30 percent per year as people change roles and companies, continuous scanning updates existing records automatically when new signature data reflects a change, without requiring anyone to manually correct the record.
Once a contact database has been built, it can be segmented in several ways before export.
By interaction frequency. Tracking how often each contact has been emailed across all connected mailboxes allows a list to be divided by relationship warmth. Contacts with frequent, ongoing communication are generally suited to newsletters, product announcements, and upsell campaigns. Contacts with a history of interaction but no recent activity are candidates for a re-engagement sequence. Contacts who appeared only once, such as a single inbound email, typically warrant a more cautious approach.
By team source. Because each contact can be mapped to the mailboxes it appears in, a list can distinguish sales prospects from customer success accounts or support inquiries, so that a current customer and a cold prospect do not receive the same message.
By standard demographic fields. Title, industry, and location filters support more specific campaign targets, such as a particular seniority level within a target industry, or a geographic region for an event invitation.
A segmented list can be exported as a CSV or Excel file and imported into a platform such as Mailchimp, Constant Contact, MailerLite, or HubSpot. Exports can range from a small set of core fields, such as name, email, title, and company, up to a full export including all available data points.
For organizations that want the list to stay current without repeating a manual export, automation platforms such as Zapier or Make.com can push new or updated contacts to an ESP automatically as they are identified across connected mailboxes. Contacts can similarly be pushed directly to a CRM such as Salesforce, HubSpot, or Microsoft Dynamics, keeping the CRM and marketing list aligned without separate manual reconciliation.
Small teams of two to five people can typically connect all relevant mailboxes and run a historical scan in a single session. Most small teams surface several hundred to a few thousand contacts, a meaningful share of which were never formally recorded anywhere, and can export a working list the same day.
Mid-size teams of ten to fifty people generally start with the sales team's mailboxes, where a historical scan alone often surfaces contact volumes in the thousands. Adding customer success and support mailboxes afterward expands coverage and enables department-based segmentation, and continuous scanning keeps all lists current without additional manual effort.
Larger organizations generally connect mailboxes by department or function. Deduplication across all connected mailboxes becomes more valuable as the number of overlapping contact records grows, and CRM sync alongside ESP export, combined with automation through Zapier or Make.com, keeps marketing audiences current as the organization scales.
This varies by team size and history, but a ten-person sales team commonly accumulates around 15,600 contacts over two years of normal activity. Adding customer success, support, and leadership mailboxes generally increases that figure.
No. Many organizations begin with a single team, most often sales, confirm the results are useful, and add other departments in a later phase.
Records referring to the same contact across different mailboxes are compared and merged, typically based on matching or closely related email addresses and names, combining the most complete data available from each source into one record.
If continuous scanning is enabled, a contact's record updates automatically when a new email signature reflects a title or company change, without requiring anyone to manually correct the existing entry.
Yes. Because the data reflects actual email activity, contacts can be grouped by how often and how recently they have been in touch, distinguishing an actively engaged contact from someone who appeared only once.
Each mailbox is typically authorized individually by the person who owns it through OAuth, which does not require centrally managing credentials or involving IT for each connection.
The process generally begins with connecting a small set of mailboxes, most often the sales team's, and running a historical scan to see what surfaces before expanding to other departments. Most providers in this category offer a limited free scan, commonly covering the most recent 90 days of email history, before any paid commitment is required.
Related reading: for the full picture on why this approach works and how it compares to purchasing a contact list, see How to Build a B2B Email Marketing List from Your Team's Inboxes.
SigParser can securely scan one to thousands of employee mailboxes to extract email addresses and more. Get a demo to learn more.