An import-exclusion rule for agency records
Jun 1, 2026
9 min read
The easiest mistake in a software move is importing everything because deletion feels risky.
Every old contact, every half-written note, every duplicate landlord, every closed transaction, every test record from 2019. It all comes across. The new system looks full on day 1, then agents start asking the same awkward questions they asked in the old one.
Which James is the buyer? Why is this vendor still active? Who owns this landlord? Is this note current, or just old noise? Can we contact this person, or did they unsubscribe years ago?
If your agency is choosing the best database for real estate agents, the import decision matters as much as the product decision. A clean new database starts with deciding which records are trustworthy enough to move now, which need quarantine, and which should stay archived.
That is the job of an import-exclusion gate.
Start with trust, not volume
Most old real estate databases contain useful history and clutter in the same export. The import tool treats both as data.
An old applicant with a clear budget, search area, last contact date, source, owner, and permission to contact is useful. A record called “Tom buyer maybe” with no phone number, no requirements, and a note saying “call later” is not useful just because it has a row in the spreadsheet.
NAR’s CRM cleanup guidance rightly focuses on duplicates, contact detail, inactive tags, and ongoing maintenance. Before a migration, ask a sharper question: would this record make the new system more trusted or less trusted?
If agents open the new database and find dead records, duplicated clients, and vague notes, they will quietly rebuild their own lists.
For a newer agent, the database is the agency’s shared memory. It should help someone answer, “What needs doing next, and why?” If a record can’t answer that after a quick check, don’t treat it as clean.
Use a move, quarantine, archive gate
Don’t review every field on every record. That burns time and creates false precision. Use 3 lanes.
| Lane | What it means | What happens next |
|---|---|---|
| Move | The record is trusted enough to enter the new system as working data | Import it with owner, status, source, and next action where relevant |
| Quarantine | The record may be useful, but one missing piece could mislead the team | Hold it in a separate import batch until someone fixes or summarises it |
| Archive | The record has no current operational value, no clear permission, or no business reason to appear in daily work | Store it outside active lists according to your retention rules |
Quarantine is the lane agencies skip. They either import messy records because they might matter, or delete them because they look weak. Both are too blunt.
A quarantined record is a pause, not a verdict. It says: “This could be useful, but not yet.”
That protects the new real estate database without forcing agents to settle every edge case before launch.
The records that should not move yet
Use this table before importing old contacts, applicants, vendors, landlords, companies, deals, and notes.
| Record type | Move when… | Quarantine when… | Archive when… |
|---|---|---|---|
| Active buyer or tenant | Requirements, timing, owner, source, and next action are clear | Budget, area, or last conversation is too vague to act on | There is no current relationship or permission to contact |
| Vendor or landlord | Property, instruction state, owner, and communication preference are clear | The contact exists but the property or decision state is missing | The relationship is historic and no longer useful for active work |
| Company or household | Linked people and relationship roles are clear | Duplicate companies, spouses, partners, or landlord entities may split the story | It is a test, supplier, or one-off record with no active or historic value |
| Closed transaction | File reference, parties, completion state, and document location are clear | The transaction exists but file references are missing | It is a duplicate shell with no distinct record value |
| Free-text note | It explains a current decision or useful history | It contains mixed facts that need summarising before import | It says nothing more than “called”, “left message”, or “follow up” |
| Task or reminder | It has an owner, date, related person or property, and reason | The action is real but detached from the record it affects | It is overdue history with no current action |
| Imported list or portal lead | Source, consent or relationship context, and first response state are visible | Source is unclear or permission needs checking | It is unqualified, duplicated, or outside your contact rules |
Legal advice sits outside this article. Retention, consent, and complaint-handling requirements vary by location and agency policy. The operating rule is simpler: don’t let uncertain records sit in the same lane as trusted live work.
If in doubt, quarantine and review.
Duplicates are not just duplicate names
Duplicate cleanup goes beyond “same email, same phone.”
A couple may appear as 2 separate buyers, then later as joint vendors. A landlord may use a personal email for one flat and a company email for another. A commercial contact may appear under a company, a trading name, and a personal mobile. One negotiator may save “James + Priya”, while another saves only Priya after a viewing.
The RealNex duplicate-record guidance gives a useful commercial real estate reminder: contacts, companies, and properties can all carry duplicates, and imports or multi-user entry often create them.
Before import, separate low-risk duplicates from high-risk duplicates.
Low-risk duplicates have the same name, email, phone, role, and recent history. They can often be merged after a quick check.
High-risk duplicates have conflicting notes, different properties, different owners, or different relationship roles. Quarantine them. Don’t let an import merge away the note that explains why the landlord uses a separate company record, or why 2 buyers with the same surname aren’t the same household.
A good database for real estate agents should help you find these risk groups before they turn into daily confusion: duplicate names, missing owners, no next action, stale active status, missing source, missing consent context, and closed files with no document reference.
AvaroAI’s search and filtering are built around connected work, so a manager can look across contacts, listings, viewings, offers, tasks, and documents instead of exporting another spreadsheet to work out what is safe to import. The design choice matters here: migration review is faster when “bad record” means “record missing the context needed to act”, not just “field blank.”
Summarise bad notes before they become permanent
Old notes are where migrations get untidy.
Agents write notes for themselves in the moment. “Wants garden, partner unsure, call after valuation” may have made sense on the day. Six months later, inside a new system, it needs structure.
Before moving notes, ask whether the note contains:
- A current requirement
- A decision or objection
- A promised follow-up
- A communication preference
- A file or document reference
- A sensitive context that should not be widely visible
If yes, summarise the useful part before import or quarantine the record. Don’t dump 40 old notes into a new timeline and call that history.
AvaroAI is deliberate about this. Contact records can carry interest level, price range, requirements, notes, tasks, reminders, and related listings because not every detail belongs in one long note. Repeatable facts should become fields or linked records. Judgement and nuance can stay as notes.
That separation stops old noise from hardening into operating truth.
Run a 45-minute exclusion review
You can do this tomorrow with one export and a small review group: one owner or manager, one agent who knows the live clients, and one person who understands files.
Use this 45-minute pass before any full import:
- Filter for records marked active but with no owner or no next action.
- Filter for duplicate names, phones, emails, companies, households, and properties.
- Pull closed transactions with missing file or document references.
- Pull contacts with no source, no recent touch, or unclear permission to contact.
- Pull free-text notes over a sensible length and mark the ones that need summary.
- Put each group into move, quarantine, or archive.
Don’t try to fix everything in the meeting. The goal is to stop weak records entering the new system as if they’re clean.
The NAR guide to choosing a CRM makes a practical point for anyone comparing systems: know what you want from the tool before choosing it. For import readiness, the same principle applies. Know what a trusted record looks like before you move thousands of them.
The best database is the one agents trust after import
The best real estate database imports the history agents trust enough to use on a busy day.
That trust comes from visible signs. Active records have owners. Live applicants have requirements. Vendor and landlord records connect to property context. Closed files point to the right documents. Notes explain decisions instead of burying them. Duplicates don’t split the same relationship across 3 places.
When those basics are missing, agents compensate. They keep private lists, old exports, inbox searches, and memory-based shortcuts. Once that starts, the new database becomes another place to check instead of the place work happens.
So before the next import, be selective. Move records that can support action. Quarantine records that need one decision. Archive records that would only pollute daily work.
That selectivity stops the old database from following your agency into the new one.
Related reading
Disclaimer: This page may contain AI-assisted content. The information is provided solely as a general guide and may not be correct, complete, or current, including, but not limited to, our full or applicable service offerings. While we strive for accuracy, no guarantee is made regarding correctness or completeness, and no expectation should be made as such. Please contact us directly to confirm any details before utilizing our service.
