# Packager Feature Guide

## Welcome <a href="#welcome" id="welcome"></a>

We are very pleased to be demonstrating this exciting feature in **Unifi** which makes moving Integrations between instances simpler and easier than ever.

## Scope <a href="#scope" id="scope"></a>

This document will guide you through the Packager feature. It will demonstrate how straightforward and efficient the task of moving your Integration can be.

Prior to the release of this feature we recommended that you build your Integration in its own Global Application in order to facilitate moving integrations between instances as efficiently as possible. This was the best method available using OOTB native ServiceNow functionality.

As good as that method was, there were issues to overcome when migrating integrations that belong to the same Process. There are a few records which are shared by multiple integrations (Trigger Business Rule, Web Service & Process - *one per Process*) and so the application/integration being migrated may or may not contain one or more of those records - depending on which application scope they were configured in. They may have had to be migrated separately.

This feature solves that problem. The Packager will pull together all of the relevant records and place them in an Update Set ready for migration.

{% hint style="info" %}
**NOTE**: The ServiceNow System Administrator (admin) role is required to see the automatic download and to view updates in the Update Set.
{% endhint %}

## Approach <a href="#approach" id="approach"></a>

We will demonstrate packaging the Integration configured in the Bidirectional Incident Guide so that it’s available to import to another instance.