# 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. 

For migrating configurations between different environments, the **Configuration Exports** feature is available. 

<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="../main-features/global-management/config-duplication">config-duplication</a></td></tr><tr><td><strong>Configuration Exports</strong></td><td>Best for config migration between the environments</td><td><a href="../main-features/imports-exports/exports/configuration-exports">configuration-exports</a></td></tr></tbody></table>