Free checklist
Agentforce readiness checklist: 20 checks for your Salesforce org
20 checks in 5 groups, in the order to do them. Each one says where to look in Setup and why it matters. Tick them off as you go. No email, no download.
By VanguardOps, written by a Salesforce architect with 13+ years in enterprise orgs. Updated November 11, 2026.
0 of 20 checked
1. Can Agentforce run in this org at all?
Settle these first. Nothing else matters until they are true.
Where to look: Setup, Company Information, Permission Set Licenses. Look for labels containing Agentforce or Einstein.
Why it matters: Without one, agents can't be turned on, however clean the org is.
The VanguardOps scan checks this for you.
Where to look: Same list of permission set licenses, or ask your Salesforce account team.
Why it matters: Agentforce uses it to ground answers and to record usage.
The VanguardOps scan checks this for you.
Where to look: Setup, Einstein Setup.
Why it matters: Agent building tools depend on it.
Check this one by hand. The scan doesn't cover it.
Where to look: A page of text, agreed with whoever owns that process.
Why it matters: "Ready for Agentforce" only means something against a specific job.
Check this one by hand. The scan doesn't cover it.
2. Can an agent understand your data model?
An agent reads names and descriptions to decide which data to use.
Where to look: Object Manager, Fields & Relationships. Sort by Description to find the blanks.
Why it matters: A field called Status_2__c with no description is a guess for an agent and for the next admin.
The VanguardOps scan checks this for you.
Where to look: Schema Builder, or Fields & Relationships on each object.
Why it matters: An agent gets from a customer to their open cases by following relationships.
The VanguardOps scan checks this for you.
Where to look: Object Manager, Validation Rules. Look for long formulas and deeply nested brackets. The scan checks error-message length; formulas you check by hand.
Why it matters: When a rule rejects an agent's update, the error message is all it has to go on.
The VanguardOps scan checks this for you.
Where to look: Duplicate rules and reports on blank key fields.
Why it matters: An agent answers from the data it finds. Wrong data gives confident wrong answers.
Check this one by hand. The scan doesn't cover it.
3. Can an agent act safely?
Agents act through flows and Apex, with the access you give them.
Where to look: Setup, Permission Sets. Check assignments on each.
Why it matters: You can't give an agent the right access and no more if nobody knows what each permission set is for.
The VanguardOps scan checks this for you.
Where to look: The agent user's permission sets, object and field permissions.
Why it matters: An agent with broad access can read and change more than its job calls for.
Check this one by hand. The scan doesn't cover it.
Where to look: Setup, Flows. Sort by API name; open the largest. The scan checks naming; flow size you check by hand.
Why it matters: Flows are how agents get things done. You need to be able to tell them apart and follow what one did.
The VanguardOps scan checks this for you.
Where to look: Setup, Flows (type Autolaunched), and Apex classes with @InvocableMethod.
Why it matters: An agent can only take actions that have been built and exposed to it.
Check this one by hand. The scan doesn't cover it.
4. Is the automation underneath stable?
An agent's actions set off whatever automation is already on the object.
Where to look: Setup, Process Builder, and Setup, Workflow Rules. Or use Migrate to Flow.
Why it matters: Salesforce ended support for both on December 31, 2025. They still run, but bugs in them won't be fixed.
The VanguardOps scan checks this for you.
Where to look: Flow Trigger Explorer for flows; Apex Triggers and Workflow Rules for the rest.
Why it matters: Stacked automation runs in an order that's hard to predict. An agent's update can set off all of it.
The VanguardOps scan checks this for you.
Where to look: Setup, Apex Test Execution, and Apex Classes, Estimate your organization's code coverage.
Why it matters: Below 75% you can't deploy Apex to production, including new agent actions.
The VanguardOps scan checks this for you.
Where to look: Setup, Apex Classes and Apex Triggers. Check the Api Version column.
Why it matters: Code on retired versions is the first thing to break and the hardest to change.
The VanguardOps scan checks this for you.
5. Is everything around the agent ready?
Integrations, knowledge and the people who will run it.
Where to look: Setup, Connected Apps OAuth Usage; Named Credentials; Certificate and Key Management.
Why it matters: Agents often call outside systems. A weak or expired connection is where that fails.
The VanguardOps scan checks this for you.
Where to look: Knowledge, filtered to published articles for the topics the agent covers.
Why it matters: A service agent answers from your knowledge base. Gaps and stale articles become wrong answers.
Check this one by hand. The scan doesn't cover it.
Where to look: A sandbox with Agentforce on, and Agentforce Testing Center.
Why it matters: You want to see the agent get it wrong in a sandbox, not in front of a customer.
Check this one by hand. The scan doesn't cover it.
Where to look: A named person, with time set aside each week.
Why it matters: Agents drift as the org changes around them. Someone has to notice.
Check this one by hand. The scan doesn't cover it.
The scan covers 12 of these 20 checks. Your ticks are saved in this browser only.
What to do with the result
If group 1 isn’t fully ticked, stop there and talk to your Salesforce account team. If it is, pick the first agent’s job, then fix the unticked items on the objects that job touches. You don’t need the whole org clean to start; you need the part the agent will use to be clean.
Common questions
- What should be on an Agentforce readiness checklist?
- Five things, in this order: whether Agentforce can run in the org at all (licenses and settings), whether an agent can understand your data model (field descriptions, relationships, validation rules), whether it can act safely (permission sets, flows, actions), whether the automation underneath is stable (no Process Builder or workflow rules, tested Apex), and whether everything around it is ready (integrations, knowledge, testing and an owner). This checklist has 20 checks across those five.
- How long does the checklist take?
- By hand, expect a few hours for a small org and a few days for a large one, most of it on field descriptions, permission sets and flows. The VanguardOps scan covers 12 of the 20 checks in a few minutes; the rest need a person.
- Do I need to finish every check before turning on Agentforce?
- No. The first group is required: without a license and the right settings nothing runs. The rest lower the risk. A narrow first agent on a well-described object can go ahead while you clean up the rest of the org.
- Is this an official Salesforce checklist?
- No. It is VanguardOps' own list, written by a Salesforce architect from what makes agents work or fail in real orgs. Salesforce's documentation is the authority on product requirements.