Apollo.io
Close Contacts5 fieldsHow to import Apollo.io data into Close
Apollo.io exports people lists as CSV files. This template maps the export to Close's contact fields: First Name and Last Name are combined into Close's single name field, then email, the phone, title, and company map directly. Apollo ships four phone columns; this template's Close schema has one phone field, so Mobile, Work Direct, Corporate, and Other are combined and the first available number wins, with Mobile taking priority. Phones are standardized and emails are lowercased before import. On Apollo's free tier the Email column shows the placeholder email_not_unlocked@domain.com for locked records. Close has a lean default contact schema, so most Apollo columns belong on the Lead record or have no native home; the Columns we don't use section covers each one.
Field-by-field mapping
This is the complete column mapping from Apollo.io to Close. The left column is the header in your CSV export. The right column is the Close field it should map to.
| Apollo.io column | Close field | |
|---|---|---|
| First Name → Last Name | Name*name Close uses a single name field on the contact record, so First Name and Last Name are combined into one with a space between them. TransformFirst Name and Last Name combined with a space | |
| Email*email On Apollo's free plan, unrevealed rows arrive as email_not_unlocked@domain.com. Filter those rows out or reveal them in Apollo before mapping. TransformLowercased and trimmed | ||
| Mobile Phone → Work Direct Phone → Corporate Phone → Other Phone | Phonephone This template's Close schema has one phone field. It takes the first available number: Mobile first, then Work Direct, then Corporate, then Other. Whichever is present wins; the rest are skipped. TransformStandardized to international format (+1, +44, etc.) | |
| Title | Titletitle | |
| Company | Companycompany |
Required by Close.
Columns we don't use
Your Apollo.io export includes 24 columns this template doesn't map. Each one below explains why, plus the workaround if you want the data in Close.
- Email Status
This template's Close schema has no email-quality field. Apollo's Verified, Unverified, Guessed, and Unavailable values are useful for filtering, Close just has no standard place for them here.
If you need it. Add a custom field on the Close contact called Apollo Email Status, then map it by hand.
- Seniority
This template's Close schema has no seniority field. The data is real and useful, Close just has no standard place for it here.
If you need it. Add a custom contact field on the Close contact for Seniority, then map it by hand.
- Departments
This template's Close schema has no department field. Apollo ships several departments per row, comma-separated.
If you need it. Add a custom contact field on the Close contact for Departments, then map it by hand.
- Corporate Phone, Other Phone, Company Phone
This template's Close schema has one phone field, which this template fills from the first available of Mobile, Work Direct, Corporate, and Other. Company Phone is the same switchboard number as Corporate Phone in most exports.
If you need it. Close supports multiple phones via its API. Add the extra numbers to the Close contact after import, or use Close's API for bulk multi-phone imports.
- Person Linkedin Url, Company Linkedin Url
This template's Close schema has no LinkedIn field.
If you need it. Add a custom URL field on the Close contact called LinkedIn, then map Person Linkedin Url to it by hand.
- Person City, Person State, Person Country
This template's Close schema has no address fields. Addresses live on the Lead, Close's company-equivalent record, not the contact.
If you need it. Update the matched Close Lead with the address after import, or add custom address fields on the Close contact.
- Website, Industry, # Employees, Annual Revenue, Company Description, Founded Year
These are company-level data points. Close stores firmographics on the Lead in its data model, not on the contact.
If you need it. Enrich the matched Close Lead after import using Apollo's company data, or add custom Lead fields and update by company name.
- Company Address, Company City, Company State, Company Country
The company address is company-level data and belongs on the Close Lead, not the contact.
If you need it. Land the company address on the matched Close Lead in a separate pass if you need it.
- Lists
Close contacts have no native field for the Apollo list a row came from. The list name is useful for segmenting prospects by campaign or saved-search source.
If you need it. Add a custom Close field called Apollo List, then open the column mapper and route Lists to it.
- Created Date
Close contacts have no native field for the date Apollo added the row to your account. The value is useful for filtering older prospects or sorting by recency.
If you need it. Add a custom Close field (date type) called Apollo Created Date, then route Created Date to it in the column mapper.
- Account Owner
Close contacts have no native field for the Apollo user assigned to a row. Account Owner is an Apollo user, not a Close user. The two are different identities and mapping them across needs a manual translation table.
If you need it. Add a custom Close field called Apollo Owner if you want to preserve the source of the record. Or use it as a filter in Apollo before exporting, so each exported file is single-owner.
Formatting and cleanup
Apollo.io exports rarely match the format Close expects. Fix these before you import.
- 1.Combines First Name and Last Name into Close's single name field
- 2.Lowercases and trims email addresses
- 3.Standardizes phone numbers to international format (+1, +44, etc.)
- 4.Fills the single phone field with the first available number, checking Mobile, then Work Direct, then Corporate, then Other
- 5.Trims whitespace and removes blank rows
Or skip the manual work
Operelio runs this cleanup and mapping for you. Upload your Apollo.io export and download a clean, import-ready file for Close.
Apollo.io to Close FAQ
Why is the Email column filled with email_not_unlocked@domain.com?
That's Apollo's placeholder for records you haven't revealed on the free plan. The email isn't included in the export until you spend a credit to reveal it or upgrade your Apollo plan. Filter those rows out of the CSV before mapping, or reveal them in Apollo first.
How do I export contacts from Apollo.io?
In Apollo, open your saved list or search, select the contacts you want, and click Export. Apollo emails you a CSV when it's ready. Upload that file to Operelio.
Why do you combine First Name and Last Name?
Close uses a single name field on the contact record, not separate first and last name fields. The template combines the two columns with a space so the contact records look right in Close.
How does the template handle Apollo's four phone columns?
This template's Close schema has one phone field. The template fills it with the first available number, checking Mobile first, then Work Direct, then Corporate, then Other. All numbers are standardized to international format before import. Close supports multiple phones via its API if you need every number kept.
Where do I import the CSV into Close?
In Close, go to Leads, click the + button at the top, then choose Import, or use Close's CSV import flow under Settings, then Import Leads. Close's import wizard handles the Lead-to-Contact link based on the Company column.
Will this create duplicate contacts?
Close groups contacts under their Lead (company) record. If a Lead with the same Company name already exists, the new contacts are added to it. Close doesn't auto-dedupe contacts by email by default, so spot-check or use Close's bulk-merge tools if you re-import the same prospects.
