ServiceNow Instance Cloning: Complete Guide to Clone Dev from Production
This guide explains the complete process of cloning a Development (DEV) instance from a Production (PROD) instance in ServiceNow. Instance cloning is an essential administrative activity that ensures lower environments mirror production configurations, enabling realistic development and testing.
1. What is Instance Cloning?
Instance cloning is the process of copying the database and application files from one ServiceNow instance to another. Most organizations periodically clone Production into lower environments such as Development or Testing so developers can work with real configurations and data.
Instance Clone Architecture
2. Why Do Organizations Perform Instance Cloning?
- Ensure development environments reflect the latest production configuration
- Allow realistic testing with production‑like data
- Troubleshoot issues that occur only in production
- Refresh outdated development or testing environments
3. Important Precautions Before Cloning
Before initiating a clone operation, administrators must take several precautions to avoid data loss or unintended integrations.
- Notify all developers and users about the clone schedule
- Backup update sets and development work
- Disable or pause integrations with external systems
- Preserve instance‑specific records such as credentials
- Ensure no critical development work is being performed
4. Steps to Clone Dev Instance from Production
Step 1: Navigate to Clone Management
Log in to the Production instance with admin access. In the Application Navigator search for 'System Clone → Clone Management'. This module allows administrators to create and manage instance cloning requests. Click 'Create Clone' to begin.
Step 2: Create a Clone Request
After clicking 'Create Clone', the Clone Request form will appear. Configure the following:
- Source Instance: Production
- Target Instance: Development
Note: The Development instance data will be completely overwritten during cloning.
Step 3: Configure Clone Options
Before submitting the request configure additional options if required.
- Use Data Preservers to retain environment‑specific records such as credentials
- Exclude certain tables if they should not be cloned
- Schedule the clone during non‑business hours to avoid disruption
Step 4: Submit the Clone Request
Click 'Submit Clone' to start the process. ServiceNow validates the request, creates a snapshot of the Production database, transfers the data to the Development instance, and overwrites the target database.
You can monitor the clone progress under: System Clone → Clone History.
Clone Lifecycle
5. Post Clone Activities
After cloning completes, several administrative actions must be performed to ensure the development instance does not interact with production systems.
- Disable outbound email notifications
- Disable or reconfigure integrations
- Verify user roles and admin access
- Disable scheduled jobs or background processes
- Perform functional testing of key applications
6. Best Practices
- Perform instance cloning regularly to keep environments aligned
- Communicate clone schedules to all stakeholders
- Use data preservers to protect critical instance‑specific records
- Always verify integrations after cloning
- Conduct smoke testing after clone completion
Conclusion
Instance cloning is a powerful capability in ServiceNow that helps organizations maintain consistency across environments. By following the precautions, cloning steps, and post‑clone activities described in this guide, administrators can safely refresh development environments while minimizing operational risks.
