This guide explains how to use Cleeng Migration Assistant to format, validate, and prepare user account data from external platforms (Recurly and Vimeo) for import into the Cleeng dashboard.
The Cleeng Migration Assistant enables a Claude-supported migration process to help streamline your data migration. Please note that if you choose to use this method, you will be using your own Claude environment, and processing data outside of the Cleeng system. Cleeng provides instructions and suggestions, but is not an intermediary in the process.
Before uploading anything to the Cleeng dashboard, you are responsible for verifying all your mapped data and output files to ensure everything is correct.
What's included
Supported source platforms:
- Recurly
- Vimeo
Supported data:
- User account data
- Web subscription data
- In-app purchase (IAP) subscription data
- Payment and card data
If you need to migrate any of the above, contact Cleeng B2B Support Team before starting. You can still proceed with user data migration in the meantime.
Step 1: Install the skill
- Download the skill file
Download the cleeng-migration-assistant.skill file (see the Skill file for upload section below). Save it in a place where you can easily find it.
- Open Claude.ai and go to Customize
Log in at Claude.ai. In the left sidebar click Customize.
- Open the Skills section and install
Navigate to Skills in the left sidebar. Click the "+" icon to add a skill and select Create a Skill > Upload a skill, then select the .skill file you downloaded. The Cleeng Migration Assistant will appear in your list once installed.
Step 2: Run the migration assistant
- Start a new conversation
Open a new chat in Claude. Type a prompt, for example: "I need to migrate my subscribers from Recurly to Cleeng" - the assistant will take it from there.
- Follow the assistant step by step
The assistant will confirm your source platform, explain what's in scope, walk you through exporting your CSV, and then transform and validate the data for you.
- Review and approve your data
If any rows have errors or warnings, the assistant will pause and ask how to handle them - you can discard, fix, or review each issue together.
- Download your output ZIP
Once approved, you'll get a ZIP withcleeng_import.csv(ready to upload) and an error report if any rows were flagged. -
Import in the Cleeng Dashboard - for details see Migration via Cleeng Dashboard.
Before you start
Complete these two checks before beginning the import.
1. Verify your publisher account
Your Cleeng account must be verified before an import will be accepted. Verify your account.
2. Disable transactional emails
A real import can trigger thousands of welcome emails to your subscribers. Disable transactional email templates in your Cleeng dashboard before uploading. Go to: Admin & Tools > Transactional Emails and disable the relevant templates.
Migration Assistant FAQs
My platform isn't Recurly or Vimeo. Can I still use the migration assistant?
Yes. If you have an export file from another platform, the migration assistant can still help you map, transform, and validate the data manually. Just let it know when it asks about your source platform.
I need to migrate payment or subscription data too.
Currently, the Migration Assistant handles user account data only. For payment, card, and subscription data migration, contact Cleeng B2B Support Team directly. You can run the user data migration in parallel while that is arranged.
Some rows had errors. Can I fix them and re-import?
Yes. You can discard errored rows and import clean rows now, then correct the remaining rows and run a separate import later. The migration_errors.csv file contains everything you need to identify and fix each issue.
What do I do with warnings in migration_errors.csv?
Warning rows can be imported - they have an anomaly but are not necessarily invalid. The migration assistant will show you each warning before generating the final file and ask whether to include or discard those rows.
What if the dashboard import fails for some rows?
After the import completes, download the report file from the Cleeng dashboard - it will list any rows that were not processed. Share those details with the migration assistant or with Cleeng support for further assistance.