Bulk Migration Capability in Recurly Subscriptions
For Recurly Subscriptions, there is no native bulk migration tool designed to move thousands of active subscribers simultaneously from old plan codes to new plan codes.
Best Practice Recommendation for API-Driven Migration
To perform a bulk migration of active subscribers, the best practice is to use the Recurly API to automate the process.
Export Current Data:
Utilize the Subscriptions export feature within Recurly to gather a comprehensive list of all active subscriptions.
Filter this export to specifically include subscriptions currently using the legacy plan codes you intend to discontinue.
Build an API Script:
Develop a script (using your preferred programming language) that is designed to iterate through the list of subscriptions obtained in the export.
For each subscription, the script must execute an Update Subscription API call.
The API call should specify the
plan_codefor the new, active plan.
Choose Migration Timing:
At Renewal: To avoid prorated charges and generating new, unexpected invoices, set the plan change to occur at the subscriber's next renewal date.
Immediately: If an immediate change in pricing or features is required, set the plan change to occur instantly. This action may trigger prorated charges and new invoices, which the subscriber will receive.
Comments
0 comments
Please sign in to leave a comment.