A big load and a long list of Flows and validation rules in the way. Config Switch in Toolkit for Salesforce turns them off in bulk, deploys the change, and puts everything back with one rollback button.
On this page
- The problem
- Switch off, or bypass?
- 1 · Get the metadata
- 2 · Turn off and deploy
- 3 · Check in Salesforce
- 4 · Roll back
- Gotchas and FAQ
Fifty validation rules and a deadline.
Sometimes a bypass is the wrong tool. When a big load needs automation switched off, clicking through Setup one rule at a time is how afternoons disappear.
A permission-based bypass keeps automation running for everyone except the migration user. That’s usually what you want. But sometimes you just need the Flows and validation rules off for the load window, and back on afterwards, exactly as they were.
That’s what Config Switch in Toolkit for Salesforce is for. It pulls your validation rules, workflows, triggers and Flows into one screen, lets you toggle them off in bulk, deploys the change, and rolls it all back with one button.
Prefer to read? Everything in the video is written out below.
Switch off, or bypass?
Pick the approach before you touch anything. They solve different problems.
| You need… | Use |
|---|---|
| Automation off for everyone during a controlled load window | Config Switch (this post) |
| Automation on for users, skipped only for the migration user | A permission bypass for Flows or validation rules |
Open Config Switch and get the metadata.
Config Switch reads your org’s automation into one list, so you can see everything that could get in the way of the load.
- Go to cloudtoolkit.co and select Config Switch from the left-hand menu.
- Log in to the Salesforce org you’re loading into.
- Click Get Metadata.


Turn the Flow off and deploy.
Toggling isn’t enough on its own. The change only reaches Salesforce when you deploy it.
- Open the Process Flows tab.
- Find the Flow. The example uses Cancel Policy.
- Toggle it off, then click Deploy Changes.

Validation rules, workflows and triggers work the same way, on their own tabs. Switch off as many as the load needs and deploy them together.
Check it in Salesforce.
A successful deploy isn’t proof. Look at the org.
Go back to Salesforce, refresh the Flows list, and confirm Cancel Policy no longer shows as active. Do the same spot check for a validation rule or two. Then run a small test load before the big one.
Roll back when the load is done.
Rollback to Original puts everything back exactly as it was before you started.
- In Config Switch, click Rollback to Original and deploy.
- Refresh the Flows page in Salesforce.
- Confirm Cancel Policy, and everything else you switched off, is active again.
Write down what you changed anyway: which components, why, and when they need to come back. If the rollback ever fails halfway, that list is your way back.
The questions people ask.
What can Config Switch turn off?
I toggled the Flow off but it still ran
Is this better than a Flow bypass?
What do I do after the migration?
Automation is one line on the cutover plan.
The Masterclass covers the full migration in load order, including what to switch off, when, and how to prove it all came back on.
Know someone about to click through fifty validation rules by hand?
Share on LinkedInOne CSV is a tutorial. Forty objects, 15 years of history and a go-live date is a project. That’s the part I do for a living.
See how I run migrations →