---
title: Import application or application-customization from source control
description: Import an app or app customization from a source control repository into App Engine Studio \(AES\) to continue developing it on this instance.
locale: en-US
canonical_url: https://www.servicenow.com/docs/r/australia/application-development/app-engine-studio/source-control-import.html
release: australia
product: App Engine Studio
classification: app-engine-studio
topic_type: task
last_updated: "2026-03-12"
reading_time_minutes: 2
breadcrumb: [Use AES with a Git source control repository, Build, App Engine Studio, Building low-code applications, Developing your application, Building applications]
---

# Import application or application-customization from source control

Import an app or app customization from a source control repository into App Engine Studio \(AES\) to continue developing it on this instance.

## Before you begin

-   Role required: admin
-   Verify that the non-production instance has network access to the Git repository.
-   Verify that the repository contains a valid application.
-   Ensure that users add the email address to their respective Users table \[sys\_user\] record that they use in their commits to the Git repository.
-   Learn more about application-customizations [Manage customizations to applications](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/application-development/application-repository-self-hosted/manage-customizations-store-apps.md).

## About this task

The source control integration does not support importing an application on a production instance. Instead install applications on a production instance from the application repository, an update set, or the App Engine Studio.

## Procedure

1.  Navigate to **All** > **App Engine** > **App Engine Studio**.

2.  Select **Import app**.

    \[Omitted image "source-control-import-form-purple.png"\] Alt text: Import an app from source control into App Engine Studio

3.  On the form, fill in the fields.

<table id="table_skj_zxl_s5"><thead><tr><th>

Field

</th><th>

Description

</th></tr></thead><tbody><tr><td>

Network protocol

</td><td>

Https or ssh credential type that enables secure channel data exchange.

</td></tr><tr><td>

URL

</td><td>

The URL to the Git repository where the application files reside. **Note:** If the Git repo URL for SSH provided by your Git server does not work, check with your Git server owner or provider for the correct URL. There may be additional specifications such as scheme protocol prefixes, port numbers, and so on, required for your Git repo URL to function.

</td></tr><tr><td>

Branch

</td><td>

The repository branch to work on within the application. **Note:**

The default branch is named after your instance. If you do not choose a name, the branch defaults to **master**.

</td></tr><tr><td>

MID Server Name

</td><td>

Select an existing MID Server to link to a Git repository stored behind your corporate firewall.**Note:** Use a separate MID Server to prevent conflicts with Discovery activities.

See [MID Server](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/servicenow-platform/mid-server-landing.md) for more information.

</td></tr><tr><td>

Default email

</td><td>

The committer email address is defined by the sys\_user record if available. But if a committer's sys\_user record email field is empty, the system generates an alternate email \(username@instancename.service-now.com\). You can also enter a default email address and change it later. To use that default email address in all cases, select the check box.

</td></tr><tr><td>

Credential

</td><td>

Select the credential for your Git repository. For more information, see [Getting started with Credentials](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/platform-security/credentials-getting-started.md).**Note:** If you select the ssh network protocol, enter a valid credential of the SSH Private Key type. If you select the https protocol, enter a valid credential of the Basic Auth Credentials type.

</td></tr></tbody>
</table>    **Note:** All application developers on the instance share the credential used to link a Git repository to an application.

4.  Select **Import app**.

    The system compares the checksum in the `checksum.txt` file to current checksum. When the checksum values match, the integration skips validation and imports the application. When the checksum values do not match, the integration first validates and sanitizes the application files before importing them.

5.  Select **Select Application**.

    App Engine Studio displays the application as a new choice in the Switch Applications window.


## What to do next

-   Review the upgrade logs for any sanitization applied to application files during the import.
-   Select the imported application to edit it.

**Parent Topic:**[Use AES with a Git source control repository](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/application-development/app-engine-studio/aes-source-control-use.md)

**Related topics**  


[MID Server](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/servicenow-platform/mid-server-landing.md)

[Getting started with credentials](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/platform-security/credentials-getting-started.md)