The Google export is not doing anything wrong here; it is Access interpreting the CSV and mapping the “Name” data into separate First/Middle/Last name fields based on delimiters in the file. To handle this, there are two practical approaches: clean the CSV before import, or adjust how the data is imported/mapped.
Since the context focuses on CSV import behavior and fixing import issues, the safest supported pattern is:
- Open and inspect the CSV in Excel
- Locate the exported contacts CSV file from Google (typically
contacts.csv).
- Open it in Excel.
- Confirm which column(s) contain the full name and how they are separated (spaces, commas, etc.).
- Normalize the name into a single column in Excel
- If Google exported separate columns (e.g.,
Given Name, Additional Name, Family Name), insert a new column such as FullName.
- Use a formula to concatenate them into one field, for example:
-
=TRIM(A2 & " " & B2 & " " & C2)
- Copy the formula down for all rows.
- Convert the formulas to values (Copy → Paste Special → Values) so the CSV contains plain text.
- Delete the original separate name columns if not needed.
- Save correctly as CSV
- Save the file as CSV.
- When Excel prompts “are you sure you want to save it in CSV format?”, choose Yes each time so the CSV structure is preserved.
- Import into Access using the cleaned CSV
- In Access, import this edited CSV into a new table.
- Map the
FullName column to a single text field (e.g., Name) in the Access table.
This approach prevents Access from splitting the name into First/Middle/Last because the CSV now has a single, already-merged name column. If some rows still split differently, check those specific rows in Excel for extra delimiters or formatting and correct them before re-importing.
References: