| Prio | Original string | Translation | — |
|---|---|---|---|
| Stop Workflow | You have to log in to add a translation. | Details | |
| Start Migration | You have to log in to add a translation. | Details | |
| Dry run is off, so this is a real migration. These changes are permanent and cannot be undone: subscriptions will be migrated and cancelled at the old gateway. | You have to log in to add a translation. | Details | |
|
Dry run is off, so this is a real migration. These changes are permanent and cannot be undone: subscriptions will be migrated and cancelled at the old gateway.
You have to log in to edit this translation.
|
|||
| Records what would happen to each subscription in the migration log without changing anything or sending email. Some gateway errors only show up during a real migration. | You have to log in to add a translation. | Details | |
|
Records what would happen to each subscription in the migration log without changing anything or sending email. Some gateway errors only show up during a real migration.
You have to log in to edit this translation.
|
|||
| Preview the migration without making any changes | You have to log in to add a translation. | Details | |
| Dry Run | You have to log in to add a translation. | Details | |
| A next payment date in the past (or none at all) usually means a payment notification from the old gateway never arrived, so the gateway may still be billing the member. Skip leaves these subscriptions alone and lists them in the migration log to check by hand. Cancel and expire cancels them at the old gateway and ends the membership three days after the migration runs. This applies to either migration type. | You have to log in to add a translation. | Details | |
|
A next payment date in the past (or none at all) usually means a payment notification from the old gateway never arrived, so the gateway may still be billing the member. Skip leaves these subscriptions alone and lists them in the migration log to check by hand. Cancel and expire cancels them at the old gateway and ends the membership three days after the migration runs. This applies to either migration type.
You have to log in to edit this translation.
|
|||
| Cancel them and expire the membership | You have to log in to add a translation. | Details | |
| Skip them and log them for manual review | You have to log in to add a translation. | Details | |
| Subscriptions With a Missed Payment | You have to log in to add a translation. | Details | |
| Edit the checkout required email | You have to log in to add a translation. | Details | |
| Edit the Stripe migration email | You have to log in to add a translation. | Details | |
| Send each migrated member one email when their subscription is processed: the Stripe migration email asks them to add a payment method, and the checkout required email asks them to check out again. To send through your own email service instead, choose "Do not email members" and use the Migration CSV after the migration. Either way, members still get your site's regular automatic emails: Stripe members without a payment method get a recurring payment reminder asking them to add one, and expiring members get the standard expiration warning. | You have to log in to add a translation. | Details | |
|
Send each migrated member one email when their subscription is processed: the Stripe migration email asks them to add a payment method, and the checkout required email asks them to check out again. To send through your own email service instead, choose "Do not email members" and use the Migration CSV after the migration. Either way, members still get your site's regular automatic emails: Stripe members without a payment method get a recurring payment reminder asking them to add one, and expiring members get the standard expiration warning.
You have to log in to edit this translation.
|
|||
| Do not email members | You have to log in to add a translation. | Details | |
| Email members about the change | You have to log in to add a translation. | Details | |
Export as
