# multiple environments (staging, development, production)

**URL:** <https://community.hubspot.com/t/multiple-environments-staging-development-production/23413>\
**Category:** APIs & Integrations\
**Tags:** workflows\
**Created:** [July 27, 2020, 11:09am UTC](https://community.hubspot.com/t/multiple-environments-staging-development-production/23413 "2020-07-27T11:09:16Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![WendyGoh](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/wendygoh/32/42320_2.png) [@WendyGoh](https://community.hubspot.com/u/WendyGoh)\
**Post date:** [July 28, 2020, 6:53am UTC](https://community.hubspot.com/t/multiple-environments-staging-development-production/23413/2 "2020-07-28T06:53:00Z")

</div>

Hey @tomas1,

Currently, while we do not have a sandbox environment in which the data replicates the real environment data, the test account that you mentioned is the best workaround.

[Test portals](https://legacydocs.hubspot.com/docs/faq/how-do-i-create-a-test-account) created from the developer account would also have access to the CRM tool, so if you’re looking for a completely separate environment, you could use a test portal to create dummy CRM data.

---

_[View the full topic](https://community.hubspot.com/t/multiple-environments-staging-development-production/23413)._
