Guide

You inherited a Salesforce org. Here's the first 30 days.

Spend the first week changing nothing: secure access and find anything with a deadline. Spend the second mapping how the org is built, the third finding out what the business actually relies on, and the fourth turning it into a ranked, priced plan. After 80+ enterprise org audits, the orgs that go wrong are the ones where someone started deleting in week one.

By VanguardOps, written by a Salesforce architect with 13+ years in enterprise orgs. Updated November 17, 2026.

Week 1: secure it and find the deadlines

  • Access. Confirm you have the admin access you need, and list everyone else with System Administrator or Modify All Data.
  • Integrations. List connected apps and named credentials, and find an owner for each. What to look for
  • Anything with a date. Certificates near expiry, storage and API limits near full, and the license renewal date. Certificates
  • A way back. Make sure there is a recent backup or export, and a sandbox you can test in.

Week 2: map how it’s built

  • Count objects, custom fields, flows, Apex classes and triggers.
  • For your busiest objects, list everything that fires on create and update. Stacked automation
  • Count active Process Builder processes and workflow rules. Why they matter now
  • Run all Apex tests and note coverage and failures. Test coverage
  • Compare licenses owned with licenses used. Unused licenses

A metadata scan does most of this week in minutes and changes nothing in the org.

Week 3: find out what the business relies on

  1. Sit with each team that uses Salesforce for an hour and watch them work.
  2. Ask which reports and dashboards leadership actually reads.
  3. Ask what breaks most often and what people work around.
  4. Match what you hear to what you mapped. Automation nobody can explain and fields nobody uses become clean-up candidates; the rest is now documented.

Week 4: price it and plan

Put a cost on each problem: the hours to fix it, and what it costs each year to leave it. The formula, with a calculator. Then sort by 3-year cost and split the list three ways:

  • Now: anything with a deadline or a security risk, and quick money such as unused seats before renewal.
  • This quarter: deployment blockers, retired automation on busy objects, stacked automation.
  • Into normal releases: documentation, unused metadata, old API versions.

That list, with dollar figures, is what gets a clean-up funded. The full audit method.

Common questions

What should I do first when I inherit a Salesforce org?
Change nothing for a week. Confirm your own access, find out who else is a System Administrator, list the integrations and who owns them, and check for anything with a date on it: certificates near expiry, limits near full, a renewal coming up.
Should I clean up unused fields right away?
No. A field that looks unused may feed a report, an integration or a formula. Map what depends on it first, and remove fields in a sandbox before production.
How long does it take to understand an inherited org?
A month gets you a working map and a ranked plan for most orgs. Knowing every corner takes longer, and you don't need that to start fixing the things that cost the most.