...
Production - use this name for your live store site which contains all finished and approved codes/data. This is the default system name and cannot be changed/altered to any other value
Staging - use this name for your pre-deployment site that is setup to mimic your live site configurations and used for your smoke tests before deployment to ‘Production'
UAT - use this name for your site configured to run as a production build with a separate database. Used by clients to check that feature requests are working as expected before deployment to ‘Staging’
Integration - use this name for your site configured for system integration tests and checks for functional/non-functional elements before deployment to ‘UAT’.
You can also label your integration environments with numeric values, e.g. Integration 1, Integration 2
...
Integration1, Integration2
Screenshot provided for ease of reference.
IMPORTANT!
As an additional best practice, it is highly recommended to test migrations first to non-Production environments. This helps you to gain a better understanding of StagingPro’s functionality, while safely launching/reviewing your test migrations.
Only after comprehensive testing and proper validation in non-Production environments, should you migrate data to a live Production environment.
...
To view our onboarding steps, please access the following article → StagingPro Onboarding