> For the complete documentation index, see [llms.txt](https://docs.pharos.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pharos.ai/configuration-guide/advanced/import-export-rules.md).

# Import / Export Rules

Export Pharos configuration rules to a file and import them into another org to move setup between sandbox and production or replicate it across orgs.

Moving configuration from sandbox to production—or replicating setup across multiple orgs—used to mean manual recreation. **Import / Export Rules** lets you export selected rules from one org to a file and import them into another, turning hours of reconfiguration into a few clicks.

***

## Accessing Import / Export

Navigate to **Pharos App → Pharos Admin → Import / Export Rules**. The landing page presents a **Rules Management** screen where you choose an operation—**Import Rules** (upload a file) or **Export Rules** (download selected rules).

![Import / Export Rules landing page — Rules Management with Import Rules (Upload Files / drop zone) and Export Rules (Export button)](https://4264222071-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fdl9tmJ56lvwg5XY63QYr%2Fuploads%2Fgit-blob-cebc55509a9a3bcc40860a7057aa0559a57a1c2d%2Fimport-export-landing.png?alt=media)

***

## Exporting Rules

Click **Export** on the Export Rules row to open the **Select rules to export** list. Every configured rule is shown with its rule type, name, target object, action, creator, and active state.

![Select rules to export — searchable table of rules with columns for Rule, Name, Object, Action, Created By, and Active](https://4264222071-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fdl9tmJ56lvwg5XY63QYr%2Fuploads%2Fgit-blob-dbceb6334ada2cb83dc6891c2daf241c75dfbeea%2Fimport-export-select-rules.png?alt=media)

### Narrow the List

Use **Search** to find rules by name, or **Filters** to narrow by category. Filters cover:

* **Active only** — hide inactive rules.
* **Rule** — including Monitoring, Archival, Notification, Masking, Event Monitoring, and Ticketing (not an exhaustive list).
* **Object** — Log, Issue, Trace Result.
* **Operation** — Create, Update.

![Filters panel — Active only toggle, and checkbox groups for Rule, Object, and Operation](https://4264222071-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fdl9tmJ56lvwg5XY63QYr%2Fuploads%2Fgit-blob-0e9ce4727710e91699e0fbe7f42767fbeca4b709%2Fimport-export-filters.png?alt=media)

### Select and Export

Tick the checkbox on each rule you want, or use the header checkbox to select the whole (filtered) list. A running count—for example, **5 of 29 selected**—and a selection bar confirm your choices. Click **Export** to download the rules as a JSON file.

![Rules table with five rules selected, a "5 items selected" bar, and the Export button active](https://4264222071-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fdl9tmJ56lvwg5XY63QYr%2Fuploads%2Fgit-blob-cd8558d77ebe8faeba599f3ee0c4b4671677390f%2Fimport-export-selected.png?alt=media)

The browser downloads an `exported-rules.json` file containing the selected rules.

![Browser Recent Download History showing exported-rules.json, 12.5 KB, Done](https://4264222071-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fdl9tmJ56lvwg5XY63QYr%2Fuploads%2Fgit-blob-53a2a17338653edffb51d38f5c9795d19e31fdae%2Fimport-export-download.png?alt=media)

***

## Importing Rules

On the Rules Management screen, use the **Import Rules** row: click **Upload Files** and choose a previously exported file, or drag the file onto the **Or drop files here** zone. Import runs immediately—there's no preview or conflict-resolution step—and a green success toast confirms when the rules have been added to the target org.

{% hint style="warning" %}
**Org-specific values don't transfer cleanly.** Slack/Teams channel IDs, Jira project keys, and integration credentials are specific to each org. After importing, open the affected rules in the target org and update these values.
{% endhint %}

***

## Best Practices

| Practice                                | Reason                                                                        |
| --------------------------------------- | ----------------------------------------------------------------------------- |
| Export from sandbox first               | Validate the imported setup in a non-production org before production         |
| Use filters to scope the export         | Export only the rules you intend to move, rather than the entire set          |
| Review org-specific values after import | Channel IDs, project keys, and credentials differ per org and must be updated |
| Keep the export file                    | Note the source org, date, and which rules were included for traceability     |

***

## Related

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>🔔 Notifications</strong></td><td>Notification rule configuration</td><td><a href="https://docs.pharos.ai/configuration-guide/notifications.md">Notifications</a></td></tr><tr><td><strong>📐 Ticketing</strong></td><td>Ticketing rule configuration</td><td><a href="https://docs.pharos.ai/configuration-guide/ticketing/rules.md">Rules</a></td></tr><tr><td><strong>📈 Monitoring</strong></td><td>Monitoring rule configuration</td><td><a href="https://docs.pharos.ai/configuration-guide/monitoring.md">Monitoring</a></td></tr><tr><td><strong>🔗 Connected Orgs</strong></td><td>Multi-org log flow</td><td><a href="https://docs.pharos.ai/configuration-guide/connected-orgs.md">Connected Orgs</a></td></tr></tbody></table>
