Migrating to Cleeng

If you're transitioning from an existing platform to Cleeng, you're in the right place. Cleeng supports two primary approaches for migrating existing clients and subscribers onto its platform: Option 1 – Managed Migration and Option 2 – Do-It-Yourself Migration. Each option is tailored to meet different requirements and resource availabilities (for more information, you can see our data migration guide in the Help Center).

This article focuses on the technical guidance for option 2: do-it-yourself migration.

Do-it-yourself data migration to Cleeng

If you have limited users/subscribers (up to 10,000) - and for those looking for flexibility and direct control, it is possible to migrate via Cleeng’s APIs.

This high level tutorial provides technical guidance on how to self migrate subscriber data from existing systems into Cleeng. It is assumed you have good understanding and access to the data required, have cleaned up the data, and are familiar with the Cleeng API, Sandbox and Cleeng’s data objects.

📘

Important notes:

• Cleeng also offers Managed Migrations. Please read more about the options and differences. Do-it-yourself migrations have certain limitations.
• When you decide to “do it yourself” and you are on a free Cleeng Pro account, Cleeng cannot support you. That also means Cleeng will not remove (wrongly imported) data (e.g. users or subscribers). Be careful and use the sandbox with sample data to try out your data before uploading to production so as to avoid unexpected bills.
• Migrated users with active subscriptions will be counted as managed users (MU) and will appear on the invoice.
• Avoid overloading our APIs and do rate limiting. Throttle at 100 RPS for migrations to avoid any risks. We can otherwise block the account. Inform Cleeng 48 hours in advance in case you plan to load 5000 users/subscribers or more on production.
• Data is processed in the background and some data only appears with a delay in the Cleeng dashboard. Use the Core APIs to verify instantly.

Migration order

The logic of the Cleeng platform and the relationships among its objects necessitate the migration of various data objects in a precise sequence to guarantee correct associations.

The migration order is outlined in the following steps:

1. First you will need to create your offers in Cleeng (aka. products, packages, SKUs etc).
2. Once the products are created you will need to migrate the user accounts so they are able to sign in after you move to the new setup.
3. Once the users are on board, you’ll need to migrate active subscriptions (entitlements) so the users can continue accessing the content they paid for. This will include web purchases as well as IAP and other channels, such as carrier billing subscriptions.
4. Ideally, Cleeng receives in-app purchase confirmations, so it can keep the relationship with the app stores (Apple, Google, Roku, etc) in sync.
5. Unfortunately, for do-it-yourself migrations, active payment details cannot be migrated due to PCI regulation and complexities. You can mitigate this by keeping your recurring billing on your legacy platform and sync the subscriptions. Alternatively, consider Managed Migrations.
6. Optionally, if you already distributed discount codes or vouchers that have not been redeemed or applied yet you can also migrate those by uploading them in the dashboard.
7. Verify your results and data.
8. Prepare for switch-over of your end-user application, and if relevant - inform your subscribers to reset their password.