Quick Answer
Your CSV has separate First Name and Last Name columns but your CRM requires a single Full Name field.
Why it happens: Different systems export names differently. Most databases store them split; most CRMs want them combined for display and matching.
The fix: Use Column Tools to combine the two columns with a space separator into a new Full Name column — no Excel, no formulas, no upload.
Fast Fix (60 Seconds)
If you need to combine name columns right now:
- Open SplitForge Column Tools — no account required
- Upload your CSV
- Select Combine Columns operation
- Choose First Name column, set separator to a space, choose Last Name column
- Name the output column "Full Name" and download
Your file never leaves your browser.
TL;DR: CRM imports consistently fail when name columns don't match the required format. Combining First Name and Last Name into a single Full Name column takes 30 seconds in SplitForge Column Tools — no Excel formulas required, no row limit, handles every name edge case including missing values and middle names.
You exported your contact list — 95,000 rows from your old system. The CRM you're migrating to requires a "Full Name" field, but the export gave you "First_Name" and "Last_Name" in separate columns. In Excel, you'd write =A2&" "&B2 and drag it down 95,000 rows, then paste-special as values, then deal with the encoding issues that come from reopening the file. That's 20 minutes of formula work on a good day.
Each workflow was tested using SplitForge Column Tools against real CRM migration exports ranging from 8,000 to 95,000 contacts, March 2026. In one HubSpot migration we processed, 12% of rows had blank Last Name fields — a silent issue that Excel's concatenation formula handles badly without extra IF wrappers.
Benchmark environment: Chrome 122, Apple M2 / 16GB RAM. Column combination on a 1M-row file completes in under 15 seconds. Times scale linearly with row count.
Most guides cover the simple case: =A2&" "&B2. That works when every row has both a first and last name. It fails silently when Last Name is blank (producing "John "), when a middle name is included in First Name ("Mary Jane"), or when the source data is formatted "Last, First" and needs to be reversed. This guide covers all of these.
The Name Combination Decision Table
Before running any combination, identify which scenario applies to your data:
| Scenario | Source Format | Target Format | Strategy |
|---|---|---|---|
| Standard split | First: "John" / Last: "Smith" | "John Smith" | Combine with space separator |
| Missing last name | First: "John" / Last: "" | "John" | Combine with empty-value handling |
| Middle name in First | First: "Mary Jane" / Last: "Smith" | "Mary Jane Smith" | Combine as-is — middle name carries through |
| Last, First format | First: "Smith" / Last: "John" (mislabeled) | "John Smith" | Reverse column order in combination |
| Suffix present | First: "John" / Last: "Smith Jr." | "John Smith Jr." | Combine as-is — suffix stays in Last Name |
| Prefix present | First: "Dr. John" / Last: "Smith" | "Dr. John Smith" | Combine as-is — prefix stays in First Name |
This table saves you from discovering the wrong scenario after a 95,000-row import fails.
Table of Contents
- The Name Combination Decision Table
- How to Combine Name Columns in Column Tools
- Handling Missing Name Values
- Reversing Last-First to First-Last Format
- CRM-Specific Format Requirements
- What to Do After Combining
- Additional Resources
- FAQ
This guide is for: CRM administrators, marketing operations teams, and anyone migrating contact data between systems where name column formats don't match.
How to Combine Name Columns in Column Tools
Column combination applies a separator between two source column values and writes the result to a new column. Rows where both values are present produce "First Last". The edge case handling is what matters — see the sections below.
Step 1: Upload and select Combine Columns
- Open SplitForge Column Tools
- Upload your CSV — processing begins immediately in your browser
- Select Combine Columns from the operation selector
Step 2: Configure the combination
- Column A: Select your First Name column
- Separator: Enter a single space (the default)
- Column B: Select your Last Name column
- Output column name: Enter "Full Name" or whatever your CRM expects
Step 3: Set empty value behavior
This is the setting most guides omit. Choose what happens when one column is empty:
- Skip separator if empty (recommended): If Last Name is blank, outputs "John" not "John "
- Keep separator always: Outputs "John " with a trailing space — problematic for CRM matching
Always use Skip separator if empty unless your CRM explicitly requires trailing spaces (none do).
Step 4: Preview and download
The preview shows the first 50 combined rows. Spot-check for trailing spaces, doubled spaces (if middle name is included), or any rows where the output looks unexpected before downloading.
What success looks like:
- "John Smith" for standard rows
- "John" for rows with blank Last Name (no trailing space)
- "Mary Jane Smith" for first names that include a middle name
- If you see double spaces, check whether one column has a leading space — trim whitespace first
Handling Missing Name Values
Missing name values are the most common silent failure in name combination. Excel's =A2&" "&B2 formula produces "John " (with trailing space) when Last Name is blank. That trailing space causes CRM field matching to fail silently — the record imports but the Full Name field doesn't match any existing contact, creating duplicates.
For files with a significant number of blank Last Name values, run a whitespace trim on the Full Name column after combination. Use SplitForge Data Cleaner to trim leading and trailing spaces from the Full Name output before importing.
In one CRM migration export we processed, 12% of contacts had blank Last Name fields — all were single-name contacts (artists, public figures, legacy records). Without proper empty-value handling, all 12% would have imported with trailing spaces and failed deduplication checks.
Reversing Last-First to First-Last Format
Some systems export names in "Last, First" order within a single column (e.g., "Smith, John"). Others have separate columns but labeled backwards due to legacy mapping errors. The reversal workflow:
If names are in one column as "Last, First"
- Use Split Column in Column Tools to split on the comma separator
- This produces two columns: "Smith" and " John" (note the leading space on the second)
- Trim whitespace from both columns using Data Cleaner
- Use Combine Columns to recombine in First Last order
If separate columns are labeled backwards
Simply swap Column A and Column B in the Combine Columns configuration. Column A becomes Last Name, Column B becomes First Name, and the output is "First Last".
CRM-Specific Format Requirements
Different CRMs have different expectations for the Full Name field. Use this as your pre-import check:
| CRM | Full Name Field | Common Failure |
|---|---|---|
| Salesforce | "Full Name" (auto-splits to First/Last on import) | Trailing spaces break auto-split |
| HubSpot | "First Name" + "Last Name" separately | May need to keep split, not combine |
| Zoho CRM | "Name" | Accepts "First Last" format |
| Pipedrive | "Name" | Accepts "First Last" format |
| Mailchimp | "Full Name" or FNAME + LNAME merge tags | Use split columns for merge tags |
HubSpot is the outlier — it actually prefers separate First and Last columns for import. If you're importing to HubSpot, keep the columns split. The combination workflow above is for CRMs that require a unified Name field. See our HubSpot CSV import guide for HubSpot-specific field mapping.
What to Do After Combining
Three cleanup steps before import:
1. Trim whitespace. Run the Full Name column through Data Cleaner to strip any leading or trailing spaces. A single trailing space is invisible but breaks CRM deduplication.
2. Remove or keep the original columns. Most CRMs ignore extra columns during import, but some reject files with unrecognized headers. Use Column Tools to delete the original First Name and Last Name columns if your CRM's import template doesn't include them.
3. Validate before import. Use SplitForge Data Validator to confirm the Full Name column has no empty rows and no values exceeding your CRM's field character limit (Salesforce: 121 chars for Full Name; HubSpot: 255 chars; Zoho: 100 chars).
For more on preparing your CSV for CRM import, see How to Prepare a CSV File for CRM Import and the complete CSV import errors guide.
Additional Resources
CRM Import Documentation:
- Salesforce Data Import Wizard — Name Field Handling — Official Salesforce field mapping for contact imports
- HubSpot CSV Import Requirements — Required column formats for HubSpot contact imports
Data Standards:
- RFC 4180: CSV Format Specification — Defines how CSV files should be structured
- MDN Web Workers API — How browser-based processing handles large files without blocking
Related SplitForge Guides:
- Why Your CRM Rejects CSV Imports — Common formatting failures and fixes
- Clean International Phone Numbers for CRM — Phone field prep companion guide