> For the complete documentation index, see [llms.txt](https://help.openloyalty.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.openloyalty.io/implementation-guide/data-and-go-live/configuration-migration.md).

# Configuration Migration

Moving the programme's configuration from staging to production in the right order, and what has to be set up by hand in each environment.

The programme is built and accepted on staging; production needs the same configuration before go-live. This page covers what moves with exports, the order to import it in, and what has to be recreated by hand. The procedures are in the User Guide's [Configuration migration](https://help.openloyalty.io/faq/configuration-migration) and [Configuration exports](https://help.openloyalty.io/integrations-and-data-exchange/imports-exports/exports/configuration-exports).

## Between environments or between tenants

| Moving configuration…                                          | Use                                                                                                             |
| -------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------- |
| From staging to production (different environments)            | **Configuration exports**: download each module's configuration as JSON on staging and import it on production. |
| Between tenants in the same environment (e.g. a second market) | [Config duplication](https://help.openloyalty.io/global-management/config-duplication)                          |

## What moves and what doesn't

| Configuration                                                                             | How it reaches production                                                                                         |
| ----------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------- |
| Wallets, custom event schemas, rewards, campaigns                                         | Configuration export and import (JSON)                                                                            |
| Tier sets                                                                                 | Import tier sets in the Admin Panel ([Adding tiers](https://help.openloyalty.io/gamification/tiers/adding-tiers)) |
| Segments, challenges, badges, leaderboards, member configuration, custom fields, channels | Check the module's import options; otherwise recreate them by hand or through the API                             |
| Webhook subscriptions                                                                     | **Always by hand** — with production endpoints and a new HMAC secret                                              |
| Admins, roles, API keys                                                                   | By hand, per environment — never copy keys                                                                        |
| Coupon codes                                                                              | Upload production code pools separately; don't reuse staging codes                                                |

## Recommended order

Configuration references other configuration — a campaign issues a reward, a reward is visible to a tier — so import dependencies first:

{% stepper %}
{% step %}

### Foundations

Member configuration, custom fields, channels, wallets, custom event schemas.
{% endstep %}

{% step %}

### Audiences

Tier sets, then segments.
{% endstep %}

{% step %}

### Things to give

Reward categories, rewards (then their production coupon codes), badges.
{% endstep %}

{% step %}

### Rules

Campaigns, challenges, leaderboards — last, because they reference everything above. After each import, follow the notification to re-link anything that couldn't be resolved.
{% endstep %}

{% step %}

### Integration settings

Webhook subscriptions, admins, roles and API keys for production.
{% endstep %}
{% endstepper %}

{% hint style="warning" %}
Check that imported campaigns are **inactive** (deactivate them after importing if needed) and activate them deliberately at go-live — especially if members or historical data are being [migrated](https://help.openloyalty.io/implementation-guide/data-and-go-live/data-migration.md) at the same time.
{% endhint %}

## Checklist

* [ ] An inventory of every configured item on staging exists, with how it reaches production.
* [ ] Imports run in dependency order, and every "missing dependency" notification is resolved.
* [ ] IDs that the integration uses (wallet codes, reward IDs, campaign IDs, tier set IDs, category IDs) are looked up again on production — IDs differ between environments; codes and names don't.
* [ ] Webhooks point to production endpoints with production HMAC secrets.
* [ ] Production has its own admins, roles and API keys.
* [ ] Production coupon pools are uploaded.
* [ ] A side-by-side review of staging and production configuration is signed off.

{% hint style="warning" %}
**Common pitfalls**

* Hard-coding staging IDs (reward, category, campaign) in the integration: they don't exist on production. Look them up by code or name, or keep them in configuration per environment.
* Forgetting webhooks: production runs, but CRM never hears about it.
* Activating imported campaigns before the data migration finishes.
  {% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.openloyalty.io/implementation-guide/data-and-go-live/configuration-migration.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
