Skip to content

Migrating subscriptions #341

@rvdsteege

Description

@rvdsteege

From customer in a support ticket:

We are currently in the process of launching a new version of *****. Now we currently have a lot of recurring subscriptions/donations in the website. Do you have any instructions on how we should go about and migrate those into our new website?

We now advise to update the theme and leave the database intact — which holds the subscriptions for Pronamic Pay and e-commerce plugin (e.g. Gravity Forms, MemberPress, WooCommerce Subscriptions). But this is not always an option:

Helaas is het voor ons niet mogelijk om met dezelfde database verder te werken. Nu is het voor ons geen probleem om op database niveau zelf wat specifieke data te migreren.

De nieuwe website wordt parallel gebouwd aan de huidige website. Aangezien er tijdens de bouw nieuwe herhaaldelijke betalingen worden afgesloten, kunnen we dit niet overnemen uit een backup. Is er een manier om Pronamic handmatig over te zetten? Wellicht via database oid?

Migrating the pronamic_gateway, pronamic_payment and pronamic_pay_subscr post types and associated post meta will continue the recurring payments for subscriptions in most cases (as the reference to the Mollie customer and mandate is nowadays stored in the subscription post content JSON). However, if the gateway configuration post ID has changed during migration, updating the _pronamic_subscription_config_id meta of the subscriptions to the new configuration post ID is also necessary.

Although the recurring payments are possibly starting fine after manual migration, some references (such as WordPress users, source IDs, etc.) are possibly broken after migration. This might result in loss of functionality (for instance, it is not possible to use the Gravity Forms form subscription notifications anymore if the form entries are not migrated or have changed IDs).

Can we improve the process of migrating subscriptions to a new website? Maybe with a separate import/export add-on plugin? Implementing custom tables in #234 might also help to ease migration.

Internal Help Scout tickets:

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    Status

    Todo

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions