> 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/faq/configuration-migration.md).

# Configuration Migration

## Step-by-Step Guide for Migrating Configurations

{% stepper %}
{% step %}
**Prepare Dependencies**

* Ensure that any dependencies, such as campaigns, rewards, tiers, or segments, are imported or created beforehand.
* After importing each configuration, adjust the imported settings to resolve any missing dependencies. Notifications will guide you through this step.
  {% endstep %}

{% step %}
**Follow the Recommended Sequence**

Migrate the setup in the following order for a smooth process:

* [ ] **Wallets**: Migrate the wallet configurations.
* [ ] **Tiers**: Migrate tiers configurations.
* [ ] **Custom Event Schemas**: Migrate custom event schema configurations.
* [ ] **Segments**: Migrate segments configurations.

{% hint style="info" %}
Note that some segments may depend on achievements and campaigns.
{% endhint %}

* [ ] **Rewards**: Migrate reward configurations.
* [ ] **Achievements**: Migrate achievement configurations.
* [ ] **Campaigns**: Migrate campaign configurations.
* [ ] **Webhooks**: Set up webhooks **manually**.
  {% endstep %}
  {% endstepper %}

## How to Best Migrate Configurations

To migrate configurations between tenants within the same environment, you can use the **Config Duplication** feature.&#x20;

For migrating configurations between different environments, the **Configuration Exports** feature is available.&#x20;

<table data-card-size="large" data-view="cards"><thead><tr><th></th><th></th><th data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>Config Duplication</strong></td><td>Best for config migration within the same environment </td><td><a href="/implementation-guide/global-management/config-duplication.md">Config Duplication</a></td></tr><tr><td><strong>Configuration Exports</strong></td><td>Best for config migration between the environments</td><td><a href="/implementation-guide/integrations-and-data-exchange/imports-exports/exports/configuration-exports.md">Configuration Exports</a></td></tr></tbody></table>


---

# 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 dynamically 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/faq/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 `build a script that syncs our docs to a CMS` 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.
