Import Leads Into Close CRM: The Local Lead Gen Guide (2026)

Close is built for calling and closing — but its best features, the Power Dialer, Smart Views, and Workflows, all assume a pipeline already full of leads worth working. This guide shows you how to import leads into Close CRM without wrecking the database: every route in, when the built-in CSV importer is genuinely the right call, when a native integration beats it, and — the part most import guides skip entirely — how to put Close's outbound features to work on the leads once they land. The examples focus on local-business outbound, where lists are big, messy, and refreshed often, which makes every import decision matter more.

How to add leads to Close CRM: the four options

Close's help center documents four routes: manual entry (the + button next to Leads), file upload through the Lead Importer, automated migration from another CRM, and the API — which is what native integrations write through. Manual entry is fine for the occasional referral. CRM migration is a one-time event for teams switching platforms. For ongoing lead generation, the real decision is between the Lead Importer and an API-based integration, and the right answer depends on whether importing is something you do once or something you do every week.

Close's CSV import: what the Lead Importer does well

The Lead Importer (click your name in the upper right, then Import Leads & Data) is built in, free on every plan, and handles CSV or Excel by drag-and-drop. It's genuinely good at one-time jobs — but it has formatting rules, all from Close's published import requirements, that trip people up:

• The first row must be a header row containing column names.
• Dates must use yyyy-mm-dd format — 2026-02-05, not 02/05/2026.
• Phone numbers need the + country-code prefix: +15125550137, not (512) 555-0137.
• Custom field columns need a custom. prefix in the header to auto-match, and choice-type custom fields (plus any Lead Status values) must already exist in Close before you import.
• Multiple values in one cell — say, two email addresses — are separated with a semicolon.
• The importer cannot bring in notes, calls, emails, or SMS history.

When the import finishes, a summary page reports how many leads were created, skipped, or failed validation, with downloadable CSVs of the problem rows. For a clean one-time migration, that's a perfectly serviceable workflow.

Where the importer strains: recurring imports

The cracks show when importing becomes a weekly ritual rather than a one-time event:

• Duplicates are your problem. The importer's Group Related Rows option dedupes on a column you pick — but for local businesses there's no reliable column. Names vary ("Joe's Plumbing" vs. "Joes Plumbing LLC"), phone numbers and URLs change. And per Close's own documentation, Close runs no automatic background duplicate detection afterward, so near-duplicates from successive CSVs quietly accumulate.
• No update-in-place. Re-importing a lead that already exists either skips it or duplicates it. The importer won't refresh a stale rating or replace a disconnected phone number on an existing lead.
• Custom field setup is on you. Every choice-type field must be created by hand in Close before the CSV that references it will import cleanly.
• Formatting toil repeats every time. Date formats, phone prefixes, header prefixes — an hour of spreadsheet cleanup per import, forever.
• It never runs itself. Someone has to export, clean, upload, and review the summary — every single week.

CSV importer vs. native integration: an honest comparison

Full disclosure before the comparison: LeadMarina builds one of the integrations described below, so we have a horse in this race. Here's the fair version anyway, because the importer genuinely wins some scenarios.

• Use the CSV importer when: you're migrating once, your data is already clean and deduplicated, you want row-level control over exactly what enters Close, or you don't want another tool in the stack. It's free, built in, and well documented.
• Use an integration when: importing recurs, you need duplicates prevented by a stable identifier rather than a guessed column, you want existing leads refreshed in place instead of skipped, you want custom fields created automatically instead of by hand, or you want the whole thing running on a schedule with nobody touching a spreadsheet.

The short version: if you import once a quarter, use the importer and skip to the Smart Views section. If filling Close is a standing job — which it is for almost every local outbound team — the rest of this guide is for you.

Step 0: start with verified local business leads, not a scraped list

How you import matters less than what you import. Close's outreach features amplify data quality in both directions: a Power Dialer session over disconnected numbers burns rep hours at machine speed, and a Workflow emailing dead addresses generates bounces that damage your domain's sending reputation. A scraped list makes both problems worse the more efficiently you work it.

That's why LeadMarina verifies everything before it can reach Close. Every lead is a full local-business profile: up to three email addresses, each SMTP-checked and labeled safe, risky, or invalid; up to three phone numbers, each with its line type (mobile, landline, VoIP, or toll-free) and carrier; the owner's name where it's identifiable (an honest caveat: ownership isn't discoverable for every business, so this field won't always be filled); plus social profiles, Google ratings, and review counts. Crucially, those verification labels arrive in Close as fields — which is exactly what makes the Smart View recipes later in this guide possible.

How to import leads into Close with LeadMarina, step by step

Step 1: Connect Close with one OAuth click

In LeadMarina, open Integrations and hit Connect on the Close card. It's OAuth — you approve on a Close screen and you're connected. No API key to dig out of settings, no Zapier in the middle. The Close integration page has the overview, and the Close docs cover every detail of what gets written where.

Step 2: Run a search worth exporting

Search a niche plus a city — "electricians in Austin, TX", "roofers in Tampa, FL". LeadMarina pulls the local businesses from Google's listings data and verifies every contact as results come in. Covering a whole territory? Bulk search handles up to 250 cities in one run. Either way, keep segments tight: one niche-city segment means one relevant message in Close later, and relevance is what gets replies. The free plan includes 100 fully verified leads, so you can run a real search against your own market before deciding anything.

Step 3: Map fields once — Close custom fields create themselves

The first time you hit Export → Close, a mapping dialog opens. Native data maps to Close's built-in fields (company name, URL, contact name, phone). Everything else — email verification status, phone line types, carriers, ratings, review counts — maps to custom fields that LeadMarina auto-creates in Close with matching names. No pre-creating fields by hand, which is the setup chore the CSV route makes you do yourself. The mapping is saved and tracked by Close's internal field IDs, so if someone renames a field in Close next month, nothing breaks. Contact-level data — phones and emails — is carried by a Contact that LeadMarina creates but never updates afterward, so any edits your reps make to contacts are never overwritten.

Step 4: Export — and re-export without fear

Every business LeadMarina finds carries a stable Google business identifier, and LeadMarina remembers which Close lead it created for each one. Re-export the same search next month — or a broader search that overlaps it — and existing leads are updated in place: fresh ratings, current phone numbers, new review counts. Never a duplicate. And exports only ever write the fields LeadMarina manages: your notes, activities, opportunities, statuses, and hand-edits are never touched. This is the property no CSV workflow can give you, because a spreadsheet has no memory of what it created last time.

Close Smart Views, Power Dialer, and Workflows on verified leads

Getting leads into Close is half the job. The other half is why you chose Close in the first place — and each of its three core outbound features gets meaningfully sharper when verification data comes along for the ride.

Smart View recipes built on verification fields

Smart Views are Close's saved, shareable, dynamically filtered lead lists — the backbone of rep prioritization. Because line type, email status, and ratings arrive as fields, you can build views that a raw import could never support:

• Call-first list: phone line type is mobile AND email status is safe. Highest-value leads — reachable two ways, likely the owner's own phone.
• Email-first list: email status is safe AND no mobile number. These go to Workflows instead of the dial queue.
• Business-hours list: line type is landline or toll-free. Front desks answer 9-to-5; queue them accordingly.
• Personalization list: owner name is present. "Hi Maria" outperforms "Hi there" — route these to your best openers.
• Reputation angle: Google rating below 4.0. A concrete, non-generic reason for the first call if you sell marketing, reviews, or customer-experience services.

Power Dialer sessions on verified mobiles

Close's Power Dialer — available on its Growth plan and up, per Close's published plan lineup at this writing — runs off a Smart View and auto-advances the moment a call ends or a number comes back disconnected or busy. It's a rep-hours multiplier, which means it multiplies whatever data you feed it. Feed it the mobile-only Smart View above: VoIP front-line numbers and landlines that ring to voicemail after 5 p.m. waste queue slots that verified mobiles convert. One honest limit: line type tells you what kind of number it is, not whether the owner picks up — but cutting the obviously dead and obviously wrong dials from the queue is exactly the kind of edge that compounds over a thousand-call week.

Workflows on safe emails only

Close Workflows automate multi-step sequences — email, SMS, tasks — and can auto-enroll any lead that matches a Smart View's filters. The rule that protects your domain: automated sequences enroll only leads whose email status is safe. Risky addresses are a judgment call — low-volume, manual, one-at-a-time sends if the lead looks valuable — and invalid addresses should never be emailed at all. Because the verification label is a field, this isn't a policy you have to remember; it's a filter condition the automation enforces for you.

Automate the refill: scheduled searches, API, and MCP

Once the mapping exists, remove yourself from the loop entirely. Schedule any LeadMarina search — once, daily, weekly, monthly, or yearly — with Close as the destination. New businesses in the territory appear as new leads; known businesses get their fields refreshed in place. Your reps open Close on Monday to a pipeline that filled and updated itself over the weekend, and your auto-enrolling Workflows pick up the new arrivals without anyone clicking anything.

Prefer to orchestrate it yourself? The REST API is available on every plan, including free — see the quick-start docs. There's also an MCP server with thirteen tools, so you can run searches and exports conversationally from Claude, ChatGPT in developer mode, Cursor, or any MCP client. Same verified leads, same Close mapping, different steering wheel.

Close CRM lead generation checklist

• Match the method to the job: CSV importer for one-time migrations, an integration for recurring lead flow.
• If you do use the importer, mind Close's format rules: header row, yyyy-mm-dd dates, + country-code phones, custom. prefixes, pre-created choice fields.
• Verify before you import — every bad row costs dials, bounces, or rep trust once Close's automation touches it.
• Connect the Close integration — one OAuth approval, no middleware.
• Map fields once and let the custom fields auto-create; the mapping survives renames.
• Build Smart Views on the verification fields: mobile call lists, safe-email Workflow lists, business-hours landline queues.
• Point the Power Dialer at verified mobiles and enroll only safe emails in Workflows.
• Schedule the searches that matter, then check the pricing page to size the lead volume to your territory.

The pattern is simple even if the details aren't: verify before you import, map once, re-export freely, and let Smart Views route each lead to the channel its data supports. Close does the closing. The pipeline fills itself.