# Staging Environment / Development Version **URL:** \ **Category:** HubSpot Ideas\ **Tags:** design-manager\ **Created:** [January 4, 2023, 12:52pm UTC](https://community.hubspot.com/t/staging-environment-development-version/72179 "2023-01-04T12:52:26Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![mariana\_pic](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/mariana_pic/32/66297_2.png) [@mariana\_pic](https://community.hubspot.com/u/mariana_pic)\ **Post date:** [January 4, 2023, 12:52pm UTC](https://community.hubspot.com/t/staging-environment-development-version/72179/1 "2023-01-04T12:52:26Z")
The CMS has evolved into a great tool. However compared to our Wordpress or Shopify website builds, we cannot provide our clients with a staging version to fully test major changes. It is easy to proof a page or a module. But if you are launching a multi-page section that should be tested in the full website environment, good luck. Content staging is very useful, but its not a full staging environment. You cannot test changes in global modules, navigation, ETC. The sandbox in enterprise doesn’t copy everything. So it would take a lot of time and manual work to do a clone and keep it updated for the client to test. We definetly NEED a good test environment where we could test the whole website with those changes in an more efficient way. I’d love confirmation that this is on the roadmap for at least Enterprise and hopefully CMS Pro as well. ---
**Author:** ![EYount](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/eyount/32/49393_2.png) [@EYount](https://community.hubspot.com/u/EYount)\ **Post date:** [May 5, 2023, 5:25pm UTC](https://community.hubspot.com/t/staging-environment-development-version/72179/2 "2023-05-05T17:25:13Z")
Yes! Having a dedicated staging environment solution would solve a lot of problems, reduce friction points, and make many Growth Driven Design projects run a lot smoother for our clients! This is a much needed addition. ---
**Author:** ![Hanley](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/hanley/32/198446_2.png) [@Hanley](https://community.hubspot.com/u/Hanley)\ **Post date:** [May 6, 2023, 8:26am UTC](https://community.hubspot.com/t/staging-environment-development-version/72179/3 "2023-05-06T08:26:49Z")
I don’t use the CMS feature yet but this sounds like a good thing to have, I use prismic and this offers the different environments but it’s too costly to use so HubSpot CMS I am definitely going to look into. ---
**Author:** ![Thijs1](https://avatars.discourse-cdn.com/v4/letter/t/839c29/32.png) [@Thijs1](https://community.hubspot.com/u/Thijs1)\ **Post date:** [December 12, 2023, 1:14pm UTC](https://community.hubspot.com/t/staging-environment-development-version/72179/4 "2023-12-12T13:14:55Z")
I agree this is crucial in website building, especially when changing multiple pages and links between them ---
**Author:** ![rebeccatravels](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/rebeccatravels/32/87209_2.png) [@rebeccatravels](https://community.hubspot.com/u/rebeccatravels)\ **Post date:** [December 22, 2023, 2:37pm UTC](https://community.hubspot.com/t/staging-environment-development-version/72179/5 "2023-12-22T14:37:10Z")
This is so simple in Wordpress and is incredibly, embarassingly painful to reproduce in HubSpot. Wanting to use some custom css in the nav, and no simple way to have a staging environment to do so is a huge risk and the solutions offered by support are painful and time consuming. I’m a partner and I genuinely wish my client was using Wordpress because this would have been painless and easy. ---
**Author:** ![apcognigy](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/apcognigy/32/39019_2.png) [@apcognigy](https://community.hubspot.com/u/apcognigy)\ **Post date:** [January 5, 2024, 11:41am UTC](https://community.hubspot.com/t/staging-environment-development-version/72179/6 "2024-01-05T11:41:22Z")
It would be nice if we could easily at least use API, where we could **Export the pages with everything** and then **Import in the sandbox** - - having to upload files manually is not the issue, mapping images could be manual work to “search-replace” in exported JSON - - multilingual can be also manual step, as even current “content staging” isn’t working with Multilingual ---
**Author:** ![sashashev](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/sashashev/32/195869_2.png) [@sashashev](https://community.hubspot.com/u/sashashev)\ **Post date:** [March 26, 2024, 12:54am UTC](https://community.hubspot.com/t/staging-environment-development-version/72179/7 "2024-03-26T00:54:14Z")
This feature is a must. We have been building websites for over 20 years and are wanting to leverage HubSpot cms but this is a deal breaker for so many projects. Large projects wont work without this