> For the complete documentation index, see [llms.txt](https://docs.forgappify.com/field-rules/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.forgappify.com/field-rules/jira-administrator/import-and-export.md).

# Import and export

Export a UI Modification to a file to back it up or move it, and import it into the same or another Jira site.

Export a UI Modification (UIM) to a file, and import that file later on the same site or on a different one. Use it to:

* **Back up** a UIM before making large changes, and restore it if needed.
* **Move a configuration between sites**, for example from a sandbox or test site to production.
* **Reuse a configuration** on another site without rebuilding it rule by rule.

***

## Exporting a UI Modification

{% stepper %}
{% step %}

### Open the UIM list

Open the Field Rules configuration page. Every UIM is listed in the table.
{% endstep %}

{% step %}

### Choose Export

Open the **...** menu at the end of the UIM's row and click **Export**.
{% endstep %}

{% step %}

### Save the file

A JSON file named after the UIM is downloaded. It contains the UIM's name, description, contexts, and all of its rules and preconditions.
{% endstep %}
{% endstepper %}

***

## Importing a UI Modification

{% stepper %}
{% step %}

### Choose Import

On the Field Rules configuration page, open the **...** menu at the top and click **Import UI Modification**.
{% endstep %}

{% step %}

### Select the file

Pick a file exported from Field Rules. The app checks it and opens the UIM in the editor, pre-filled with the exported configuration.
{% endstep %}

{% step %}

### Review and resolve

Go through any notices shown at the top of the editor. If the app needs your input, a **Resolve references** section is shown. See the next section.
{% endstep %}

{% step %}

### Save

Review the name, contexts, and rules, adjust anything you need, and click **Import**. The imported UIM is added to your list.
{% endstep %}
{% endstepper %}

{% hint style="info" %}
Imported rules are added as a new UIM. Nothing is changed in your existing UIMs unless you choose to update one (see below).
{% endhint %}

***

## Why you may be asked to resolve items

A UIM refers to things that exist on your Jira site, such as spaces, work types, fields, groups, statuses, and request types. Every Jira site identifies these with its own internal identifiers, so the same space or field has a different identifier on two different sites.

When you import, Field Rules matches the items in the file to the items on your site automatically wherever it can. Anything it cannot match with confidence is left for you to decide.

For each unmatched item you can:

* **Pick a replacement** from your site, or
* **Remove it** from the rules that use it.

Once every item is decided, click **Accept** to apply your choices and continue. The more closely the two sites are set up alike (same names for spaces, fields, groups, and so on), the fewer items you will need to resolve.

{% hint style="warning" %}
Review the result before saving. Removing a reference can change when a rule applies, so check the affected rules and contexts.
{% endhint %}

***

## Importing into the same site

If you import a file exported from the same site, and the UIM it came from still exists, you are asked how to save it:

* **Create new** - adds the imported configuration as an additional UIM.
* **Update existing** - replaces the current configuration of the original UIM with the imported one. This cannot be undone.

This makes it easy to restore a UIM from a backup.

***

## Good to know

* The export file contains the UIM configuration only. Work item content and user profile details are not included.
* Only files exported from Field Rules can be imported. A file exported from a newer version of the app may need the app to be updated first.
* Each site can hold a limited number of UIMs. If the limit is reached, delete one before importing.