See Your Salesforce Org's Data Model on One Diagram

A mature Salesforce org holds hundreds of objects — Account, Contact, and Opportunity beside layers of custom and junction objects. DbSchema reads the object metadata over a Salesforce JDBC driver and renders it as an ER diagram consultants and admins can explore, query, and document.

Standard, custom, and junction objects mapped together
Lookup and master-detail relationships traced on the canvas
SOQL-compatible queries built by point and click
Field types and picklist values captured in shareable docs

available for

ISO-27001 certified

Free Community Edition No signup required 15-day Architect trial included

Free Download

DbSchema mapping a Salesforce org's objects and relationships as an ER diagram

Trusted by teams at

Hundreds of Objects, Two Kinds of Links
and No Complete Picture

Integration projects, system reviews, and client handoffs all start with the same question: how does this org's data actually fit together? Answering it from Setup screens or developer API calls, object by object, burns days of a consultant's time.

DbSchema assembles the answer once — every object and every lookup or master-detail relationship on a diagram you can hand to the next person who asks.

Diagram, Query & Document
the Org Data Model

Database-grade tooling for the platform's object layer.

Reverse engineer Salesforce object metadata into an ER diagram

Read the Org, Draw the Model

DbSchema pulls object metadata through the JDBC driver and lays out standard objects, custom objects, and their relationships on an interactive canvas.

Build SOQL-compatible queries visually in DbSchema

Query Objects Without Writing SOQL

Pick objects, choose fields, add filters — the builder writes the SQL and the driver translates it to SOQL, so admins query data on their own.

Generate documentation of a Salesforce org's data model

Handoff Docs Clients Actually Open

Export HTML documentation of object names, field types, picklist values, and relationships — the record implementation teams and change control demand.

The Org Stays in the Cloud
the Model Comes With You

Synchronize once and the object model lives in a DbSchema file of its own — reviewable on a plane, shareable with people who have no Salesforce license, and comparable across orgs.

Explore the Salesforce data model offline

Explore Offline

Open the synchronized model and study the org's structure with no connection at all.

Version the Salesforce data model in Git

Keep History in Git

The model is a file, so each metadata snapshot can be committed and diffed over time.

Read the SQL behind visually built Salesforce queries

SQL on Top, SOQL Underneath

Read the query the builder generated before the driver translates it for the org.

Compare Salesforce sandbox and production object schemas

Spot Sandbox Drift

Compare object schemas between sandbox and production and see what no longer matches.

Drivers and Authentication in Practice

Two commercial drivers work out of the box: register the CData or Simba Salesforce JDBC driver JAR under Connections > Manage Drivers. With Simba, the connection string looks like jdbc:salesforce:[email protected];Password=password;SecurityToken=token, where the token comes from "Reset My Security Token" in your Salesforce profile settings. Orgs using a Connected App authenticate with the Consumer Key and Consumer Secret OAuth parameters instead of the username/password pair.

DbSchema also ships its own open-source Salesforce JDBC driver — source on GitHub — and the Salesforce JDBC driver page walks through the setup.