When you decide to switch to Cleeng from another platform, one of the very important points that need to be handled is undoubtedly data migration.
Our Experience
Cleeng has a strong track record of successfully executing complex subscriber migrations for enterprise clients worldwide. We have migrated millions of users across multiple platforms (credit cards, Apple, Google, Amazon, Roku) while ensuring data integrity, security, and service continuity. Our proven methodology, combined with close collaboration with our clients, minimizes risks and provides confidence that the migration process will be seamless and reliable.
Cleeng Migration Options
Cleeng supports two primary approaches for migrating existing clients and subscribers onto its platform:
- Option 1 – Managed Migration
- Option 2 – Do-It-Yourself Migration.
Each option is tailored to meet different requirements and resource availabilities.
Option 1: Managed Migration
Work directly with Cleeng or a certified Cleeng partner for a comprehensive, end-to-end migration. This option is ideal for organizations with many subscribers or those seeking to minimize operational risks, and impact on your subscriber activities.
Key Features
- Full Migration of Users & Payment Details: Cleeng manages the entire process, including all user profiles, active subscriptions, payment details, and entitlements. Sensitive payment data is securely handled per GDPR and PCI requirements.
- Structured, Stepwise Guidance: The process includes careful planning, staging in sandbox and production, data validation, and cutover support. Cleeng provides templates, checklists, and dedicated support personnel at each phase.
- User Experience Focus: Steps are designed to minimize user disruption and ensure service continuity.
- Compliance: All procedures follow strict GDPR and PCI standards, with secure data transfer using encryption and SFTP.
Scope of Migration
To be migrated:
- User data (emails, locale, country, currency, optional profile info)
- Subscription data (active entitlements)
- (Optional) Credit card payment details (via PSP → Adyen)
- (Optional) In-app purchase references (Apple, Google, Amazon, Roku)
Not included by default:
- Historical subscriptions and subscription lifecycle data
- Aggregated analytical financial numbers, like historical MRR, CLTV, etc.
- Historical transactions
- Historical emails being sent
- Receipt/Invoices or financial/analytics data
Migration Process Overview
The data migration process consists of several steps:
- Confirm scope of migration data (user, entitlements, app stores)
- Detailed User data
- Password hashing algorithm ( Bcrypt )
- VIP users, running promotions, etc.
- What app stores, and what versions (e.g. Apple StoreKit 1 or StoreKit2)
- Which payment methods, and what functionalities are enabled
- Mapping of the products, SKUs and offers
- Volume for each data object
- Initial data preparation - Standard templates are available for each data object.
Key considerations include:- Renewal/expiry dates - must be in the future
- Supported currencies
- Locale - dictates the language users will see on the widgets and emails
- Prepare Cleeng sandbox environment for test migration
- Data migration in the Test environment and verification of results
- Prepare Cleeng production environment
- Ensure relevant payment methods are enabled and configured
- Data migration in the Production environment and verification of results
- New service cutover
- Post-migration analysis of migrated data
Roles and responsibilities
| Activity | Cleeng | Customer |
| Kick-off migration process | X | |
| Support on the migration templates | X | |
| Planning, communication and execution of a cutover strategy | X | |
| Coordinating with existing payment service provider for payment data migration. | X | |
| Exporting relevant data from legacy platform/systems | X | |
| Ensuring data is complete and properly formatted | X | |
| Delivering data according to agreed timelines | X | |
| Final review of data before being processed | X | |
| Importing data into the Cleeng platform within agreed timelines | X | |
| Sharing post-migration analysis data | X |
Additional Notes
- Some customers have difficulty extracting and handling large data sets. Cleeng can recommend partners that can help you.
- Not all data types can be migrated as part of the default migration process. For example, Cleeng does not import historical lifecycle analytics, transactions or previously redeemed coupons. Always cross-reference your scope with Cleeng support.
- Cleeng provides documentation, templates, and sample scripts for typical onboarding use-cases and can review your planned approach
Option 2: Do-It-Yourself Migration
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.
Key Steps
- User & Subscription Upload: Use Cleeng’s API endpoints to import users and create active subscriptions. Carefully monitor and adhere to Cleeng’s API rate limits when building scripts or automation for the import.
- Handling Legacy Credit Card Data: for self-service migration today we do not support extracting card information due to PCI guidelines. However you can keep existing users billing through your previous provider, and use Cleeng for all new subscribers. Sync subscription data either manually or by automated scripts until the bulk of your users churned on the legacy system.
- Password Resets (Important): For security and compliance, password resets for migrated users are often required. It’s strongly recommended to proactively communicate this “platform update” to all affected subscribers.
Learn more
Please go to the developer documentation for more details on the do-it-yourself data migration to Cleeng.