Automation Builds
Part of Marketing workflow version control
Copying a live workflow into a test environment
Inventory dependencies, isolate outbound actions and check what a copied workflow can prove before updating production.
For a change rehearsal, decide what the copied live workflow must isolate: configuration, dependent assets, records and outbound connections. Copy only what the chosen product supports, list anything that did not transfer, and check every consequential destination before running an action.
Choose the kind of copy
Cloning a workflow in the live account creates another workflow in that account; it can be a starting point for editing but is not a separate test environment. Give the clone a distinct name and review its entry rules, actions and links before activation.
A separate sandbox can contain supported production assets where the product and subscription allow it. HubSpot standard sandboxes require a listed Enterprise subscription.
During creation, workflows with supported dependencies can copy; an unsupported dependency can prevent a workflow from copying. Check which assets copied and identify any that did not, rather than assuming the workflow arrived intact.
Supported vs. unsupported assets when copying workflows to sandbox
- Supported assets (can be copied)
- Workflows, forms, segments, emails, properties, user assignments, webhooks (if configured correctly)
- Unsupported assets (may prevent copy)
- Custom code secrets, certain connected apps, integrations relying on production-specific configurations
Inventory the dependencies
Record the live workflow ID and revision. List every dependency: form, segment, email, property, record association, user assignment, webhook, custom code secret and connected app. Mark each as copied, replaced with a test version or left disconnected. Record the starting data needed for the rehearsal.
In HubSpot, production integrations do not connect automatically to a standard sandbox. Before testing, check webhook destinations and other external references, and confirm each points where intended. Production and sandbox record IDs differ, so a copied diagram is an incomplete test setup until these references are checked.
Contain the routes you exercise
Before enrolling a record, inspect every path that could send a message, change a CRM record or call another service. Use controlled recipients and destinations where available. HubSpot says production integrations do not connect automatically to a standard sandbox, so check each workflow route separately rather than assume it is contained.
Use fictional or appropriately controlled records. HubSpot offers an option to copy some production contacts during sandbox creation, but real customer data is not automatically necessary to check a branch. If records are copied, review the need and access.
Write expected outcomes for an eligible record, an excluded record and each changed path. For an executed action, inspect the destination state as well as workflow history.
Decide how the change reaches production
Plan the return route before editing. HubSpot’s deployment feature applies to eligible supported assets: only new supported assets can be deployed, and edits to supported assets copied from production cannot be deployed. Do not assume a workflow is eligible; check the current eligible-assets list. For an existing live workflow, plan a controlled production edit or another supported route, then review the resulting production configuration.
A sandbox rehearsal establishes only what happened in that sandbox. After implementation, compare the approved change with production, record its revision and effective time, and check the production dependencies that could differ.
Workflow copy and deployment process from production to sandbox and back
- Confirm eligibility of assets for copying to sandbox (Enterprise subscription required)HubSpot standard sandboxes require Enterprise subscription
- Copy workflow and dependencies; note any that failed to transferCheck supported dependencies only; unsupported ones may block copy
- Test in sandbox using controlled records and destinationsUse fictional or isolated data; avoid real customer records unless necessary
- Plan return path: deploy via HubSpot deployment feature or manual editOnly new supported assets can be deployed; edits to copied assets cannot be deployed
- Compare sandbox outcome with production; record revision and effective timePost-implementation review ensures consistency and traceability
Key facts about HubSpot sandbox workflows and deployment
- Sandbox requirement
- Enterprise subscription needed for standard sandbox access
- Deployment eligibility
- Only new supported assets can be deployed to production
- Production integration connectivity
- Does not connect automatically to sandbox – must be manually verified
- Data handling
- Real customer data not automatically copied; use controlled or fictional records
