Migration overview
Can I migrate my subscriptions myself?
Can I migrate my subscriptions myself?
Yes, we have a built-in migration utility in the app which allows you to do the migration yourself. (reference)
Do my customers need to do anything during the migration process?
Do my customers need to do anything during the migration process?
No, there is nothing that your customers have to do on their end. They won’t even notice the switch 🙂. Subscription login is seamless through the app's magic link functionality. When migrating from non shopify platforms like WooCommerce - your customers might need to activate their shopify account from their email (optional - for when you want customer to login to Shopify account to manage their orders).
Should I set up integrations before or after migration?
Should I set up integrations before or after migration?
Please ensure that you have all your marketing / notification integrations disconnected on your old platform to avoid any notifications being triggered from these third party providers.
Is it necessary that I have to use one of the supported payment providers?
Is it necessary that I have to use one of the supported payment providers?
Yes, as a native subscription app we only support the payment providers which are supported by Shopify for subscriptions. Check Shopify’s list of eligible payment providers for more details.
Which platforms are supported for subscription migration?
Which platforms are supported for subscription migration?
Almost all subscription platforms/apps including but not limited to Recharge, Smartrr, Bold, Skio, Seal are supported. We also support migrating from any non- Shopify platform like Woocommerce, BigCommerce, Salesforce as long as they are able to provide us with the required data!
What are the details about merging 2 Loop stores into one?
What are the details about merging 2 Loop stores into one?
Two Loop accounts cannot be directly merged together. However, you can migrate subscription data from one account (Store 2) into another (Store 1) if compatible conditions are met.
The second store (Store 2) is treated as a custom subscription app platform, and its data is migrated into the primary store (Store 1). This process depends on the payment service provider (PSP) used.
Migration is supported when the PSP is Stripe or Auth. For other PSPs, feasibility must be confirmed with the Migration Team.
All credit card information from Store 2 is automatically transferred to Store 1 via Shopify.
No, order history, analytics, and similar data will not carry over during the migration.
You must provide the new variant IDs for products in Store 2. These IDs are required for precise product mapping in the migration process.
You also need to confirm the payment service provider currently used in your store and share new variant IDs so the Migration Team can proceed.
Why is my store migration delayed?
Why is my store migration delayed?
Since migration involves handling highly sensitive data, we follow a strict Standard Operating Procedure (SOP) to ensure every step is completed with accuracy and security.
Before we proceed, it would be helpful:
If you could share an export of the data, and
ensure that our team has collaborative access to your store.
This will allow us to immediately plan and begin our pre-checks.
Additionally, please note that we might reach out to clarify any questions that come up if we identify any data anomalies during the validation process.
To give you a clear picture of what the process involves:
Migration requires careful handling due to the sensitivity of the data.
Even when everything seems ready, our team double-checks each step to ensure accuracy and prevent errors.
The process cannot be completed within a single day because of its complexity and verification requirements.
Typically, migration takes around 3 to 7 working days to complete.
This duration allows us to perform both manual reviews and technical validations for data accuracy.
The final import to Loop is executed only after all checks pass successfully through our Migration Engine.
These steps are essential to maintain data integrity and deliver an error-free migration experience.
We truly understand the urgency and appreciate your patience as we follow this process to ensure a secure and seamless experience.
Data format here: https://help.loopwork.co/en/articles/12742349-loop-migration-process [data format]
Why are we not seeing billing addresses after migration?
Why are we not seeing billing addresses after migration?
We don't migrate billing address as part of the migration because we focus only subscription addresses at subscription contract level. Payment token should have billing address already.