Skip to main content
Clientell AIClientell AI

Find the old automations still running in your org.Free, read-only, in about 10 minutes.

For Salesforce adminsRead-onlyFree

Process Builder and Workflow Rules lost support on 31 December 2025. They still run. Connect production for a read-only scan, get a health score, then connect your sandbox to get a migration plan that is built and tested for you.

Connect your production orgGet a demo
Free scan · Read-only · No credit card

Connect your org.
Report in 10 minutes.

Read-onlySOC 2No install
You receive
Live chat + PDF~10 min
© Clientell AI 2026 · Privacy · Terms
Why now

Support ended. The automations did not stop.

Process Builder and Workflow Rules lost Salesforce support on 31 December 2025. They still run in your org today. That is the risk: old logic keeps working until the day a change makes it fail, and no one at Salesforce will fix it.

Process Builder and Workflow Rules
  1. Before 2026

    Both tools are the standard way to automate. Most orgs build dozens.

  2. 31 Dec 2025

    Salesforce ends support for both. No more fixes from Salesforce.

  3. Today

    They still run in your org. The scan lists each one and what it touches.

What the scan finds

The old automations nobody wants to touch.

Most orgs have years of Process Builder and Workflow Rules. They run quietly until a change breaks one. The scan lists every one and shows what it touches.

What it looks at
4 areas
  • 01
    Process Builder and Workflow Rules still running

    A full list, with the objects and fields each one reads and writes.

  • 02
    Automations that overlap

    Two or more automations that fire on the same record and can undo each other.

  • 03
    Old automations that nobody owns

    Rules with no clear purpose, no recent change and no one to ask.

  • 04
    What is safe to move first

    A short order for the migration, starting with the low-risk ones.

Sample report

What you get back.

A health score, the list of old automations still running, and a short migration plan. The card below is an example to show the shape. Your report is built from your own org.

Sample report
Example only
Automation health

Legacy automations still run on live objects. Four should move first.

Still running
  • Lead assignment (Process Builder)
    Touches: Lead, Owner, Queue
    High risk
  • Set renewal date on close (Workflow Rule)
    Touches: Opportunity, Contract
    Medium risk
  • Email alert on case escalation
    Touches: Case, Email template
    Low risk
  • Update account tier (Process Builder)
    Touches: Account, Opportunity
    High risk
Migration plan
  1. 1Start with the low-risk rules. Rebuild each as a Flow in your sandbox.
  2. 2Test each Flow against the old behaviour. Show you the difference.
  3. 3Move the high-risk ones last, with a rollback.

Example data to show the shape of the report. Your score and your list come from your own org.

Start the scan

Connect production. Read-only. About 10 minutes.

Then connect your sandbox to get the fix plan.

Connect your production orgBook a demo

Read-only · SOC 2 Type II · No credit card

How it works

Scan production. Fix in the sandbox.

The scan needs only production, and it only reads. The fix plan needs a sandbox, because that is where we can build and test the new Flows without risk to your live org.

Four steps
  1. 01
    Connect production, read-onlyAbout 10 minutes

    The scan reads your automations and how they connect. It changes nothing.

  2. 02
    Get your health scoreFree

    A score with the reasons beside it, and the list of Process Builder and Workflow Rules still running.

  3. 03
    Connect your sandboxSafe place to test

    This is where the fix plan is built. We rebuild each rule as a Flow and test it there.

  4. 04
    Roll out the fixesProduction

    Clientell AI asks before it changes anything in production.

Safety

Read-only on production. Always.

You see the permissions before you approve the connection. Fixes are built in your sandbox. Clientell AI asks before it changes anything in production.

What the scan can and cannot do
Read-only
It reads
  • Your automations: Process Builder, Workflow Rules and Flows
  • The objects and fields those automations use
  • How automations depend on each other
It never
  • It does not create, change or delete anything in production
  • It does not deploy during the scan
  • It does not keep a copy of your records
Common questions

What admins ask before they connect.

FAQ

Answers, before you start.

More on plans on the pricing page, or see how this fits our full Salesforce health check and flow audit.

Common questions
  • Yes. The scan only reads. It cannot create, change or delete anything in your production org. You connect production for the scan. Any fix is built and tested in your sandbox.
Free scan

Find out what is still running.

Connect your production org. Then connect your sandbox to get the fix plan.

Connect your production orgBook a demo

Read-only · SOC 2 Type II · No credit card