How to Normalise Job Titles in a Lead List Before a Mail Merge or CRM Import

Normalise the title column before it reaches a merge field or a CRM. Export the list, paste the title column (or the whole CSV) into the job title normalizer, choose the short or long style, and download the file with a new title_clean column. Every spelling of a role becomes one title, abbreviations are spelled out and the noise that lead databases copy from LinkedIn headlines is removed.

Sources, read 2 November 2026: HubSpot's default contact properties (the Job Title property is free text) and the US Bureau of Labor Statistics Standard Occupational Classification, which groups thousands of job-title spellings into far fewer occupations for the same reason: one role, many names.

Why titles need cleaning

Lead databases fill the title from profiles and form fills, so one export mixes full headlines ("Founder | Helping SaaS teams grow"), company names after an @, ALL CAPS, emoji and every abbreviation people use. That causes two separate problems:

Where the title goes	What a messy title does
A {{title}} merge field	Prints the raw value: "as SR. VP, SALES @ ACME | Speaker"
A CRM property	Splits one role into VP Sales, Vice President, Sales, Sales VP, V.P. Sales and VP of Sales
Segments and routing rules	Catch only the spelling the rule was written for
Persona reports	Undercount every role that has several spellings

Step by step

1. Export the list with its title column. Apollo calls it Title, Sales Navigator exports Job Title, HubSpot Job Title.
2. Paste or upload it into the job title normalizer. Choose short or long style, and Title Case for a CRM property or lower case if the title sits mid-sentence in your copy ("most VPs of sales I talk to").
3. Press Normalise and read the rows marked worth a look. These are titles it trimmed but couldn't map, or ones with ambiguous acronyms. CPO, CSO, CCO and CDO are left as written because they stand for different roles at different companies.
4. Download the CSV. Every original column is kept; map title_clean to the merge field or the CRM property.
5. Tag seniority if you need it. The job title seniority filter reads the cleaned column and labels each row C-level, VP, director, manager and so on.
6. Check the addresses. Upload the file on the verify page before the sequence or import, so the cleaned rows are also rows that can receive mail.

What it changes and what it leaves

Changed: VP, SVP, EVP and AVP spellings; the unambiguous C-level titles; "VP, Sales", "VP - Sales" and "Sales VP" to "VP of Sales" (and the same for Director and Head); Sr., Jr., Mgr, Mktg, Acct, Exec and Biz Dev spelled out; "Founder/CEO" to "Founder & CEO". Removed: the company after " at " or " @ ", roles after a "|", taglines after a long dash, bracketed notes like "(Hiring!)" and emoji. Kept: brand casing (HubSpot Admin, iOS Developer) and acronyms (HR, SEO, SDR).

Honest limits

• Patterns, not a model. A title it has never seen a variant of is trimmed and re-cased, not mapped. Read the flagged rows.
• English only. Non-English titles are trimmed and re-cased, not translated.
• Titles go stale. People change jobs; the B2B contact data decay post covers how fast. A clean title can still be last year's title.
• Nothing about the address. A perfectly normalised row can still bounce.

For the copy side of personalization, see cold email personalization at scale and mail merge blank fields.

Where SimpleVerifier fits

Run the cleaned file through the verify page; the first 100 checks are free with a Google sign-in. Pro is $39 a month with the first 100,000 checks a month at full speed, then slower, never cut off. See pricing.