Schema Atlas

Salesforce schema intelligence — explore, audit, and document your org's data model in seconds.

Admin / Sys Admin
Audit every field, lookup, and picklist — no more "ask the developer"
Developer
API names, types, required flags — map integrations in seconds, copy in one click
Architect
Relationship intelligence + package contribution split — architecture docs in minutes
Business Analyst
Find where revenue, contact, or case data lives — self-serve, no dev needed
InfoSec / Compliance
PII field radar across all objects — surface Email, Phone, SSN fields instantly
Implementation Partner
Cascade delete warnings + package split — catch migration risks before go-live

OAuth read-only token — direct to Salesforce by default, nothing stored server-side. (Optional relay for orgs without CORS: forwards, never stores.)

Explore and document any Salesforce org's data model

Reconstructing a data model by hand is the tax on every implementation, audit and migration. Object Manager shows one object at a time, relationships live in a field's detail page, and the artefact somebody actually asked for — a dictionary, an ERD, a field spec — has to be assembled manually from all of it.

Schema Atlas connects to an org read-only, describes its objects and fields, and turns that into the artefact shaped for whoever asked. Nothing is uploaded: the describe runs from your browser against your own instance, and the workbook is generated in memory and handed straight to your downloads folder.

What it exports

Common questions

Is my schema uploaded anywhere?

No. There is no database and nothing is stored server-side. The describe call goes directly from your browser to your own Salesforce instance and the results are processed in memory. Full detail on the trust page.

Is it read-only?

Yes. Schema Atlas only reads metadata. It never writes to your org and never touches business records.

Does it work on Vlocity and Salesforce Industries orgs?

Yes, including managed-package namespaces. Fields are split by package contribution so you can see what is standard CRM, what is Industries, what is CPQ and what is yours.

Can it document every object at once?

You can scope an export to the last rendered graph, a selected object and its neighbours, or every object described in the session. On very large orgs, select the objects you need rather than describing everything — an enterprise-wide describe is a lot of metadata for one browser tab.

Does it show formula text?

Optionally. The formula-text column is a toggle because it needs additional Tooling API calls; leave it off and no extra calls are made.

Why do I need to add a CORS entry?

Because the browser calls your org directly rather than routing through a server. See the CORS setup guide, including what to do when your org blocks the Apex shortcut.

Can I use the exports in client deliverables?

Yes. The workbooks are ordinary .xlsx files with no licence restriction on the output.

What does it cost?

Nothing. No account, no trial, no paid tier.

— objects
🧬

Select an object to open its Intelligence Dashboard

Relationships · Field DNA · Package Split · Graph
CRM standard
Industries pkg
CPQ pkg
Other managed
🔍
Tick objects in the left sidebar to load their fields, then search here

Export

Take your schema out of the browser — as a document, a diagram, or raw data.

Include
Spreadsheet
A field dictionary for documentation or review — opens in Excel or Sheets.
or flat CSV
Diagram
An entity-relationship diagram showing how your objects connect.
Lucidchart SVG
Raw data
Full metadata as JSON to feed a script or another tool.
Migration pack for data migrations
Objects in dependency load order, upsert keys, required & loadable fields, picklist values — plus blank Source / Value-mapping columns. Your migration plan, ready to fill in.
Integration contract for API / integration devs
Per field: writable & updatable flags, required-on-insert, external-ID upsert keys, type & size, valid picklist values, references. The exact field contract to build an integration.
PII & security audit
Just the sensitive fields — Email, Phone, SSN — across everything you've explored, for a compliance review.
Compliance dictionary for governance / audit
Salesforce's own Data Classification per field — compliance categorization, sensitivity level, field usage, data owner — plus a gap list: fields that look sensitive but have no classification assigned.
Fit-gap workbook for business analysts
What the org already has, laid out for a requirements workshop — per-object field inventory with blank Fit / Partial / Gap, resolution and priority columns, plus a new-requirements backlog sheet.