Wholesalers · List import
Property list import that keeps one deal per house
A property export is a list of houses, but a CRM is built around people. We've built and tested a GoHighLevel (GHL) import that keeps both straight: the owner is one contact, and each property that owner holds is its own deal. It runs on a sample of your list first, and the rest waits until you approve what the sample shows.
The job
Bring the list in without folding houses together
The import decides what every later step is able to see.
A list pulled for wholesaling is a list of properties, each with an owner and that owner's phone numbers. Plenty of owners hold more than one property. A CRM built around the person can fold those rows into one record, and then the second house never gets its own stage, its own note or its own conversation.
One contact, one deal per property. In the import we built and tested, an owner with several houses kept a separate deal for each house. The person stays one contact, so everything said to them is in one place, while each property moves through the seller pipeline on its own.
The HighLevel setting behind it. HighLevel's help center (modified 1 September 2025) describes a setting called Allow Multiple Opportunities per Contact, under Sub-Account Settings, then Objects, then Opportunities. With it off, HighLevel restricts new duplicate opportunities for the same contact in the same pipeline. If you are building this yourself, look at that setting before the first row comes in.
The flags come in with the list. The screening that runs after the import works from the Do Not Call and litigator flags that arrive in your exported list. So those flags have to come across with each record. A flag left behind in the spreadsheet is a flag the screening never sees.
A sample before the rest. We imported a sample of the list first, then wrote the owner a report on what had happened to it. The owner approved those results, and only then was the remainder of the list cleared for import. A problem caught on a sample gets fixed on the sample; the same problem across a full list has to be fixed on every row.
Importing is not messaging. Bringing a list in gives nobody permission to contact it. Cold-lead texting sits outside this build, and the import starts no calls. At our last checkpoint the dialer was not yet connected to the account, so calling from HighLevel was still ahead.
What we set up
The parts of the list import
Planned in writing, run on a sample, then cleared for the rest once you approve.
- Each owner brought in as one contact, phone numbers on the record
- A separate deal in the seller pipeline for every property the owner holds
- The Do Not Call and litigator flags from your export carried in with each record
- A sample import before the full list
- A written report on the sample, sent to you
- Your approval before the rest of the list is cleared for import
- Screening and the AI buy-box pass waiting at the far end of the import
How a setup runs
From a spreadsheet to deals in your pipeline
A call with Rob
Thirty minutes on where your lists come from, how they are laid out, and what an owner with several properties looks like in your data.
The import rules in writing
How a row becomes a contact and a deal, and which flags come across with it, goes into the plan document. Your approval comes before any build work.
Sample import
A slice of the list goes in first. We check that every house became its own deal and that the flags arrived with their records.
Your review
You get the sample results written up. Nothing more is imported until you say the results are right.
QA report, then the rest
At handover you get a QA report with screenshots. A later change, such as a new list source, gets a verdict first, telling you whether it falls within what you approved or counts as new scope.
What you bring
What to send before the first import
A recent export
The property list exactly as your provider exports it, with owners, phone numbers and whatever flags it carries.
Your pipeline stages
The stages a seller deal moves through at your company, so each imported property lands where your team expects it.
Someone to read the sample
The person who knows your lists best. They read the sample results and approve them before the rest comes in.
Your plan for texting
Cold texting is not part of this build. If you want texts for booked appointments, the number's texting registration has to be approved first, so it is worth starting early.
Where it stops
The import brings properties in and keeps a deal for each one. It does not text cold leads, place calls or decide by itself who is safe to contact. The screening step does that from the flags in your list, and it is not a compliance guarantee.
Services used
Where the import and the pipeline get set up
CRM migration to HighLevel
Contacts moved from your old CRM or spreadsheet with every column mapped, duplicates handled and imported lists kept apart from new opt-ins.
See CRM migrationHighLevel pipeline and CRM setup
Pipelines, calendars and custom fields shaped around how you sell, with bookings and no-shows moving each deal on their own.
See Pipeline and CRM setupQuestions
What wholesalers ask about importing a list
An owner has several properties. Do they end up as one record?
Why not import the whole list at once?
Do our Do Not Call and litigator flags carry over?
Will the import start texting or calling people?
Is there a HighLevel setting we should check first?
Who you talk to
Rob Eason
Rob runs HLAI Experts and takes the 1:1 calls himself.
He is a HighLevel Certified Admin with the second-most reviews in HighLevel's Certified Admin Directory worldwide, all of them 5 out of 5.
He won HighLevel's Top New Subaccounts via AI Employee award in its 2025 Summer of AI Awards and taught HighLevel's official masterclass on its AI Employee.
Before HighLevel, he co-owned a 60-employee financial services firm and sold his share.
On the call he looks at your account, not a script.
5/5 across 83 reviews in HighLevel's Certified Admin DirectoryBring a sample of your list to Rob
In 30 minutes Rob looks at a recent export and tells you how its rows would land in HighLevel, owner by owner and house by house.