Customer Migration Mapping

3 min

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 APIHERE, you will find:

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