How to download my application from another server or website in ServiceNow

[NaveenkumarM]

Hi all,
I created a custom application in ServiceNow and I want to download or export it from another server/instance.

How can I properly export or download my app (as update set or application file) and move it between instances?

Thanks.

[DGAJ]

Hi @NaveenkumarM ,

I believe you mean on a  PDI ?

To achieve this, You can connect your instance to github repository, then commit your update set to the repository- 

On your other instance, connect it to the repo and retrieve the update set.

Follow this article for guidance 

https://www.servicenow.com/community/developer-forum/how-to-link-servicenow-application-with-github/...

*******************************************************************************************
If my answer has helped with your question, please mark my answer as the accepted solution and give a thumbs up.

Best regards,

[Nayan ArchX]

Great question — this is exactly how ServiceNow intends apps to be moved, but the method depends on how the app was created and what you want to move.

Below is a clear, correct, step-by-step guide with best practices.

FIRST: Identify your application type

Go to Studio → Application Picker and check:

• Scoped Application → use Application Files
• Global / non-scoped work → use Update Sets

Do NOT rely on update sets alone for scoped apps

OPTION 1 (RECOMMENDED): Export a Scoped Application (Application File)

Best for:

• Custom apps built in Studio
• Moving apps between instances cleanly
• Versioning & reuse

Step-by-Step (Export)

1. Switch to your application scope
2. Go to:

3.  System Applications → Studio

1. Click File → Export Application
2. Choose:
   • Include demo data (optional)
   • Version (e.g., 1.0.0)
3. Download the .zip file

This ZIP is your application package.

Import on Target Instance

1. Go to: System Applications → Applications
2. Click Import Application
3. Upload the ZIP
4. Review preview
5. Install

✔️ Tables
✔️ Scripts
✔️ ACLs
✔️ UI elements
✔️ Dependencies

OPTION 2: Update Sets (NOT recommended for scoped apps)

Only use when:

• Fixing small changes
• Moving configs inside same environment
• App already installed

Why Update Sets Fail for Apps

• Miss role mappings
• Miss ACL conditions
• Miss sys_app records
• Cause scope issues

 

OPTION 3: Source Control (Advanced / Enterprise)

Best for:

• Teams
• CI/CD pipelines

Steps:

1. Link app to Git repository
2. Commit changes
3. Pull into target instance

This is the cleanest DevOps approach, but requires setup.

Common Mistakes to Avoid

❌ Exporting scoped app via update set
❌ Forgetting dependencies (plugins)
❌ Changing scope mid-development
❌ Installing app without previewing

 

Quick Decision Guide

Scenario	Method
Full custom app	Application Export (ZIP)
Small config fix	Update Set
Team / DevOps	Source Control

Pro Tip (Senior Dev Move)

Before export:

System Applications → Studio → Validate Application

Catches missing references before you break PROD.

If my response has resolved your query, please consider giving it a thumbs up ‌‌ and marking it as the correct answer‌‌!

Thanks

Nayan Patel

IT ServiceNow Consult, ServiceNow ArchX

If my response has resolved your query, please mark it Helpful by giving it a thumbs up and accept the solution

[Its_Azar]

Hi there @NaveenkumarM 

You can use Source Control for this — that’s how I usually move changes across instances.

Link your application to GitLab, set up the environments, and then simply commit your changes. Once committed, you can pull those changes into the target instance (for example, DEV → QA).

If you don’t want to use the GitLab approach, an alternative is to open the application and export the application file, then import it into the target instance.

Hope this helps 👍