# How to understand a Salesforce org you inherited. > Understanding an inherited Salesforce org with SyncOnAI 360 means syncing its metadata and source, asking it questions in plain English, opening any component to see what uses it, and reading its health and audit to find the risks. Every answer comes from the org itself and states how much of the org it covered. Source: https://synconai360.com/use-cases/inherited-salesforce-org ## Key facts - **20+**: Metadata types synced, with full source - **1**: Search across the whole org - **Every**: Answer states its coverage - **0**: Changes made by exploring ## Why inherited Salesforce orgs are so hard to learn The person who built it has gone. What is left is hundreds of fields, Flows, triggers and permission sets, with names that made sense to someone once. - **No documentation.** Or documentation that describes an org from three years ago. - **Hidden automation.** Saving one record fires Flows, triggers and rules nobody can list. - **Fear of touching anything.** Every change might break something nobody knew existed. - **Setup one screen at a time.** There is no way to see the org as a whole. ## How do you ask a Salesforce org what it does? Ask in plain English: what runs when a Case is created, which classes reference Opportunity, what writes to the Status field. The chat reads the synced metadata and source, shows the tools it used, and answers from your org rather than from general Salesforce knowledge. Save any useful answer as a page, so the understanding you build becomes the documentation the org never had. - Plain-English questions - Answers from your org - Save answers as documentation ## How do you see what depends on what? Open any component in Lineage to see what uses it, what it uses and what to watch, in plain language first with the technical map behind it. Relationships are parsed from source and Salesforce's dependency data, and where source could not be read, that is said rather than hidden. Search any component by name in the Knowledge Hub and open it straight into its lineage. - What uses it and what it uses - Evidence behind every link - Search into lineage ## How do you find the risks first? The health score and audit tell you where the org is weakest: security exposure, overlapping automation, legacy Workflow and Process Builder, missing tests, sprawling fields. Each finding has its evidence, severity and cost to fix. The Architecture lens profiles how the org is built, its automation mix, naming, sharing posture and packaging, so you can work with its conventions instead of against them. - Health and audit - Evidence and cost per finding - How the org is really built ## How do you make your first change safely? Every change is a proposal with named checks, including the components that reference what you are changing, and a validation against the org before anything is saved. Deploy to a sandbox first, then production, and keep the receipt with rollback to the recorded previous version. Exploring never changes the org; only an approved proposal does. - Blast radius before you change - Validation first - Rollback from the receipt ## How do you see what changed in the org recently? The Changes lens shows what changed and when, and whether it came through SyncOnAI 360 or from somewhere else. The audit reads the last thirty days of the Setup Audit Trail and flags changes made outside a release process. Knowing what moved recently tells you where the previous team was working and where problems are most likely. - What changed and when - Setup Audit Trail checks - Where to look first ## Your first two weeks with an inherited org 1. **Connect.** Start with a sandbox if you prefer. 2. **Read the health.** See the score and the weakest sections. 3. **Ask.** Question the org about its key processes. 4. **Map.** Open the components you will touch first in Lineage. 5. **Change safely.** Ship your first fix as a checked proposal. ## An inherited org, guessed versus understood | Without | With SyncOnAI 360 | |---|---| | Clicking through Setup for weeks | Plain-English questions answered from the org | | Automation discovered by accident | What runs on each object, listed | | Afraid to change anything | Blast radius shown before every change | | Knowledge that leaves with you | Answers saved as pages | ## Your first-week checklist for an inherited org - [ ] Connect a sandbox first if production access is sensitive. - [ ] Read the health score, its confidence and its coverage before anything else. - [ ] List the five objects the business depends on most and ask what runs on each. - [ ] Open the components you will touch first in Lineage. - [ ] Check the Changes lens for what moved recently and who moved it. - [ ] Save every useful answer as a page so the next person starts ahead. - [ ] Ship your first change to a sandbox, then production, through a proposal. ## Who inherits orgs - **New admins.** Get your bearings in the first week instead of the first quarter. - **Consultancies taking over.** Pick up an org from another partner with evidence of its state. - **Developers.** Learn the code and what it touches before changing it. - **Architects.** See the design as built, not as remembered. ## Frequently asked questions ### Can it explain what a Flow does? Yes. The Flow builder explains a Flow in plain sentences, and the chat can describe what runs on an object. ### Will exploring change anything? No. Only approved proposals change an org. ### Can I start on a sandbox? Yes. Connect a sandbox and explore before connecting production. ### What about managed packages? Package components are listed; where the publisher hides source, it is shown as hidden rather than missing. ### How complete are the answers? Every answer states how much of the org it was based on. ### Can I document what I learn? Yes. Save any chat answer as a page, searchable later by you and the AI. ### Does it read our records? No. It reads metadata; record queries run live only when you ask for data. ### Is this on the free plan? Yes. Every plan includes every feature. ### How long until I can start asking questions? As soon as the first sync finishes, which takes several minutes for a large org and runs in the background with progress shown. ### Can a colleague see what I learned? Yes. Pages and saved answers are shared across the workspace and searchable from the Knowledge Hub.