The Object Says 'Application.' Your SOQL Says 'Lead.'

A team tells you, plainly, “we don’t track Leads.” You open Object Manager to confirm — and there’s no Leads object in the list. Then a report type references Lead, a SOQL query returns three thousand of them, and the key prefix on the records is 00Q. Both things are true at once. Nobody is lying and nothing is broken.

You’ve met a relabeled standard object — and until you know the rule, it will send you hunting for an object that’s been hiding in plain sight under a different name.

The label moves; the API name never does

Salesforce lets you rename standard objects and their tabs through Setup → Rename Tabs and Labels. The change is cosmetic but total: the App Launcher, tabs, Object Manager, list views, and report-type pickers all start showing the new word. What does not change — ever — is the API name. SOQL, report-type definitions, formula fields, validation rules, Apex, and every line of metadata still say Lead.

So an org repurposes the Lead object as an intake queue and relabels it “Application.” Staff now see “Applications” everywhere they click. Meanwhile every query, automation, and integration still references Lead, because at the API level that’s all it has ever been. Search Object Manager for “Lead” and you get nothing — the object is alphabetized under A now.

Where it trips people

• You can’t find “Leads” in a dropdown — it’s listed as “Applications.”
• Documentation and SOQL disagree with what the user sees on screen, so a hand-off doc reads as wrong even when it’s right.
• A consultant and a staff member describe the same object with different nouns and spend ten minutes convinced they’re discussing different things.

It isn’t only Lead. Opportunity relabeled to “Donation” or “Deal,” Account to “Organization” or “Household,” Case to “Ticket” or “Request” — all common, especially in nonprofit orgs that bent the standard model to fit their own language.

How to see through it in thirty seconds

The API name is the ground truth; ask for it directly:

sf sobject describe --sobject Lead --json | jq '.result | {label, name, keyPrefix}'

That prints the friendly label next to the immutable name, so you map “Application” → Lead once and stop second-guessing. The key prefix is the other tell — the first three characters of any record Id never lie:

• 00Q = Lead
• 006 = Opportunity
• 001 = Account
• 500 = Case

And Setup → Rename Tabs and Labels lists every relabel the org has made, in one place.

This is one instance of a wider habit: the interface is a label on top of the system, not the system itself — the same reflex that catches a form quietly dropping the data it claims to save.

The working rule, once you know to look: talk to people in their labels, write code in the API names, and never trust a dropdown to tell you what an object really is. When “we don’t have any X” collides with “there are three thousand X,” you’re not confused — you’ve found a rename.