160 columns come out. On average, you need 10. List Rails cuts it down to those, and quietly removes all the noise.
Upload to export in under 60 seconds. Works with the export you already pull — nothing to install, nothing to configure.
Your MLS hands you the same bloated file every week. List Rails hands it back the way you actually work it.
Your MLS decides which columns come out, and it isn't asking. You get all 160, every time, and delete the same 150 by hand before the file is any use.
An expired listing that relisted last week looks exactly like one still sitting there. Nothing in the spreadsheet tells them apart — you find out on the call, after the introduction.
Same deletions, same filters, same sort, every pull. The work you did last Monday is gone, and the file you send yourself is a snapshot nobody can rebuild.
Pull Active and Expired in the same export. List Rails matches every expired listing against every live one — the address and city, and the MLS number — and scrubs it against a relist, a sale or coming soon, keeping only the ones that genuinely never came back.
Unit 4 and Unit 6 at the same address are two different sellers. #8 and Unit 8 are the same one. Address matching handles both, along with the usual street-suffix spellings.
Pending, Under Contract, Coming Soon and Closed all mean that seller re-engaged. Each status is a chip you can move in or out of the scrub, built from the values actually in your file.
A running count at each step: filtered, cross-referenced, deduped. Nothing disappears without a number next to it, and any step can be switched off.
List Rails never assumed your file came from an MLS. It reads whatever columns it finds and builds the checkboxes from those — so the same sixty seconds work on whatever you pulled.
Save a profile per source. The columns you keep from the assessor are not the columns you keep from the MLS — so List Rails remembers each source separately, and the next pull from that source is one click.
A preset sets the columns, filters and scrub in one click — that's the sixty-second path. Or take the five steps yourself; each one shows what it's about to remove before it removes it.
Excel or CSV, straight from the MLS. Read in your browser, not uploaded anywhere.
Your standing fields arrive checked. Every box shows a real value from the data so you can decide without opening the file.
Stack conditions. Each one reports how many rows it alone would pass, so you can see which is doing the cutting.
Cross-reference the statuses against each other, then collapse duplicate properties.
Excel with a frozen header and filters on, plain CSV, or a file shaped for your CRM import.
Each preset knows which statuses to pull, what to keep, and what to scrub against. The card tells you which boxes to tick in the MLS before you export.
Expired listings whose property never came back as Active, Coming Soon, Under Contract or Closed.
The seller pulled it deliberately — and the listing agreement is often still live, so the agent keeps the client.
Both dead-listing types in one pass, scrubbed against everything that means the property is back.
Still listed, still unsold, past 90 days. Catch them before they expire, while the agent still holds the listing.
No scrub, no filters. Keeps your standing fields and drops the rest — for any pull that doesn't fit the others.
A scrubbed list is worth nothing sitting in your downloads folder. List Rails hands it off in the shape the next tool expects, so there's no re-mapping on the other end.
Frozen header row, filters already switched on, your columns in your order. Open it and start calling.
Every CRM on the market takes a CSV import. This is the one that always works, with no integration to set up and nothing to connect.
Column names mapped to what the importer expects, with your lead status and source tag already stamped — so the file drops in without a mapping screen.
Being built during beta
Creates the leads over the API, no file in between. Close and Follow Up Boss first, then any CRM through a webhook.
In buildSend the list to the skip-trace service you already pay for, on your own subscription — then merge the phones and owner names back onto your rows.
In buildGroup a scrubbed list by listing agent and rank who is sitting on the most dead inventory. No spreadsheet gives you this.
In buildBeta users decide the order these ship in — the first question we ask you is which CRM you actually use.
List Rails runs entirely inside your browser. Your file is read on your own machine, processed there, and the result is saved straight back to your downloads. It is not uploaded, not stored, and not seen by us — because there is no server for it to reach.
The file never crosses the network. You can watch it in your browser's network tab and see nothing leave.
Open the page, drop a file, get your export. Nothing to sign into before you can use it.
Once the page has loaded, it keeps working with the wi-fi off. There is nothing for it to phone home to.
You're processing an export you're already licensed to hold. No scraping, no third-party data feed, nothing leaving your control.
Every one of these is working today. None of it needs an account, an install or a connection to anything.
Priced as a utility, not a lead source. You already pay for your MLS access and your leads — this just makes what you pull usable.
Enough to see whether it saves you the time it claims.
For anyone working expired, cancelled or stale-active lists every week.
For an office running lists across a team.
Early access is free while we're in beta. Pricing above is what we plan to charge at launch; anyone who joins the beta keeps their rate for a year. No card required to start, and nothing is charged until you say so.
It's built and tested against RealTracs, whose export columns are the same for every subscriber — so it works for any RealTracs agent with no setup. It reads any Excel or CSV file with a header row, so other MLS exports will load; you may need to tick your columns the first time and save it as a profile.
No, and we couldn't if we wanted to. The tool runs entirely in your browser — there is no server that receives your file. The only thing we ever collect is the email address you give us on this page.
You're processing an export you already pulled and are licensed to hold, on your own computer. That's ordinary use of your own data. We don't scrape your MLS or hold a data feed. As always, your participation agreement is the authority — worth a read if you plan to share output outside your brokerage.
List Rails doesn't scrub against the Do Not Call registry, and you shouldn't treat its output as call-ready. If your campaign dials or texts, run the numbers through DNC scrubbing first. Email and mail don't carry the same exposure.
Both. It reads real Excel workbooks — shared strings, date formats, leading-zero ZIPs and all — as well as CSV and tab-delimited files. It'll also tell you plainly if you hand it an old .xls, which needs a re-save first.
No. It reads any CSV, Excel or tab-delimited file with a header row, and builds its column list from what's actually in your file — so tax and assessor exports, probate lists, farm lists and bought lists all load the same way. The presets are written around MLS statuses because that's the most common pull, but the columns, filters, dedupe and exports don't care where the file came from.
Any time, and your saved profiles stay in your browser either way. Since the tool never held your data, there's nothing to export or delete on the way out.
Tell us where you work and we'll send you access. Free during beta, and beta users keep their launch rate for a year.