Salesforce won't show more than 2,000 rows: how to export your full list view anyway

The wall every Salesforce user hits

Search "salesforce list view limit" and you will find ten years of forum threads asking the same thing: why does my list view stop at 2,000 rows, and how do I get the rest? The limit is real and documented. A list view shows at most 2,000 records in the browser, no matter how many actually match your filters. The count at the top might say 50,000. You still only see 2,000.

The annoying part is that you never notice the wall until you need it gone. For daily work, 2,000 rows is plenty. But the day you need the whole list, for a mail merge, a handover, an audit, or a cleanup, a 30-second job turns into an afternoon.

Why the limit exists

To be fair to Salesforce, the cap is about performance, not laziness. A list view is a live query. Loading 50,000 rows into a browser tab would be slow for you and costly for them. So the screen stops at 2,000, and Salesforce assumes anyone who needs more will use Reports or the API.

That assumption is where things break. "Just use a report" sounds easy until you try it. The filters do not copy over one to one. You rebuild the columns by hand. And in many companies, the Export Reports permission is turned off anyway, so even a perfect report ends at a greyed-out button. Your list view was already exactly right. You should not have to rebuild it somewhere else just to get a CSV.

The workarounds people try

Here is the honest list of what people do, and where each one hurts:

• Rebuild the view as a report. Works if your filters are simple and you have export permission. Costs 15 to 45 minutes per view. And the report goes stale the next time someone edits the list view.
• Data Loader. Salesforce's official bulk tool. Free and powerful, but complete overkill. You install a desktop app, log it in, and write a SOQL query by hand to copy your view's filters. Most people do this once and never again.
• Copy-paste, page by page. Yes, people really select 200 rows at a time and paste into Excel. For 8,000 rows, that is 40 rounds of select, copy, switch, paste. It also breaks dates and drops leading zeros without telling you.
• Browser extensions. Some just scrape the page, so they hit the same 2,000-row cap. The ones that use the API often ask for broad access to every Salesforce page you open.

The full list is already available, just not on screen

Here is what the UI does not tell you. The complete list is available through Salesforce's own REST API. Every list view has an API address. Results come back in pages, and each page points to the next one. Follow the pages to the end and you have the whole list. Same columns, same filters, no 2,000-row cap.

That is exactly what our Salesforce list view exporter does. You connect with the Salesforce login you already have (one-click OAuth, or a session token if your admin blocks connected apps). You pick any list view on Contacts, Leads, Accounts or Opportunities. The tool walks through all the pages and saves the result as a CSV. An 8,000-row list takes about a minute. A 100,000-row list works too, because the file streams to your disk instead of piling up in browser memory.

The list you built in Salesforce is already the export plan. A tool's only job is to follow it past row 2,000.

What about permissions and safety?

Fair question, and the answer matters. The exporter reads data using your own login. So it can only export records you can already see in Salesforce. Sharing rules, field security and role hierarchy all still apply, because the API enforces them the same way the screen does. The tool is read-only. It cannot edit, delete or create anything. And your login is used in memory for the run only. We never store it.

The two-minute version

If you just want the steps: open the list view exporter, click Connect with Salesforce, approve the prompt, pick your object and list view, and click Export. The free preview shows the first rows so you can check the columns before you commit. That is the whole process, whether the list has 2,001 rows or 200,000.

Making the CSV behave in Excel

Two small habits keep the file clean. Open it through Excel's Data import instead of double-clicking it. And set ID and phone columns to text. Excel loves to turn Salesforce IDs into scientific notation and cut leading zeros off phone numbers, and it does this silently. Also, name the file with the view and the date, like Open-Opps-APAC-2026-07-02.csv. The third time someone asks "which export is this," you will be glad you did.

When you should NOT export

Worth saying clearly: if what you really want is a live dashboard, a recurring feed, or a connection to another system, a one-off CSV is the wrong shape. Use a proper integration or Salesforce's scheduled reports for that. The export shines for the one-time jobs: the handover, the audit, the mail merge, the cleanup, the question someone needs answered today.

About the "just use a report" advice

You will see this in every forum thread, so here is the fair comparison. Cloning your view as a report works when three things line up: your filters translate cleanly (list view filters and report filters differ in annoying corners, especially dates), your profile has Export Reports turned on, and nobody edits the original view later. When all three hold, a report is fine. But each one fails often enough that exporting the view itself is the path that works every time. That is why this tool exists.

Frequently asked questions