---
schema_version: "1"
id: ffb463b3a41bb0b17d8ef37f6e89b5904fe144bd6b2ab8302ae6b5cad9526ff6
title: Considerations for Deploying Processes
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/platform/264-0-0/process_changesets_packaging.md
canonical_url: https://help.salesforce.com/s/articleView?id=platform.process_changesets_packaging.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 3a5913cf8a833d7ccc014ccc3989e86b4027c73462c1a119e4b68ebf6ef26cb4
description: Keep these considerations in mind when deploying processes, such as when using packages or change sets.
products:
  - Flow Builder
  - Salesforce Platform
release: "264"
---
# Considerations for Deploying Processes

Keep these considerations in mind when deploying processes, such as when using packages or change sets.

### Required Editions

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small edition">
      <colgroup>
        <col>
      </colgroup>
      <tbody>
        <tr class="">
          <td class="slds-cell-wrap" style="vertical-align:top;">Available in: both Salesforce Classic (<a href="https://help.salesforce.com/s/articleView?id=xcloud.overview_edition_lex_only.htm&amp;language=en_US" target="_blank">not available in all orgs</a>)
            and Lightning Experience</td>

        </tr>
        <tr class="">
          <td class="slds-cell-wrap" style="vertical-align:top;">
            <p>Change sets are available in: <strong>Professional</strong>, <strong>Enterprise</strong>,
              <strong>Performance</strong>, <strong>Unlimited</strong>, and <strong>Developer</strong> Editions
            </p>
            <p style="margin-bottom:0;">Packages are
              available in: <strong>Essentials</strong>, <strong>Professional</strong>, <strong>Enterprise</strong>,
              <strong>Performance</strong>, <strong>Unlimited</strong>, and <strong>Developer</strong> Editions
            </p>
          </td>

        </tr>
      </tbody>
    </table>

![Important](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-platform-platform_automation-264-0-0-production-enus/60568438-ec7e-4665-acd1-7c80dcbe60d5/images/icon_important.png)

Important Support and updates for Process Builder have ended as of December 31, 2025. This means that support won't be provided for any process and bugs in the Process Builder product won't be fixed. See [Workflow Rules & Process Builder End of Support](https://help.salesforce.com/s/articleView?id=001096524&type=1&language=en_US).

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](https://help.salesforce.com/s/articleView?id=platform.flow_migrate_to_flow_learning_map.htm&release=264.0.0&type=5 "Flow Builder combines the capabilities of workflow rules and Process Builder in a single point-and-click tool, making it easier to create a triggered process. If you created triggered processes with workflow rules or Process Builder, use the Migrate to Flow tool to move them to Flow Builder. Start by migrating and testing in a sandbox environment before moving your new flows to production.") and use the [Migrate to Flow](https://help.salesforce.com/s/articleView?id=platform.flow_migrate_to_flow.htm&release=264.0.0&type=5 "Use the Migrate to Flow tool to convert your Process Builder processes and workflow rules into Flow Builder, including scheduled actions. The tool also supports partial migration of processes for most actions.") tool. For new automations, create flows in [Flow Builder](https://help.salesforce.com/s/articleView?id=platform.flow.htm&release=264.0.0&type=5 "Automation reduces repetitive work and helps your team complete tasks faster and more accurately. With Flow Builder, you can build simple or complex automations, forms, and guided experiences with no code. You can add forms to Salesforce pages and Experience sites, and launch flows using buttons, record triggers, or schedules.").

## 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.

#### See Also

- [Deploy Processes and Flows as Active](https://help.salesforce.com/s/articleView?id=platform.flow_distribute_deploy_active.htm&release=264.0.0&type=5 "By default, processes and flows that are active in a sandbox or non-production org are deployed to a production org as inactive. After deployment, manually reactivate the new versions. In production orgs, you can enable the setting to deploy a new active version of a process or flow via change sets or Metadata API. If you use a continuous integration and continuous delivery model to deploy metadata changes, enable the option to deploy processes and flows as active.")