> 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/integrations-and-data-exchange/imports-exports/imports/data-migration-guide.md).

# Data Migration Guide

When migrating an existing loyalty program to Open Loyalty, the order in which you import data matters. Members are the core of your loyalty program — all other data depends on accurate member records being in place first.

#### 🧩 Recommended import sequence

{% stepper %}
{% step %}

#### 1. Import members

Start by importing all member profiles. This establishes the foundation — every other import type references members by their Open Loyalty UUID.
{% endstep %}

{% step %}

#### 2. Map member IDs

After importing members, note the Open Loyalty UUIDs assigned to each member. You will need these IDs for unit transfer imports. Transactions and custom events can use external identifiers (email, phone, loyalty card number), but unit transfers require the internal Open Loyalty member ID.

{% hint style="info" %}
Use the **Members export** to download a complete list of members with their UUIDs after the import is complete.
{% endhint %}
{% endstep %}

{% step %}

#### 3. Import unit transfers (point balances)

With member IDs mapped, import unit transfers to set correct point balances. This step requires the Open Loyalty member UUID — external identifiers are not supported for unit transfers.
{% endstep %}

{% step %}

#### 4. Import transactions (optional)

Import historical transaction data and match transactions to members. Transactions can reference members by email, phone, or loyalty card number, so they don't require the internal UUID.
{% endstep %}

{% step %}

#### 5. Import remaining data

Import any additional data as needed: segments, redemption codes, coupons, and collections.
{% endstep %}
{% endstepper %}

### What cannot be imported

Not all data types support bulk import. The following operations are **not available** through file import and must be done via the API or manually in the Admin Panel:

* Reward redemption status updates (e.g., marking redemptions as delivered or cancelled)
* Custom events
* Webhook configuration


---

# 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/integrations-and-data-exchange/imports-exports/imports/data-migration-guide.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.