Skip to main content
Procore Support (en-au)

Self-Serve Workflows Migration

  1. Last updated
  2. Save as PDF

 

How do I transition from Legacy (v1) to Self-Serve (v2) Workflows? 

To transition your company from Legacy Workflows to the Self-serve Workflows beta, you will need to work with Procore to determine if Self-Serve Workflows is the right fit. We have intentionally made this process manual because for the following reasons:
 

  1. Once the Self-serve (v2) Workflow engine has been turned on for a given tool (such as Commitment(s), it cannot be switched back to the Legacy Workflows engine. We want to make sure users are confident about the transition and do it at a time that makes sense for them. 

  2. Procore cannot migrate Legacy workflow templates to the Self-serve workflows engine, meaning they will need to be rebuilt. We want to make sure you can rebuild your workflows in Self-serve before you make the switch. To learn more about the differences between both workflow engines, See What are the differences between legacy and self-serve workflows?

  3. Some features, such as Reporting on the current assignee, public API and custom response types, still need to be made available with Self-serve workflows. If your Legacy workflow process depends on these features, it may be best to wait a few months before you make the switch. 

Can I test self-serve workflows before transitioning?

Yes, you can create workflow templates, assign them to projects and configure them, all without switching completely to the self-serve workflow engine. Your projects will continue to use the legacy engine until you have made the transition complete. Procore recommends that you plan and build self-serve workflow templates before switching so you will know if your workflow requirements can be met. To learn more about the creation and configuration of self-serve workflows, follow our guide here: Workflows - User Guide.

You can also try self-serve workflows in our monthly sandbox environment, where you can try out the full process of going through a workflow before you commit to making the switch in your company’s live Procore environment. 

What steps should I complete before updating my workflows:

Procore recommends completing the following steps:
 

  1. Create a Custom Workflow Template 

  2. Assign a Custom Workflow Template to a Project 

  3. Configure a Custom Workflow Template on a Project
     

After you follow these steps and switch to the Self-serve workflows engine, any new items created within the transitioned tool will now be using the workflow template you defined. 

What happens to items that are currently going through a workflow when I make the switch?

These items will need to restart their workflow after you configure a self-serve workflow on the project. 

Will Procore’s Custom Solutions team help me rebuild the workflows in the self-serve engine?

No, the self-serve workflows engine is built to empower you to build and manage workflows without needing to pay or wait for assistance. However, if you have questions or if something is not working as intended, please get in touch with our support team or reach out to your Procore representative. 

What are the next steps? 

After reviewing this page and the linked support documentation, if you are ready to transition to the self-serve workflows engine, you may request access to update specific tools. Once access has been granted, the ‘Update’ button will become available and you can update at any time. Receiving access to the ‘Update’ button will not make the update occur automatically. You will need to update the desired tool in the Workflows tool configurations. See Migrate your Company to Self-Serve Workflows.