If you’re currently using Bold and want to move to Loop, our migration team can help you transfer all your subscriptions smoothly with zero disruption to your customers.
Prerequisites
Before proceeding with a subscription import process, we need to make sure these things are in place.
Since Bold is built on native subscription APIs of Shopify, there is no need for any payment migration in this case.
Please ensure that the API token created for the Loop team has write access to the subscription object, otherwise step (4) will fail.
Migrate from Bold
Once you have satisfied the prerequisites mentioned above, the loop team will be able to help you bring subscriptions over from your Bold app.
Please reach out to us at [email protected] with the required information and our team will help you get things over the line with our dedicated migration for a white glove migration experience on any of our paid plans.
Learn more: Options you have while migrating to Loop
Here is a quick email template to kick-start things if you have not been in touch with a team member from Loop already 😉
Subject line : {Brand Name} Migration from Bold -> Loop
Email content
Source platform - Bold
Bold API key - {insert api token}
Our Onboarding/migrations team will get in touch with you shortly and suggest a few days as per the team's availability.
White glove migration walkthrough
This section details the overall sequence of steps taken by the Loop team on the scheduled migration date.
Loop team will take an export from Bold APIs (reference) using the shared tokens from earlier.
Once the data has been exported from the APIs, Loop team will convert it into the standard migration data format of Loop.
Once the data has been fetched from Bold, the migration expert will begin the import at the scheduled time.
Post subscription migration completion, Loop team will go proceed with actioning a bulk cancellation action on Bold through their APIs (reference)
A detailed migration report (reference) will be shared with the merchant, along with a 1:1 mapping between the contracts in both platforms for easy review.
Merchant is then advised to do an overall review by spot checking a few contracts in between and ensuring data parity.
Loop team will wait to hear back on the data review and migration confirmation requested in (6) and any open points on the same.
Point (4) ensures that no customer is doubly charged due to the subscription contract being active on both platforms.
If there are any custom requirements for the migration like price update, variant swapping etc., the migration team would need to be informed at least a week in advance so that we can have this accommodated on our end.
Need help?
No worries - we're here for you!
If you have any questions or need assistance, feel free to email us at [email protected] or chat with us using the support beacon at the bottom right of your screen.
Regards,
Loop Subscriptions Team 🙂