Your First 90 Days as a New Salesforce Admin

Written by Desere Balicog Acedo · Reviewed by Dedric Brown, Salesforce Product Manager and founder of Blazer2Role · Published October 7, 2026 · Facts verified October 7, 2026

• No computer science degree required
• Built for 3+ years of professional experience
• A real plan, not a pep talk

You got the job. Congratulations. Now comes the part nobody prepares you for: logging into an org someone else built, full of fields you did not create, automation you cannot see, and users who expect you to fix things on day one. Your first 90 days decide how your team sees you for the next two years. This guide gives you a practical plan, month by month, built around how admin work actually happens. If you want a refresher on the daily rhythm first, read what a Salesforce admin actually does all day.

In this guide

1. Before day one
2. Days 1 to 30: learn the org and the people
3. Days 31 to 60: quick wins and safe habits
4. Days 61 to 90: own the roadmap
5. Mistakes new admins make
6. If you are the only admin
7. Questions people ask

Before day one

A little preparation keeps your first week from feeling like drinking from a fire hose.

• Ask about access: confirm you will get System Administrator access, a sandbox, and access to any integrated tools such as email, marketing, or support systems.
• Ask who the users are: which teams use Salesforce, roughly how many users there are, and which clouds the company runs, such as Sales Cloud or Service Cloud.
• Ask about history: was there an admin before you, a consultant, or nobody? This tells you how much documentation to expect.
• Refresh the basics: review security, data model, and Flow on Trailhead, because these are the areas you will touch first.

Days 1 to 30: learn the org and the people

Your goal this month is understanding, not output. Resist the urge to impress people with quick changes in production before you know what depends on what.

• Meet your stakeholders: schedule short conversations with each team that uses Salesforce. Ask what they use daily, what frustrates them, and what they wish the system did.
• Shadow real users: watch a sales rep or service agent work for an hour. You will spot more problems than any requirements document shows.
• Inventory the org: list the main objects, custom fields, record types, profiles, permission sets, active Flows, and integrations. A simple spreadsheet works.
• Check recent changes: review the Setup Audit Trail to see who changed what recently, which tells you where the active work and risk sit.
• Run Health Check: Salesforce Health Check shows a summary score against a security baseline and lists settings that are less restrictive than recommended, per Salesforce Help. Note the risks, but do not fix everything at once.
• Start a decision log: write down what you learn and why things are built the way they are. Future you will need it.

Here is the first honest concession: the org you inherit is probably messier than you hoped. In the SF Ben 2026 admin survey, 56.3 percent of admins said technical debt is their biggest challenge, and only 2 percent described their org as clean and well maintained. You will not fix that in 90 days, and nobody reasonable expects you to.

Days 31 to 60: quick wins and safe habits

Now you can start changing things, carefully. Pick wins that are visible, low risk, and easy to undo.

• Build in a sandbox first: make and test every change in a sandbox before production, even small ones. This habit protects you more than any skill.
• Fix daily annoyances: a cleaner page layout, a missing list view, or a report a manager keeps asking for. Small fixes earn trust fast.
• Clean one slice of data: merge duplicates or fix a messy picklist for one team. Show the before and after.
• Set up a request process: give users one place to submit requests, such as a simple form or a case queue, so work stops arriving through hallway conversations.
• Write release notes: tell users what changed, in plain language, every time you deploy. Teams forgive a lot when they are kept informed.
• Train as you go: a five minute screen share showing a new feature often matters more than the feature itself.

Second concession: you will break something. Maybe a validation rule blocks a sales rep, or a field change hides data from a team. It happens to every new admin. Testing in a sandbox, changing one thing at a time, and documenting what you deploy make those mistakes small and quick to reverse.

Days 61 to 90: own the roadmap

By month three you know the org, the people, and the pain points. Turn that knowledge into a plan your manager can see.

• Build a backlog: list every request and problem you found, then rank them by business impact and effort.
• Pick one meaningful project: for example, replacing a manual process with a Flow, rebuilding a messy report set, or cleaning up permissions for one team.
• Tackle one security item: security is a common weak spot. In the SF Ben survey, 41.9 percent of admins identified security management as a key skills gap, so even one fixed Health Check risk stands out.
• Retire what nobody uses: unused fields, reports, and inactive automation add confusion. Document before you remove anything.
• Present a 90 day summary: show your manager what you learned, what you fixed, and what you recommend next. This is how you turn from new hire into trusted owner.

Third concession: a 90 day plan bends to the business. A product launch, an urgent integration, or a reorganization can take over a month without warning. Keep the plan, but adjust it openly instead of pretending nothing changed.

Mistakes new admins make

• Changing production directly: skipping the sandbox to save time is the fastest way to lose trust.
• Saying yes to everything: every request becomes urgent when there is no process. Log requests and prioritize them openly.
• Granting broad access to stop complaints: giving users extra permissions to solve a visibility problem creates security risk later.
• Building without asking why: a requested field is often a symptom of a process problem. Ask what the user is trying to achieve first.
• Not documenting: undocumented changes become the next admin's technical debt, and that next admin might be you in a year.
• Hiding confusion: asking a question in the Trailblazer Community or a user group is faster than guessing in production.

If parts of the platform still feel hard, that is normal. Our guide on whether Salesforce is hard to learn explains which topics take everyone longest.

If you are the only admin

Many new admins work alone. In the SF Ben 2026 admin survey, about 20 percent of admins manage their org entirely alone, 43 percent work without developer support, and 53.1 percent feel too much is expected of admins.

• Set expectations early: agree with your manager on response times and how requests get prioritized.
• Build an outside network: join a local or virtual user group so you have people to ask.
• Use AI carefully: about 44 percent of admins use AI daily or regularly, per the same survey. It helps with formulas and documentation, but test everything it suggests in a sandbox.
• Protect learning time: block an hour a week for Trailhead or release notes, or the job will eat it.

Your previous career helps here too. The communication and process skills that got you hired, covered in our guide to transferable skills for tech jobs, are what make a solo admin effective. If you are still preparing for the role, see how pay grows after year one in our entry level Salesforce salary guide.

Blazer2Role sells the coaching and courses described here. We do not guarantee job placement. If you are starting a new admin role and want a second opinion on your 90 day plan, email support@blazer2role.com.

Questions people ask

What should a new Salesforce admin do first?
Start by learning, not changing. Meet each team that uses Salesforce, shadow real users, inventory objects, fields, permissions, and automation, review the Setup Audit Trail, and run Health Check. Document what you find. Make your first changes in a sandbox only after you understand what depends on what.

How long does it take to get comfortable as a new Salesforce admin?
Most new admins feel comfortable with the daily work within about three months, though complex orgs take longer. The first month is mostly learning the org and the people. Confidence grows fastest when you build in a sandbox, document changes, and ask questions in the community instead of guessing.

What is a 30 60 90 day plan for a Salesforce admin?
It is a simple roadmap for your first three months. Days 1 to 30 focus on learning the org and stakeholders. Days 31 to 60 deliver small, safe wins built in a sandbox. Days 61 to 90 turn your findings into a prioritized backlog, one meaningful project, and a summary for your manager.

What mistakes do new Salesforce admins make?
Common mistakes include changing production without testing in a sandbox, saying yes to every request without a process, granting broad permissions to stop complaints, building fields without asking why, and skipping documentation. Each one creates technical debt or security risk that becomes harder to undo later.

What if I am the only Salesforce admin at my company?
You are not alone in that. About 20 percent of admins manage their org entirely alone, per the SF Ben 2026 admin survey. Set clear expectations with your manager, create a simple request process, join a user group for support, and protect time each week for learning.

Should I use AI as a new Salesforce admin?
Yes, carefully. About 44 percent of admins use AI daily or regularly, per the SF Ben 2026 admin survey. AI helps draft formulas, documentation, and user guides, but it can be confidently wrong about your org. Test every suggestion in a sandbox before anything reaches production.