Currently, there's no way to move workflows, propertities, or other items FROM a sandbox enviornment to our Production account. There needs to be an easier way to do this instead of recreating.
Don’t miss this opportunity to surface any questions you have as you begin adopting these new features, and learn how to build, test, and deploy with confidence.
Hey @AlonzoBrown and @Jigar_Thakker - You can enroll to our public beta from any production portal with an enterprise subscription! Please search for the product update titled "New Standard Sandbox with improved production metadata & deploy to production supported assets"
@RLPena - you can use the records import & export tool to add additional records to your sandbox. Please let me know if you have any additional questions!
Hi @Jigar_Thakker - we'll let you know when we're ready to give you access to the beta. Thanks for your patience as the team has been working on some additional optimizations over the last weeks.
@RLPena - are you referring to allowing more production records in Sandbox?
I'm the Product manager for Sandboxes, and we're actively looking for private beta testers for our deploy to production MVP. For anyone who's open to being part of this, please fill out this form and we'll be in touch. Thank you!
Hi everyone! My name is Hallie and I am an APM on the CXM team here at HubSpot. I'm excited to share that there is a Private Beta for deploying Sandbox workflows and properties to Production. The Product Manager is going to share a link in a comment below shortly that you can click if you are interested in participating in this Beta.
This is 100% needed and the main reason I DON'T USE SANDBOX... If we have to manually do all of this work twice, that's often worth the risk to just build it in production and hope it goes well.
There's no reason to offer a sandbox environment if the user can't move the workflow to production after testing! Having to recreate the workflow just creates more friction and introduces more opportunities for human error, defeating the purpose of testing in the first place. PLEASE prioritize this feature!
I totally agree! I love the workflow functionality, it ticks all the boxes, but if I build out a whole workflow and then test it, I don't like that I have to recreate it manually. That just opens up so much room for error.
We would also like to see this feature prioritised ASAP. There is a lot of room for error in Hubspot at the moment which is a huge risk for enterprise customers.
For what they charge this option should have been a priority a long time ago. It's 2023 and we still can't do something as simple as moving a website from one environment to another.
Agreed with everyone. There should be a way to move/export a workflow from sandbox and vice versa, since a workflow can lead to enrolling in another workflow. I can't believe I have to recreate everything just to test something to make sure it works. It needlessly wastes a lot of time
Was seriously considering bumping my subscription up to enterprise as a sandbox was a key selling point. Now I have tested it during the trial I am utterly disappointed that changes can't be synced back to the production environment. (I miss Salesforce )
We just upgraded to Enterprise with the sandbox as a selling point and didn't even think to check that things could be pushed from Sandbox to Production because... duh? Why would we waste our time building out a complex pipeline with a ton of sophisticated workflows in the sandbox to test if we have to completely rebuild them on the production side once they work the way we want? That is the most monumental waste of time ever.
Please add this! Not only is it a lot of work to re-build the workflows in production after they are tested successfully in the sandbox, but it brings in an element of risk if they are not rebuilt exactly the same.
a migration tool with validation stages will improve the delivery process and synchronization. Fields don't necessarily need to follow same convention as long as the mapping by the migrator is valid