You are here:
Considerations for Deploying Processes
Keep these considerations in mind when deploying processes, such as when using packages or change sets.
Required Editions
| Available in: both Salesforce Classic (not available in all orgs) and Lightning Experience |
Change sets are available in: Professional, Enterprise, Performance, Unlimited, and Developer Editions Packages are available in: Essentials, Professional, Enterprise, Performance, Unlimited, and Developer Editions |
After December 31, 2025, existing processes continue to run, and you can activate, deactivate, and edit them; however, we recommend using Flow Builder. To migrate existing processes, plan your switch to Flow Builder and use the Migrate to Flow tool. For new automations, create flows in Flow Builder.
Processes That Reference Other Components
If you deploy a process that contains any of the following actions, the corresponding components aren’t included in the package or change set automatically. To deploy successfully, manually add the referenced components to the package or change set.
- Apex
- Email Alerts
- Launch a Flow
- Post to Chatter
- Quick Actions
- Submit for Approval
Templates
If you install a process template from a package, make sure the process is inactive unless you want it to actively run in your org.
If you add a process template to a package, first deactivate the process unless you’re sure that installers want that process to be active in their orgs.
Deploying Processes That Post to Chatter
If your process posts to the Chatter feed of a specific user or group, the process runs only in the source org. The IDs referenced by the Post to Chatter action don’t exist in the target org.
