Note: This article is on the new Sandbox 2.0 which is currently in Private Beta. For Freshservice's legacy Sandbox click here.

Regular Data Refresh: Periodically refresh your cloned instances with updated data from the production. This prevents data staleness and ensures that your testing remains relevant and effective. This can be achieved via config sets from the production to cloned instances.


Access Control: Implement strict access controls in the cloned instances to limit who can make changes and access sensitive data. 


Documentation: Maintain detailed documentation of configurations, customizations, and test results in the cloned environment. This documentation serves as a valuable reference for future development and troubleshooting.


User Training: Use the cloned environment for user training and onboarding. It provides a risk-free space for users to familiarize themselves with new features and functionalities.


Communication: Maintain clear communication channels between developers, testers, and other stakeholders using the cloned instance. Ensure that everyone is aware of changes and testing schedules to minimize disruptions.


Feedback Loop: Encourage feedback from users and testers in the cloned environment. Their insights can help uncover usability issues and fine-tune features before they are made live.


Delete unused clones: When no longer needed, delete unused clones to conserve resources and reduce potential security risks. Once deleted, all data in that clone is deleted and cannot be revived.