> For the complete documentation index, see [llms.txt](https://help.smartrr.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.smartrr.com/docs/getting-started/onboarding/migrating-subscriptions-from-payment-processors.md).

# Migrating subscriptions from payment processors

Smartrr supports migration of payment methods for multiple payment providers.

Migrating existing customers doesn't have to be daunting. If you're looking to migrate to Smartrr, you can rest easy knowing we offer in-house migrations from your current subscription app. 

Once your initial Smartrr setup is complete, our team will schedule a migration date. On this day, we'll have our QA team ready to review your migration while we run our dedicated migration script. After a successful migration, our QA team does one final review of the site and the data transferred—at which point your shop will be ready to go live.

We have migrated brands from every major subscription app as well as bespoke platforms. Our team is always available to answer any questions about your specific migration-related needs, and you can reach us at <hello@smartrr.com> with any questions.

Below you will find some more information on the requirements of migrating to a Shopify Subscription API eligible subscription app.

## Payment Processors

Smartrr supports migrating subscriptions from multiple alternative payment processors including:

* PayPal Express
* Stripe
* Authorize.net
* Braintree\*

{% hint style="warning" %}
\*In order to migrate subscriptions from Braintree there is a required extra step which is described in the [section below](#braintree).
{% endhint %}

Once migration is complete, Smartrr can use any of Shopify's eligible payment processors to handle all new subscription payments. It's always important to[ review Shopify's subscription requirements](https://help.shopify.com/en/manual/products/purchase-options/subscriptions/shopify-subscriptions/considerations#supported-subscription-product-payment-gateways) to determine your eligibility for offering subscriptions on your storefront.&#x20;

<figure><img src="https://3658670565-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FndNAuxS4koYyI8AQTpS9%2Fuploads%2F5ufzfoBFcBgcReCz54sM%2FSmartrr%20Help%20Docs%20%E2%80%93%201.jpg?alt=media&amp;token=e6628b2e-c264-407b-adad-e709376eef8c" alt="To use subscriptions, you must be using one of the following gateways: Shopify Payments, PayPal Express, Authorize.net, Adyen, Stripe. Refer to Shopify&#x27;s &#x22;Shopify Subscriptions app eligibility considerations&#x22; for further details."><figcaption></figcaption></figure>

### Braintree

In order to migrate subscriptions from Braintree, subscription data will first need to be transferred into Stripe, which is a supported Shopify payment processor.&#x20;

You will need to reach out to Braintree and have them create a file that can be transferred to Stripe. [Here’s some additional documentation](https://developer.paypal.com/braintree/articles/get-started/data-migration/overview) discussing this process with Braintree.&#x20;

If you do not already have a Stripe account you will need to create one to transfer the payment data into from Braintree. Once all customer’s payment information is in a Stripe account we can fully migrate all your subscriptions into Smartrr.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.smartrr.com/docs/getting-started/onboarding/migrating-subscriptions-from-payment-processors.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.