Minnesota SOS bulk data — $30/week for the full database

Minnesota’s Secretary of State publishes its business registry in bulk CSV format for $30 per week. That’s one of the cheapest data feeds in the country. But most underwriting shops and credit platforms don’t use it. Here’s why, and what you actually get.

The pitch sounds too good

Thirty dollars a week for a full extract of every active business entity, LLC, corporation, partnership, and assumed name filed in Minnesota. No per-lookup fees. No seat limits. No API throttle. The data refreshes weekly. On paper, this is the cheapest way to pull Minnesota entity records at scale.

But cheapness and usability are different things. The bulk file is a raw export. It ships as CSV with minimal structure. Field names don’t always match what’s on the SOS portal. Officer and manager lists come as a single text block, not parsed rows. If you need beneficial ownership data, it’s not in the bulk feed at all · you still have to hit the state’s lookup tool. So a vendor evaluating whether to build a bulk-feed integration has to ask: do we spend weeks parsing malformed CSV, or do we just scrape the web portal like everyone else?

Most choose the portal.

What’s actually in the file

The bulk export includes entity name, file number, entity type (corporation, LLC, LP), jurisdiction, filing date, status (active, dissolved, merged), and the registered agent name and address. That’s useful for basic entity verification. You can quickly confirm an entity exists, when it was formed, and who the statutory agent is.

But here’s the gap: it doesn’t include officer names, member names, manager names, or any detail about who actually runs the business. If you’re underwriting a $50,000 equipment loan and you need to know who signs the guarantee, you have to go back to Minnesota’s portal and pull the detailed record. The bulk file is a fast screen-out tool, not a complete dossier.

There’s also no UCC search in the bulk feed · Minnesota’s UCC filings live in a separate system. And no USDOT/FMCSA data, which you need if you’re underwriting a fleet or a carrier. So the $30-per-week file answers “does this LLC exist and is it current?” but not “who owns it, who owes money against it, and does it have open safety violations?”

When bulk data makes sense

If you’re running daily compliance checks across a book of existing clients, bulk data is smart. Download once a week, compare every entity you have on file to the latest state snapshot, flag any that have dissolved or changed status. That’s a quick refresh. Cost per check drops to pennies.

If you’re processing a handful of new applications per day, bulk data is overkill. You’ll pay $30 per week and use a fraction of it. You’re better off pulling individual records on demand.

The real win is if you’re building an internal dashboard or doing batch vetting of hundreds of entities at once. A single $30 download, parsed and loaded into your system, beats 500 individual portal lookups across your team.

The parsing problem

Anyone who’s tried to normalize Secretary of State CSV exports knows the issue: state feeds are inconsistent, especially in how they handle arrays of data. Minnesota’s bulk file lists registered agents cleanly. But if an entity has five officers, are they in the same row separated by pipes, or five separate rows with the same entity ID? (The answer varies, and it’s never obvious from the documentation.) A vendor building a production system has to code defensively, handle edge cases, and maintain the parser as the state changes its export format without warning.

That engineering cost · plus the cost of still having to hit the portal for officer details · adds up to more than just scraping the web interface directly. For a small vendor or a bank doing this in-house, it’s easier to just pull the records you need, when you need them.

Cost vs. labor

If you have someone with an hour per week to download, parse, and load Minnesota bulk data into a spreadsheet or database, $30 per week is unbeatable. If you need the data parsed, deduplicated, cross-referenced against UCC and USDOT, and delivered in a single report, the labor cost to DIY it is much higher than the data cost.

That’s the real math most underwriters face. The bulk file is cheap. Turning it into intelligence is not.

Bottom line

Minnesota’s bulk SOS data is legitimately useful if you have a high volume of Minnesota entities to check and you can absorb a parsing step. For a single underwriter pulling a few records a month, it’s not worth the setup. And regardless of price, you’re still missing officer names, UCC liens, and USDOT history · fields that often matter more than the entity status itself. Bulk data is a piece of the puzzle, not the whole picture.