Ability to choose sync direction between HubSpot Sandboxes and HubSpot Production Environments
Currently, you can only sync from the production to the sandbox. If could also sync in the other direction that would be awesome and will allow development teams to mimic their actual deployment flow. In development, it is uncommon to create something in production before creating it in a test/dev environment.
This feature is now in public beta as part of our new standard sandbox.
How to participate in the beta?
Enterprise Hub Customers can enroll their production portal to the following public beta under "Product Updates":
New Standard Sandbox version with improved copy of production metadata & deploy to production
Once enrolled you'll get access to an additional standard sandbox during the beta period so you can get started with the new sandbox and deploy to production feature.
Just heard that this is in beta: Here's what included for now:
What is it?
You can now push net new custom object definitions, pipelines, and CMS themes, templates and modules from your sandbox back to your production account. You will be able to select individual pipelines, custom object definitions or themes/templates/modules to push back to your production account.
Why does it matter?
Sandboxes are used to reduce the time and risk of experimenting and testing. In order to save time and reduce potential human error across the process, we need to make it as easy to push what you've built back into production as it was for you to set-up your Sandbox in the first place. Push to production will help you bring the changes that are important back to your production account, while leaving other changes in the Sandbox.
How does it work?
Customers will be able to select individual pipelines, custom object definitions or themes/templates/modules to push back to their production account. They will only be able to push assets that were created for the first time in the sandbox. If the asset was synced to the sandbox account from the production account and then edited, those changes cannot be pushed back to production right now.
Only super admins in the production account are able to push changes back to production. Customers will see a new "production account" item on their sandboxes homepage and can start the sync back to production by clicking "Configure sync to production". This will require customers to confirm twice before a sync starts. Users must be in the production account in order to start a sync back to production.
@dennisedson can you make sure the status of this idea post changes to "In beta"? Thanks!
@MGan Is there any news as to whether the features in the beta will be implemented to all accounts? And what is the ETA on that? I have a client who is very interested in synching sandbox content to their production environment.
Adding to this requirement. Crazy in an enterprise environment that we cannot develop safely away from production. Does the Beta mean that something is there somewhere hidden away?
Please add this feature asap. We need to be able to safely develop and test in the Sandbox without having to do the same work twice to repeat it in production.
This is something our dev team has been asking for. We have to log any dev work we do in sandbox then export/import or manually put it into production when the test is complete. This is not how a sandbox works in other softwares. We need to be able to push properties/objects/workflows/etc to the production environment. (The "commit" feature, of course, would also throw errors if something was off)
@MGan does sunset mean the beta ended and you're implementing this or it means you couldn't get it to work in beta and the whole idea has been scrapped? Since it's been 8 months..
How is it possible that this functionality has been sunset? Not having it implies doing the work twice. Is there any information on whether it will be implemented in the future?
Adding my vote for this feature to be implemented, it does add risk to making complex changes to an existing environment - either you make them direct in PROD and hope for the best, or make them in Sandbox, test, hope you remember what they all were and reapply in Prod. Not great.
Adding my vote to this! This is definetely needed. We do a lot of integration and custom code testing in the test environment and moving it to production is an absolute pain. It requires a lot of time and modification when moving functioning code from test to production.
