Hi
I'm working on a data migration project. The issue i'm facing is that processes defined to launch on Create (CRUD) actions are triggering during the migration.
What is the best/fastest way to temporarily deactivate these processes and prevent them from launching during data migration?Kind regardsThibaut
Hi Thibaut,
This is a common issue during data migrations CRUD-based business logic firing unintentionally during bulk data loads. The best approach depends on the platform you're using.
Use a Migration Flag / Context Bypass
Add a field like isDataMigration or Source to the records being migrated.
Update your automation logic (triggers, workflows, processes) to check this flag and exit early if the flag is true.
This is clean, maintainable, and gives you control over future migrations as well.
if (Trigger.isInsert && !Trigger.isExecutingMigration) {
// only run logic when not a migration
}
This lets you avoid turning processes off entirely, reducing post-migration risks.
Hi JR,
Thank you for your response.
This approach is functional, but it does present some challenges. Specifically, each record creation triggers a process, even if that process ultimately skips its internal logic. Consequently, millions of processes will be initiated during the migration, which is far from ideal.Ideally, we don't want to trigger any processes during the migration.(even if there is no logic within said process)
Hi,
You're right, setting a migration flag to bypass logic within automated processes is a workable solution, but it's important to note that it doesn't prevent the processes themselves from being triggered which, at the scale we're migrating, would result in millions of unnecessary process initiations.
To avoid performance impacts and system strain, I recommend temporarily deactivating the relevant automation components (such as [Flows / Triggers / Workflows, depending on your system]) for the duration of the migration. This ensures no processes are launched at all during the data load.
Once migration is complete, we can re-enable the components and run post-migration validations.
Pros: Best option for performance
Cons: Requires careful tracking and post-migration reactivation
Hello,If the environment where you will be working is a self-managed one, you can disable execution of all processes in Service Center, under Administration and then Servers.Disable "Processes" for all servers before the migration, and re-enable them after you are finished.
Hi Sérgio,Thank you for the reply.
Unfortunately the destination environment is part of a O11 Cloud platform.