--- sourceDocument: Yokohama ServiceNow AI Platform Administration sourceDocumentLink: https://www.servicenow.com/docs/r/yokohama/platform-administration Release : - yokohama ft:locale : - en-US ft:publication_title : - Yokohama ServiceNow AI Platform Administration ft:clusterId : - platadm bundleId : - platadm workflow : - Platform --- # Request a clone # Request a clone {#ariaid-title1} * Release version: Yokohama * * Updated September 12, 2025 * * ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 4 minutes to read Request a clone to copy data from a production instance to a non-production instance or to copy data between non-production instances. ## Before you begin Role required: `clone_admin` on the source instance; `clone_admin` and `soap` on the target instance. ## Procedure 1. Navigate to AllClone Admin ConsoleRequest Clone. 2. On the form, fill in the fields. {#t_StartAClone__table_ujp_cdf_gxb__entry__2} | Field | Description | |-|-| | Source instance | The original database where data is copied from. | | Target instance | The new location where the data is copied to. Note: You can add an instance or select an existing instance without leaving the page. | | Clone Profile | Apply a clone profile that you created previously. All exclusions, preservers, and scripts you added to the profile are applied to the clone request. If clone profile is left empty the system will pull in all available preservers, exclusions and cleanup scripts Note: If default is checked on the clone profile, the clone request loads this profile every time you open the clone request page. | | Lock settings at the time of clone request | If you use a clone profile, this option locks the settings and options at the time of the clone request. Any subsequent changes to the clone profile, regardless of when the clone runs, don't affect the clone request. | | Clone Scheduled Start time | The start time to begin cloning your instance. See [Schedule recurring clones (legacy)](https://www.servicenow.com/docs/OpqB1lN5gyMrjHtO7Thd8g "Schedule recurring clones to keep your cloned instances up to date."). | | * Email updates about this clone * External email address {#t_StartAClone__ul_qg5_jfw_sgc} | The email or emails to be notified of the clone process and clone completion. | [Table 1. Clone request form] {#t_StartAClone__table_ujp_cdf_gxb} {#t_StartAClone__step_pq5_rsf_cgc} {#t_StartAClone__step_pq5_rsf_cgc} 3. Select the hyperlinked number under each item in the definitions section to review your exclusions, preservers, and cleanup scripts. 4. Select the options to configure for your clone. Note: For information on all available options see [Clone options](https://www.servicenow.com/docs/CRsir~wUlMDEVHwkPx3~uw "A reference topic that contains various configurations for your data when requesting a clone."). For information on general guidelines to expedite your clone request see [General guidelines for optimizing your clone duration](https://www.servicenow.com/docs/2D2K5NojIY2eTlmT04YsmA "A reference topic that includes general guidelines to optimize your clone duration when requesting a clone."). 5. Select Continue. 6. Review your clone request summary and select Confirm and Submit Clone Request. ## Request a clone (legacy) {#ariaid-title2} Request a clone to copy data from a production instance to a non-production instance or to copy data between non-production instances. ### Before you begin Role required: clone_admin Starting with the Australia release, clone requests are no longer deployed, enhanced, or supported on the legacy page. Requests that are initiated via the legacy page `clone_instance.do` don't show up on the new clone console home page. However, they can still be found on the legacy clone history page `clone_instance_list.do`. Note: Configure your target instance before requesting your clone. See [Register target instance (legacy)](https://www.servicenow.com/docs/6HzmuIEdZKvbdkGE7P6QWw "A clone target record specifies the instance URL and credentials used for cloning."). Configure a clone profile. See [Create a custom clone profile](https://www.servicenow.com/docs/EHLOPXNTD81NaooRt9ltuQ "Clone profiles act as reusable clone templates to establish consistent clone outcomes. Clone profiles enable you to set up exclusions, preservers, and cleanup scripts for specific clone scenarios."). For self-hosted customer instances that use an Oracle database, see [https://support.servicenow.com/kb?id=kb_article_view\&sysparm_article=KB0563847](https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0563847). ### About this task The ServiceNow AI Platform uses data from the most recent, daily backup of the source instance when cloning. Backups that are used for cloning are a maximum of 36 hours old. The initial preparation begins, including selecting the latest backup to use, only at the date and time processing is scheduled to start. ### Procedure 1. Log in to the instance that you want to clone. This instance becomes the source instance of the clone request. 2. Configure a [Register target instance (legacy)](https://www.servicenow.com/docs/6HzmuIEdZKvbdkGE7P6QWw "A clone target record specifies the instance URL and credentials used for cloning.") record for each target instance that you want to receive clone data. 3. Verify the list of tables that are excluded from cloning and [add or remove tables to exclude](https://www.servicenow.com/docs/6UhmJbldWWgU~6f573P~yw "Exclude a legacy table on the target instance from being overwritten from the source instance.") from the target instance. 4. Verify the list of tables and system properties that you want saved on the target instance with the following. 5. Navigate to Instance cloneRequest Clone. 6. **Optional:** Specify a predefined clone profile. A clone profile stores target and clone options. The clone profile automatically populates your clone request with your selected profile settings. See [clone profiles for clone requests](https://www.servicenow.com/docs/v7tcAn3OjyiFaha4lyroXQ "Clone profiles enable you to set up exclusions, preservers, and cleanup scripts for specific clone scenarios."). 7. In the Target instance field, select the target instance that you want to receive the cloned data. Create a separate clone request for each target instance that you want to receive clone data. 8. In the Clone Scheduled Start Time field, select the time that you want the cloning to start. You can schedule multiple clone requests for the same source instance. For example, create a clone request to copy data to non-production instance A and another clone request to copy data to non-production instance B. The scheduling engine determines whether multiple clone requests against the same source instance can occur simultaneously or whether they must occur sequentially. If your source instance is large, see clone chaining on [Exploring Instance Clone](https://www.servicenow.com/docs/FWmv8Y4_ncGhmCCwcpNooQ#exploring-instance-clone "Explore how to use a clone to copy everything in a database from one instance to another."). The system verifies the scheduled start time and either accepts the date-time value that you selected or suggests an available date-time value. The validation process helps prevent scheduling conflicts with other automations using the same target instance. 9. In the Email upon completion field, enter your email address so that you can receive alerts after the cloning finishes, is canceled, or has an error. 10. Select the Options arrowhead so that it turns downward. 11. Fill in your options. 12. Select Submit. If there are no issues with the clone request, the system displays the Authenticate Target modal. 13. Enter the user name and password for an administrator account on the target instance and then select Authenticate. 14. Review the clone settings and select OK. An email is sent to the supplied address after the clone finishes, is canceled, or has an error. {#t_StartAClone_legacy__steps_xtb_bnm_zx} ### What to do next * [Schedule recurring clones](https://www.servicenow.com/docs/OpqB1lN5gyMrjHtO7Thd8g "Schedule recurring clones to keep your cloned instances up to date."). * [Cancel your clone request](https://www.servicenow.com/docs/uo0WZ2ZHglNuS4OLM8vkDg#cancel-clone "You can cancel a clone that is scheduled, requested, or in progress until the Node Repoint state. Canceling a clone retains the target instance as-is in its pre-clone state with its original data."). * [View the clone history](https://www.servicenow.com/docs/lpVwl3BcAWiOPOB_ICPPCQ "You can view the status and history of any instance clone request.") of completed clones. {#t_StartAClone_legacy__ul_gmy_t5s_fhb} *[\>]: and then