> ## Documentation Index
> Fetch the complete documentation index at: https://codebeans-payment-rules-pro.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

# Import and export

> Move rules between stores as JSON — and what does not travel with them.

Rules move between stores as JSON files.

## Exporting

**… → Export customization** on any row in the customizations list. The rule downloads as a JSON file containing its conditions, operations, payment method selections, and per-method settings.

Export one rule at a time; there is no bulk export.

## Importing

**Import customization**, top right of the customizations list.

![The import dialog](https://mintcdn.com/codebeans-payment-rules-pro/0guf-DxrSbw6Ls57/images/import-modal.png?fit=max\&auto=format\&n=0guf-DxrSbw6Ls57\&q=85\&s=62aed220c5f5c501ff4b3f425176d5aa)

The dialog accepts a single `.json` file — the drop zone is labelled **Upload function configuration (.json)** and rejects any other file type. Drag the file in or use **Add files**, then press **Import**. The rule is recreated in your list.

### If the file is rejected

A red banner appears above the file. Its heading says what is wrong — for example **This file is missing the rule type or title.** or **Wrong or corrupted configuration.** — and the text below it explains that the file must be a valid `.json` exported from Codebeans Payment Rules Pro. The file stays selected, so you can read the reason before you close the dialog.

![The import error banner](https://mintcdn.com/codebeans-payment-rules-pro/0guf-DxrSbw6Ls57/images/import-error.png?fit=max\&auto=format\&n=0guf-DxrSbw6Ls57\&q=85\&s=2173e2c9d646f566ff0e09ab1a124181)

Two things cause it:

* **The file was edited.** Exported JSON is not meant to be hand-tweaked; changing it usually breaks the structure the importer expects. Export a fresh copy rather than repairing one.
* **The file came from somewhere else.** Another app's export, or a JSON file unrelated to payment rules, will not import.

The fix in both cases is the same: go to the store that has the working rule, **… → Export customization**, and import that fresh file.

## What it is for

**Staging to production.** Build and test on a development store, export, import into the live store. Safer than rebuilding a complex rule from memory.

**Backup before a risky edit.** Export first. If the edit goes wrong, delete and re-import the original.

**Replicating across stores.** Multi-store merchants build the rule once and import it everywhere.

**Support.** Attaching the export to a support request tells the team exactly what your rule contains.

## What does not travel

> [!WARNING]
>
> A rule references your store's payment methods. Import it into a store with different gateways enabled and the references will not all resolve — a rule hiding *Credit Card (Stripe)* does nothing on a store with no Stripe. Open every imported rule and confirm its method toggles before activating it.

The same caution applies to Organizer rules: imported country and Market zones are only as valid as the target store's Markets configuration, and company zones depend on that store's B2B records.

## After importing

Check three things, in order:

1. The **payment methods** resolved to real methods on this store.
2. The **Description** panel reads as the rule you intended.
3. The **Status** — set it deliberately rather than assuming.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.