Web Subscription Data

The table below specifies data to be provided in the Web Subscription Data migration template.

Mandatory fields are marked with an asterisk (*).

Please ensure your data adhere to the data specification guidelines before submission.

Column Name	Format	Description	Example
User email*	string	The email address of the customer. It is a unique user identifier in Cleeng.	[email protected]
Offer ID*	string	Cleeng offer ID corresponding with the previously subscribed package.	S123456789_PL
Expiry date*	YYYY-MM-DD	The date of the subscription expiry or scheduled renewal. It must not be in the past.	2026-10-30
Status*	string	The status of the subscription: `active` means that the user has access and the subscription will be automatically renewed when the expiry date is reached (Cleeng will attempt to charge the subscriber on the expiry date.) `stopped` if the user has access but opted out from the renewal (Cleeng will terminate the subscription upon expiry).	active
Payment method ID (will be used also for payment gateway)*	integer	A numeric value, representing unique id of a specific payment method to be used for subscription renewal.
Subscription external ID	string	Custom attribute that allows to store subscription ID from legacy or third-party system for reporting purposes.
External properties	JSON format, only strings	Additional custom attributes.
Season Index (required for seasonal offer)	integer	The season number within an offer. Required for seasonal offers	1
Coupon Code	string	Coupon applied on a subscription in a legacy system.	Free4Me
Campaign name	string	Name of a campaign to which a coupon code belongs	Winter season
Coupon Already Used	integer	The number of times a coupon was applied already.	1

Important considerations

Cleeng logic triggers first recurring billing on an expiration date of subscription. Cleeng logic also automatically terminates subscriptions that reach expiry without valid payment details. Therefore, clients must proactively adjust or extend expiration dates in advance to allow for migration of payment details. This buffering accommodates typical PSP processing delays and reduces risk of unintended subscriber terminations. Proper expiry date planning is a critical success factor for smooth migration.
Before exporting and providing subscription data to us, all subscription updates in the legacy system should be stopped. This prevents scenarios where a subscription is modified in the legacy platform after the export, but the change is not reflected in Cleeng. By freezing updates at the source, you ensure data consistency and avoid discrepancies that could impact billing accuracy and customer experience
For users who are being migrated and are entitled to specific localized offers, it is required to map the offer ID of each localized offer. This ensures that users retain access to the correct localized pricing
The required format of expiration date is YYYY-MM-DD, please do not include hourly timestamps in it.