Migration Overview
User Migration endpoints let an integration import an existing user base into the tokenization platform via API. They cover the cases where users are created in bulk during an onboarding cut-over instead of one-by-one through the standard Create User flow.
Migrate User With Wallet (Single)
Migrates a single user that already has a wallet address. The wallet address is stored as-is (lower-cased), and a KYC token event is published unless kyc_sent=true.
Migrate Users With Wallets (Bulk)
Migrates up to 500 users in a single request when each user already has a wallet address. Failures are reported per row — the request itself succeeds with HTTP 200 even when individual rows are skipped.
Migrate Users With Wallets (CSV)
Migrates users from a CSV file upload when each user already has a wallet address. Limits and response shape mirror the Bulk JSON endpoint: up to 500 rows, maximum file size 5 MB, per-row results.
Migrate User Without Wallet (Single)
Migrates a single user whose wallet should be generated by the platform. The user record is persisted synchronously; the wallet is generated asynchronously via the same mechanism as the standard Create User flow.
Migrate Users Without Wallets (Bulk)
Migrates up to 500 users in a single request; wallets are generated asynchronously for each row. Failures are reported per row — the request itself succeeds with HTTP 200 even when individual rows are skipped.
Migrate Users Without Wallets (CSV)
Migrates users from a CSV file upload; wallets are generated asynchronously per row. Limits and response shape mirror the Bulk JSON endpoint: up to 500 rows, maximum file size 5 MB, per-row results.