Migrate from Bold Native (V2)
Pre-requisites
Migrate from Bold
White glove migration walkthrough
Need help?
There are a few prerequisites that the Loop team requires before proceeding with a subscription import.
Loop widget must be live on the storefront and account page should point to Loop customer portal (guide) (read more)
Bold API token must be created with write access to all scopes and shared with loop team (guide)
Customer portal permissions must be set to disabled prior to the migration (guide)
Notifications must be set to disabled prior to the migration (guide)
Since Bold v2 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.
Once you have satisfied the prerequisites mentioned above, the loop team will be able to help you bring subscriptions over from your Bold v2 app.
Please reach out to us on support@loopwork.co 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.
To understand more about the options you have while migrating to loop, refer to this article.
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 V2 -> Loop
Email content
Source platform - Bold v2
Bold API key - {insert api token}
Make special note to confirm which version of Bold you are using just to be sure as the process differs quite a lot between the two platforms (guide)
Our Onboarding / migrations team will get in touch with you shortly and suggest a few days as per the team's availability.
This section details the overall 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.
There is no need to worry. We are here to assist you. Please contact us at support@loopwork.co or feel free to reach out to us through the chat by clicking on the support beacon located at the bottom right corner.
Regards,
Loop Subscription Team 🙂
Migrate from Bold
White glove migration walkthrough
Need help?
Pre-requisites
There are a few prerequisites that the Loop team requires before proceeding with a subscription import.
Loop widget must be live on the storefront and account page should point to Loop customer portal (guide) (read more)
Bold API token must be created with write access to all scopes and shared with loop team (guide)
Customer portal permissions must be set to disabled prior to the migration (guide)
Notifications must be set to disabled prior to the migration (guide)
Since Bold v2 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 v2 app.
Please reach out to us on support@loopwork.co 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.
To understand more about the options you have while migrating to loop, refer to this article.
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 V2 -> Loop
Email content
Source platform - Bold v2
Bold API key - {insert api token}
Make special note to confirm which version of Bold you are using just to be sure as the process differs quite a lot between the two platforms (guide)
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 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.
Still Need help?
There is no need to worry. We are here to assist you. Please contact us at support@loopwork.co or feel free to reach out to us through the chat by clicking on the support beacon located at the bottom right corner.
Regards,
Loop Subscription Team 🙂
Updated on: 11/09/2024
Thank you!