Migration to Flows | Frequently asked questions

Salesforce will phase out these tools, so they’ll no longer be supported or updated after December 31, 2025. If something goes wrong, Sage People or Salesforce won't support or fix it. Salesforce wants to focus on a single, more powerful automation tool called Flow, which offers more features and flexibility than Process Builder and Workflow Rules

What is a Salesforce Flow?

A Salesforce Flow is a more advanced automation tool that allows you to create complex business processes with a visual interface. It combines the capabilities of both Process Builder and Workflow Rules, and adds more features.

What do I need to do?

Do I need to migrate all my existing automations to Flow?

Yes, migrate your existing automations to Flow before the retirement date. This will ensure they continue to work and receive support from Sage People and Salesforce.

Do I need to set up flows in both sandbox and production?

No, once you’ve migrated the Flows or created and tested in the sandbox, you can use Salesforce Change Sets functionality. This will easily move the flows from the sandbox to production.

How do I do it?

How do I start learning about Salesforce Flows?

You can start by exploring Salesforce's official documentation, Trailhead modules, and online tutorials to get familiar with Flow. Salesforce provides comprehensive documentation and guides for using the Migration Tool, and you can visit the Sage People community for further details.

Will there be any support available during the migration process?

Yes, as with the rest of your system, Sage People support is here to help with any issues. Our customer success team can guide your migration, and our partners can complete it for you if needed. If you face any issues, you can review our support information. You can also raise a case with Sage People Support through the Sage People community.

Can I test without notifying users?

Yes, testing in sandbox scrambles user emails. If you're testing in production you can disable email deliverability to stop emails sending, although we don’t recommend it.

Is there anyone who can complete this process for our company?

Yes, our partners can complete this process for your company. If you have an existing relationship with a partner, you can contact them directly; if not, contact our customer success team.

What steps does using the Migration Tool involve?

The steps typically include selecting the automations to migrate, reviewing the migration plan, and executing the migration. Detailed steps are in the tool's documentation.

When using the Migration tool, will it highlight areas of a process or rule that didn't migrate properly or had errors?

Yes, the Migrate to Flow tool in Salesforce does help identify areas of a process or rule that didn't migrate successfully. After the migration, the tool provides a list of actions that require more configurations. This helps you to review and resolve any issues to ensure the migrated Flow works as expected. The Flow Migration tool will highlight actions that require additional configuration. It can indicate if certain parts of the process are too complex to migrate using the tool. This allows you to review and resolve these complexities manually in Flow Builder.

Can I test the Migration Tool before using it in production?

Yes, it's recommended to test the migration in a sandbox environment before applying to your production.

What types of automations can I migrate using the tool?

The tool can migrate some automations created with Process Builder and Workflow Rules. We've included guidelines with examples of when and how to use the tool.

How long does the migration process take?

The duration depends on the complexity and number of automations you migrate.

What do I do if the migration fails?

If migration fails, review the error messages provided by the tool and review the Salesforce guidance to find steps to help. Further help is available from Sage People support who can give further guidance.

How can I verify that I have successfully migrated my automation?

After migration, test the automations in your sandbox environment to ensure they work as expected. The tool can also provide a summary of the migration results.

Can I create a new sandbox to test this specifically?

Yes, you can purchase more sandboxes; liaise with our customer success team for more information.

Can I deactivate a migrated Flow and move back to the Process builder before December?

Yes, that’s possible. However, we do recommend moving to Flow as quickly as possible and not reverting.

Do I need to migrate Managed Workflow Rules or Process Builders?

No, managed Workflow and Process Builders won’t appear in the Migration tool and will update via software updates.

If I migrate a Flow without errors, does that mean it's working correctly?

Not always. We recommend you test each Flow to make sure it's working as intended.

What about Process Builders?

What will happen to my existing Process Builder and Workflow Rules after the retirement date?

They’ll continue to function, but they won't receive any support or updates. Sage People and Salesforce won't fix any bugs or issues.

I have a Process Builder I don’t use anymore, do I migrate it?

You don't need to migrate a Process Builder that you won't need again. However, if there's a chance you’ll use it in the future, we recommend migrating it for future use.

Does the tool remove the old Process Builder or Workflow rule?

No, you can disable the old automation as part of this process and it will remain intact.

I have an active Process Builder and I'm unsure of its purpose - do I migrate it?

Test the Process Builder in your sandbox by completing the actions that trigger it and reviewing the result. For further clarity, contact our support team to review and explain the Process Builder's function. If you have multiple Process Builders with unclear functions, consider working with a partner to analyze your setup and help with migration.

Related features

Does this affect Action Events?

This change impacts only "Custom" Action events, as Process Builder delivers them. The Flow Migration Tool will convert the Process Builder element to a Flow, and the Action Event element of it will be unchanged. This change doesn't impact Action Events that aren't "Custom" Action Events, so you don't need to act.

Are there plans to retire Email Alerts?

There are no known plans to retire Email Alerts. Any Email Alerts you have that you send through Process Builder or Workflow will move across to Flow when using the Migration tool. They'll also be available to select in Flow.