Your record-triggered Flows are great at their day job. During a data load, they also stamp today’s date on 2014 records and fire off emails nobody asked for. Here is how to let the migration user skip them while everyone else keeps the automation.
On this page
- The problem
- 1 · Custom Permission
- 2 · Permission Set
- 3 · Assign the user
- 4 · Edit the Flow
- Test, then load
- Gotchas and FAQ
Your Flow is doing its job. That’s the problem.
Record-triggered Flows that are useful every day can do the wrong thing to hundreds of thousands of migrated records in an afternoon.
The example from the video: an active Flow fires when a record’s Status changes to Active, and sets Client Start Date to today. Lovely for a new client signed this morning. Less lovely for a client who became Active in 2014 and is being migrated today, because now their start date says 2026.
You could deactivate the Flow for the load. But then it’s off for everyone, and you have to remember to turn it back on. The cleaner option is a bypass: the Flow stays active, and it skips one user, the one doing the migration.
Prefer to read? Everything in the video is written out below.
Create a Custom Permission.
This is the flag the Flow will check to decide whether the running user gets a pass.
- In Setup, search for Custom Permissions and click New.
- Name it Bypass Flows. The API name becomes
Bypass_Flows. - Save.
Already set up a validation rule bypass? Keep the two permissions separate. Sometimes you want the rules on and the automation off, or the other way round.
Put it in a Permission Set.
A Permission Set lets you give the bypass to one person and take it away again later, without touching profiles.
- In Setup, open Permission Sets and click New.
- Call it Bypass Flows. No license type is needed.
- Open Custom Permissions inside the set, click Edit, add Bypass Flows and save.
Assign it to the migration user.
Whoever logs into Data Loader for the load gets the Permission Set. Nobody else does.
From the Bypass Flows Permission Set, click Manage Assignments → Add Assignment, pick the migration user and click Assign. A dedicated migration user makes this cleaner, and makes it obvious later which records came in with automation bypassed.
Teach the Flow to check the permission.
Add one condition to the Flow’s entry criteria so it only runs for users who do not hold Bypass Flows.
Open the Flow, click the Start element, and keep your existing condition. Then make the entry criteria require that the running user doesn’t have the permission. With a formula, it looks like this (the video’s example triggers on Status = Active):
AND(
ISPICKVAL( {!$Record.Status__c}, "Active" ),
NOT( {!$Permission.Bypass_Flows} )
)Swap Status__c for your own field. The important line is the last one. When the running user holds Bypass Flows, the whole AND() is false and the Flow never starts. Everyone else triggers it exactly as before.
Don’t break the original condition. The bypass is added to the logic. It must not change when the Flow normally runs. Save as a new version, and the Flow stays active the whole time.
Test both users, then load.
Two quick tests tell you the bypass works and that you didn’t break the Flow for everyone else.
- 1
As a normal user
Change a test record to Active. Client Start Date should still fill in. The Flow is fine.
- 2
As the migration user
Do the same. Client Start Date should stay as it was. The bypass works.
- 3
After the migration
Remove the Permission Set assignment, and review the imported records for anything the Flow would normally have filled in. Bypassing the Flow doesn’t make the data right on its own.
The questions people ask.
Can I bypass a Flow without deactivating it?
Does this affect other users?
I set it all up, but the Flow still runs during my load
$Permission.Bypass_Flows with the right API name.Can I bypass a lot of Flows at once?
What do I do after the migration?
Automation is one piece of the load plan.
The Masterclass covers the whole migration in load order, including when to bypass, when to deactivate and what to clean up afterwards.
Know someone whose Flows keep firing during a data load?
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 →