Join the #BuildWithBuildAgent Challenge! Get recognized, earn exclusive swag, and inspire the ServiceNow Community with what you can build using Build Agent.  Join the Challenge.

Production Vs Dev Instance for Brand new ServiceNow customer

FalakK
Tera Contributor

Is it recommended to build In Prod instance for a first time ServiceNow customers and then push changes into lower instances or follow a typical implementation path of Dev>Test>Prod? What's ServiceNow best practice recommendation is in this regard? 

 

3 REPLIES 3

Alessandro Alme
Giga Guru

Hello @FalakK.

 

According Platform Implementation training and Now Create methodology (workstream Design, build and unit test > Deploy code to Test Environment and Go-Live Transition processes, the best practice is typical implementation path: Dev > ... > Prod.

 

Screenshot 2025-03-14 17.43.56.png

 

Thanks,

Alessandro.

Dr Atul G- LNG
Tera Patron
Tera Patron

Hi @FalakK 

As per best practices and standard procedures, development should always begin in the Dev environment, followed by testing in Test/UAT, and then deployment to Production. However, if cloning is required, Dev and Test should be cloned from Production while maintaining the deployment flow as Dev → Test → Prod.

*************************************************************************************************************
If my response proves useful, please indicate its helpfulness by selecting " Accept as Solution" and " Helpful." This action benefits both the community and me.

Regards
Dr. Atul G. - Learn N Grow Together
ServiceNow Techno - Functional Trainer
LinkedIn: https://www.linkedin.com/in/dratulgrover
YouTube: https://www.youtube.com/@LearnNGrowTogetherwithAtulG
Topmate: https://topmate.io/atul_grover_lng [ Connect for 1-1 Session]

****************************************************************************************************************

Sandeep Rajput
Tera Patron
Tera Patron

@FalakK As suggested by others, make sure to follow Dev >Test>Prod cycle. Try to keep your prod instance untouched till everything gets finalised on Dev and the process/feature implementation is reviewed by the quality assurance teams. Make sure to capture your configurations/customisations in form of update sets, track their sequences and ultimately deploy the QA approved processes on prod.