Bulk-import leads from Excel

Bring in many leads at once from a spreadsheet or another CRM, instead of keying each one in by hand.

When you have more than a handful of leads to add (migrating off a previous tool, or dropping in a list exported from a spreadsheet or another CRM), the Import leads button opens a file-upload flow that creates the leads in bulk. Each imported lead lands in your Kanban as a residential Request with its contact and address, the same way a hand-keyed lead does, and any connected CRM syncs out automatically.

Residential only. Import leads creates residential Requests, and lives in the residential Requests section of the Portal.

Before you start

You need Editor role or higher in the residential area. Viewers see Import leads disabled, the same as New request.
Your workspace needs the residential Requests area enabled. If you don't see Requests in the nav, ask your admin.
Have your file ready as a spreadsheet, CSV, or other supported upload, with one lead per row.
Each lead needs at least first name, last name, email, and a full address (street, number, postcode, city), the same fields the manual create form requires. Phone is optional.
Addresses are geocoded to a map pin during import. Use clean addresses where you can, and fix any pin per Request afterward.

Import a lead list

Open Requests in the residential section of the Portal nav.
Click Import leads in the top-right, next to New request.
Drop your spreadsheet or file into the upload window, or click to browse.
Reonic reads the file, creates one Request per row, attaches each contact, and geocodes each address.
Find the imported leads in your Requests Kanban or list. Open any Request to fill in the optional project detail fields that aren't part of the import.

Note

Import leads is a separate path from the create form. Use New request for one walk-in or referral at a time, and Import leads when you're bringing in a whole spreadsheet.

What carries over

The import creates Requests with their contact and address, the same shape a manually-created lead has on the create form. Imported leads also carry the lead-source detail from the source file or broker, so they can arrive already attributed. Your list and Kanban views filter by lead source either way.

You add the project details afterward, on the Request's Basics tab:

Project package (solar, battery, wallbox, or heat-pump sizing). Pre-select packages later, either when you build the offer or by editing the Request's Basics tab.
Detail fields like requested solar size (kWp), requested storage size (kWh), and the customer message.

Duplicate contacts

Reonic matches an imported lead to an existing contact using the broker ID carried in the import payload (from CRMs like HubSpot, Pipedrive, Weclapp, Bitrix, or Photovate). When a row carries a matching broker ID, it attaches to that existing contact. When no broker ID is present, a fresh contact is created. The same contact can legitimately hold more than one Request (a revisit, a second property), so duplicate-looking rows aren't always wrong.

If you spot a genuine duplicate contact after an import, reconcile the two contacts. See Manage contacts in the CRM.

Pro tip

If your source file overlaps with contacts you already have and there's no broker ID, clean the file before import or reconcile the duplicates afterward.

Things to know

Follow up with imported leads yourself. The customer-welcome email and internal team notification are workspace-level settings, and they fire from your public contact form, not from every intake path. Send outreach yourself, or review your workspace's notification settings with your Reonic account manager.
Imported and manually-created leads both sync to your CRM. When your workspace has a CRM integration configured, a request syncs out to your connected CRMs (HubSpot, Pipedrive, Salesforce, Weclapp, Bitrix) as soon as it's created, whether you imported it or entered it yourself on the Portal.
The map pin is what carries through. Address fields are required, and the location is geocoded automatically. If a geocode lands wrong on an imported row, open that Request and adjust the pin on the map.
Editing an imported contact prompts a confirmation. If a contact came from an integration (HubSpot, Pipedrive, Weclapp, and so on) and you change any of its fields, a banner asks "Are you sure you want to update the contact details?" before saving.

Last updated on September 30, 2026