---
title: Customer Migration Mapping
slug: customer-migration-mapping
docTags: 
createdAt: 2026-07-22T08:37:00.251Z
---

# What this is about

The customer list returned by the customerarea API now includes a migration object for each customer, showing whether that customer has been migrated to the new cloud platform and, if so, its corresponding organization\_id.

## What you'll find

In the customer/list endpoint, documented in [Customer List API](docId\:zHZnxpx3uxTPqkF7mPwNF), you will find:

:::BlockQuote
...
"organization\_id": "019f88ef-7fb5-725c-88e8-0d7028d1b392",
"migration\_status": "MIGRATED"
...
:::

- **organization\_id** — the customer's identifier on the new platform. It is populated only if the customer has been provisioned or migrated (or exists solely on the new platform). Otherwise it is null.
- **migration\_status** — the current migration state of the customer (values are uppercase, e.g. MIGRATED, NOT\_MIGRATED, MIGRATION\_STARTED).

## How to use it

- If organization\_id is present, that value is the customer's identifier on the **new platform** — use it there.
- If organization\_id is null, keep using the customer's existing customer\_code on the **legacy** API.

## New platform API key

To operate on the new platform, you'll need a separate API key. This key is **not** the same as your legacy x-api-key — you'll find it directly inside the **new panel**, under your account/API settings.

