a new catalog item ccopy the item from sandBOX TO DEV INSTANCE

[nenavathsur]

how to copy the catalog item from sandbox to dev instance in servicenow

please steps to copy or export

[sachinvic · Accepted solution]

@nenavathsur 

If this is a catalog item you created/customized in the Sandbox and want to move to Dev, the preferred approach is to use an Update Set.

Basic steps:

1. In the Sandbox, create/select an Update Set and make it current.
2. Open the Catalog Item and make sure the required changes are captured in the Update Set. You can use Add to Update Set where applicable.
3. Complete the Update Set.
4. Move it to the Dev instance using Retrieve Update Set or export the completed Update Set as XML and import it into Dev.
5. In Dev, open Retrieved Update Sets, preview the Update Set, resolve any conflicts, and then commit it.
6. Validate the Catalog Item and its related configuration such as variables, Catalog Client Scripts, UI Policies, flows/workflows, and catalog/category mappings.

For a simple catalog item, this is generally cleaner than manually exporting individual records. Also make sure any dependencies that are not captured by the Update Set are handled separately.

Helpful? Please mark the response as Accepted Solution ✅ and close the thread 🔒 — this helps future readers find the solution faster.

Regards,
Sachinvic
✨ ArchX Certified | ✨ 16x ServiceNow AI MVP

[Tanushree Maiti · Accepted solution]

Hi @nenavathsur 

Here Copy means do you want to create a duplicate of catalog item OR do you want to move catalog item from sandbox to Dev

If it is movement of catalog from sandbox to Dev then follow these steps: 

Step 1: Create and Set a Current Update Set in Sandbox

• Log in to your sandbox instance.
• In the Application Navigator, search for Update Sets (System Update Sets > Local Update Sets).
• Click New to create a new update set and set its state to In Progress.
• Right-click the header or use Make Current to make this new update set active so all subsequent actions are captured here.

Step 2: Capture the Catalog Item and Related Records

• Navigate to Service Catalog > Catalog Definitions > Maintain Items
• Open the specific catalog item you want to move.
• Do minor edit and save it.
• Ensure the item and its dependent components (such as variables, variable sets, client scripts, script include and UI policies etc) are added into update set:
• Mark the update set state to Complete once you are done capturing everything.

Step 3: Export the Update Set from Sandbox  (Or using Update Source – you can move – this one I prefer for better tracking)

• Go to System Update Sets > Local Update Sets in your sandbox instance.
• Open your completed update set .
• Under Related Links, click Export to XML. Save the XML file to your computer.

Step 4: Import and Commit in Dev Instance

• Log in to your target dev instance.
• Navigate to System Update Sets > Retrieved Update Sets.
• Click Import Update Set from XML
• Once the uploaded update set appears in the list, open it.
• Click Preview Update Set to check for any missing dependencies or collision errors.
• Resolve any potential conflicts if flagged, and then click Commit Update Set.

[sachinvic · Accepted solution]

@nenavathsur 

If this is a catalog item you created/customized in the Sandbox and want to move to Dev, the preferred approach is to use an Update Set.

Basic steps:

1. In the Sandbox, create/select an Update Set and make it current.
2. Open the Catalog Item and make sure the required changes are captured in the Update Set. You can use Add to Update Set where applicable.
3. Complete the Update Set.
4. Move it to the Dev instance using Retrieve Update Set or export the completed Update Set as XML and import it into Dev.
5. In Dev, open Retrieved Update Sets, preview the Update Set, resolve any conflicts, and then commit it.
6. Validate the Catalog Item and its related configuration such as variables, Catalog Client Scripts, UI Policies, flows/workflows, and catalog/category mappings.

For a simple catalog item, this is generally cleaner than manually exporting individual records. Also make sure any dependencies that are not captured by the Update Set are handled separately.

Helpful? Please mark the response as Accepted Solution ✅ and close the thread 🔒 — this helps future readers find the solution faster.

Regards,
Sachinvic
✨ ArchX Certified | ✨ 16x ServiceNow AI MVP

[nenavathsur · Accepted solution]

also workable thank you @sachinvic 

[Tanushree Maiti · Accepted solution]

Hi @nenavathsur 

Here Copy means do you want to create a duplicate of catalog item OR do you want to move catalog item from sandbox to Dev

If it is movement of catalog from sandbox to Dev then follow these steps: 

Step 1: Create and Set a Current Update Set in Sandbox

• Log in to your sandbox instance.
• In the Application Navigator, search for Update Sets (System Update Sets > Local Update Sets).
• Click New to create a new update set and set its state to In Progress.
• Right-click the header or use Make Current to make this new update set active so all subsequent actions are captured here.

Step 2: Capture the Catalog Item and Related Records

• Navigate to Service Catalog > Catalog Definitions > Maintain Items
• Open the specific catalog item you want to move.
• Do minor edit and save it.
• Ensure the item and its dependent components (such as variables, variable sets, client scripts, script include and UI policies etc) are added into update set:
• Mark the update set state to Complete once you are done capturing everything.

Step 3: Export the Update Set from Sandbox  (Or using Update Source – you can move – this one I prefer for better tracking)

• Go to System Update Sets > Local Update Sets in your sandbox instance.
• Open your completed update set .
• Under Related Links, click Export to XML. Save the XML file to your computer.

Step 4: Import and Commit in Dev Instance

• Log in to your target dev instance.
• Navigate to System Update Sets > Retrieved Update Sets.
• Click Import Update Set from XML
• Once the uploaded update set appears in the list, open it.
• Click Preview Update Set to check for any missing dependencies or collision errors.
• Resolve any potential conflicts if flagged, and then click Commit Update Set.

[nenavathsur]

thank you @Tanushree Maiti  for your perfect solution here🙂