Splitting & parsing names
Splitting names means breaking a single full-name column into separate first, middle, and last name fields so each piece can be used on its own — for personalization, sorting, or a CRM import. Sigmera parses a name column entirely in your browser: it splits each name, you preview and fix the tricky rows, and you download a clean file with nothing uploaded to a server.
Last updated: June 2026
What name parsing is
Name parsing is the decomposition of a single “full name” string into its component fields — typically first (given) name, optional middle name, and last (family) name, with prefixes and suffixes pulled aside. The basic heuristic is a split on whitespace: the first token is the given name, the final token is the family name, and anything between is the middle name. That heuristic is right most of the time and wrong in exactly the cases that matter most, which is what makes name parsing deceptively hard.
Why it matters
Almost every downstream system wants names in separate fields. Email and SMS personalization needs a first name on its own — “Hi Ada” reads naturally, “Hi Ada Lovelace” does not. Alphabetical sorting and reporting need the last name as a discrete field. CRMs and applicant-tracking systems store first and last name in distinct columns and will either reject a single combined field or dump the whole name into “first name”, leaving the last-name field blank. Getting the split right once, at import time, prevents awkward mail merges and broken sorting for the life of the record.
The hard cases
A simple split-on-space works until it doesn’t. The cases that defeat it are common enough that you will hit them in any real list:
- Compound surnames. “van der Berg”, “De La Cruz”, and “Mac Donald” have multi-word family names. A last-space split captures only “Berg”, “Cruz”, or “Donald” and misfiles the particle as a middle name.
- Prefixes and suffixes. Titles (Mr., Dr., Prof.) and suffixes (Jr., Sr., III, PhD) must be extracted into their own fields. Left in place, “Jr.” becomes part of the surname and breaks both matching and sorting.
- Last-name-first order. “Lovelace, Ada” reverses the usual order. A comma is the signal to flip the parse, but a parser that ignores it puts the surname in the first-name field.
- Single-token and mononym names. Some people have one name, and some cells hold a company rather than a person. Forcing a last name onto a single token invents data that was never there.
- Cultural ordering. In many cultures the family name comes first. There is no universal algorithm, which is the deeper reason name parsing always needs a human-reviewable preview rather than blind automation.
How to approach it
Start by stripping recognizable prefixes and suffixes into their own columns. Detect a comma to handle “Last, First” order, and recognize common surname particles so compound family names stay together. Apply the first-token / last-token split to what remains, and treat single-token cells as a special case rather than forcing a blank field. Critically, preview the result and correct the handful of rows the rules get wrong — name data is too varied for any algorithm to be perfect, so review is part of the process. Because Sigmera runs all of this in the browser, the names — personal data under GDPR — never leave your device, satisfying the data-minimization principle of GDPR Article 5.
In this topic
The tool, guides, and real-world use cases for splitting a full-name column.
Frequently asked questions
- How do you split a full name into first and last name?
- The basic rule is to split on the space: everything before the first space is the first name, everything after the last space is the last name, and anything in between is the middle name. This handles the common 'First Last' and 'First Middle Last' cases, but it breaks on compound surnames, prefixes, and suffixes — which is why a preview and per-row review matter.
- What about compound and multi-word surnames?
- Names like 'van der Berg', 'De La Cruz', or 'Mac Donald' have surnames made of several words, so a naive last-space split puts only the final word in the last-name field. A robust parser recognizes common surname particles (van, von, de, la, der, bin, al) and keeps them with the surname, but no rule is perfect, so a preview lets you correct the rows that need it.
- How do you handle titles and suffixes like Dr. or Jr.?
- Prefixes (Mr., Dr., Prof.) and suffixes (Jr., Sr., III, PhD) should be stripped into their own fields or removed, not left in the first or last name. If 'Jr.' lands in the last-name column, you end up with two people named 'Smith' and 'Smith Jr.' who look different to your CRM. Pull these out before splitting the core name.
- Does splitting names in the browser upload my data?
- No. The name splitter runs entirely in your browser using client-side JavaScript, so the file never leaves your device and nothing is sent to a server. Because names are personal data under GDPR, processing them locally keeps you compliant with the data-minimization principle of GDPR Article 5 — zero bytes are uploaded.