When a new site is provisioned, it starts with an empty workflow library. Rather than rebuilding workflows from scratch, you can request that Cumulus support copy one or more workflows from an existing site. This is the fastest way to replicate a proven operational process across multiple projects.
📋 Note
Workflow copying is performed by the Cumulus backend team. End users cannot copy workflows between sites directly from the Control Center UI.
When to Use This Process
- A new site has been provisioned and you want to replicate workflows from an existing site.
- A customer has multiple locations running the same procedures.
- You want to standardize activities across different projects.
Information Required for the Request
| Field | Description |
|---|---|
| Source Site Name | The site you want to copy workflows from |
| Destination Site Name | The site you want to copy workflows to |
| Workflows to Copy | List specific workflow names, or state "all workflows" |
| Include Nested Activities? | Yes/No — whether sub-activities and child steps should be included |
| Override Existing? | Whether to overwrite workflows with the same name at the destination site |
How to Submit the Request
- Submit a support ticket at support@cumulusds.com or via the Zendesk Support Portal.
- Use the subject: "Workflow Copy Request – [Source Site] to [Destination Site]"
- Include all fields listed in the table above.
- If copying from multiple source sites, submit one request per source-destination pair.
After the Copy Is Complete
- Cumulus support will notify you when the copy is done (typically within 1–2 business days).
- Log in to the destination site in Control Center and navigate to Workflows to verify the copied workflows appear correctly.
- Review all workflow steps in the destination site before activating for field use — tool assignments, torque specs, and asset references may need to be updated for the new site's equipment.
⚠️ Verify Tool Assignments After Copy
Copied workflows retain tool model references from the source site. If the destination site uses different tool models or serial numbers, update the tool assignments within each workflow before deploying to field users.