Stripe-to-Stripe Migrator

[claudiulodro]

All Submissions:

• Have you followed the Newspack Contributing guideline?
• Does your code follow the WordPress' coding standards and VIP Go coding standards?
• Have you checked to ensure there aren't other open Pull Requests for the same update/change?

Changes proposed in this Pull Request:

This PR adds a Stripe-to-Stripe migrator which can migrate Stripe subscriptions (even Connect ones) to Newspack Simplified Donate Block Stripe subscriptions. We'll want to figure out how to merge this and #1984, because merge conflicts are gonna happen as soon as one of these is merged.

How to test the changes in this Pull Request:

1. Generate some Stripe Connect orders using this PR: Experimental Stripe Connect test #2031 Make sure after you're done and this branch is checked out, you reset the Stripe keys in the Reader Revenue settings to use the child connected account keys, not the parent account which would be e.g. Pico's Stripe keys.
2. Run wp newspack stripe sync-stripe-connect-to-stripe --dry-run. You should see output similar to the following:

Processing customer: [email protected]
  - Processing subscription: [redacted subscription id]
    * Found subscription item: $15/month
    * Would have created subscription with next renewal at 2022-10-22
Processing customer: [email protected]
  - Processing subscription: [redacted subscription id]
    * Found subscription item: $41.5/month
    * Would have created subscription with next renewal at 2022-10-22
Processing customer: [email protected]
  - Processing subscription: [redacted subscription id]
    * Found subscription item: $20.91/month
    * Would have created subscription with next renewal at 2022-10-22
...

4. Run wp newspack stripe sync-stripe-connect-to-stripe. You should see output similar to the following:

Processing customer: [email protected]
  - Processing subscription: [redacted existing subscription id]
    * Found subscription item: $15/month
    * Created subscription: [redacted new subscription id] with next renewal at 2022-10-22
    * Cancelled old subscription: [redacted existing subscription id]
Processing customer: [email protected]
  - Processing subscription: [redacted existing subscription id]
    * Found subscription item: $41.5/month
    * Created subscription: [redacted new subscription id] with next renewal at 2022-10-22
    * Cancelled old subscription: [redacted existing subscription id]
Processing customer: [email protected]
  - Processing subscription: [redacted existing subscription id]
    * Found subscription item: $20.91/month
    * Created subscription: [redacted new subscription id] with next renewal at 2022-10-22
    * Cancelled old subscription: [redacted existing subscription id]
...

In Stripe, you should see the new subscriptions created with correct next renewal date:

In the cancelled subscriptions section, you should see the old ones cancelled:

5. Run wp newspack stripe sync-stripe-connect-to-stripe again. You should see output similar to the following:

Processing customer: [email protected]
  - Processing subscription: [redacted new subscription id]
  - Subscription already migrated to Newspack on 2022-09-22T19:43:15+00:00. Skipping.
Processing customer: [email protected]
  - Processing subscription: [redacted new subscription id]
  - Subscription already migrated to Newspack on 2022-09-22T19:43:19+00:00. Skipping.
Processing customer: [email protected]
  - Processing subscription: [redacted new subscription id]
  - Subscription already migrated to Newspack on 2022-09-22T19:43:23+00:00. Skipping.
...

6. Run wp newspack stripe sync-stripe-connect-to-stripe --force. This will re-build all subscriptions, even migrated ones. You should see output similar to the following:

Processing customer: [email protected]
  - Processing subscription:  [redacted existing subscription id]
    * Found subscription item: $15/month
    * Created subscription: [redacted new subscription id] with next renewal at 2022-10-22
    * Cancelled old subscription:  [redacted existing subscription id]
Processing customer: [email protected]
  - Processing subscription:  [redacted existing subscription id]
    * Found subscription item: $41.5/month
    * Created subscription: [redacted new subscription id] with next renewal at 2022-10-22
    * Cancelled old subscription: [redacted existing subscription id]
Processing customer: [email protected]
  - Processing subscription:  [redacted existing subscription id]
    * Found subscription item: $20.91/month
    * Created subscription: [redacted new subscription id] with next renewal at 2022-10-22
    * Cancelled old subscription:  [redacted existing subscription id]
...

Other information:

• Have you added an explanation of what your changes do and why you'd like us to include them?
• Have you written new tests for your changes, as applicable?
• Have you successfully ran tests with your changes locally?

[claudiulodro]

Just realized after opening this, I should probably add a check for existing Woo and Simplified Donate Block payments in Stripe, so we don't override those.

[adekbadek]

Pushed two changes:

• e09d57d changes the methods to static, since they're called statically. As it was before the code errored out, perhaps because I ran it on PHP 8.
• 0537941 adds trial_end, to avoid charging the customer twice. When a subscriptions is created, the customer is charged. Putting the subscription on trial period until next invoice seems like the only way to create a subscription without the initial charge.

[claudiulodro]

Good catch! Thanks for fixing those. I switched to a different local environment recently, and clearly I need to make sure PHP notices are working correctly 🤔 I'll hold off on merging this until #1984 is merged, so I can resolve merge conflicts in this one

[matticbot]

🎉 This PR is included in version 1.92.0-alpha.4 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

[matticbot]

🎉 This PR is included in version 1.92.0 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀