Migration process - RaiseNow Manager to RaiseNow Hub

To ensure an efficient migration process, the following steps must be executed in order.

1. Switch Tamaro to process new one-off and recurring card payments on RaiseNow Hub. This step is crucial to avoid generating subscriptions on the RaiseNow legacy platform after the migration has already been initiated. Subscriptions created on RaiseNow Manager after the migration process has been initiated will not be migrated to RaiseNow Hub. This means any backend integrations you may have must be ready to process one-off payments and new subscription records from RaiseNow Hub by this time. Please refer to this article for guidance on integrations.
2. Execution of the migration process for card data. This migration is managed by RaiseNow and does not directly involve RaiseNow customers. It is a complex migration process that ensures, data is transferred between the new systems in a PCI compliant manner. This step is a hard prerequisite to charge imported subscriptions on RaiseNow Hub.
3. Transfer of subscriptions to RaiseNow Hub. After this step, subscriptions exist both in RaiseNow Manager as well as in RaiseNow Hub. Subscriptions in RaiseNow Hub will have references to the legacy subscription token from RaiseNow Manager. See this section for more details. Subscriptions in RaiseNow Hub will be imported with a suspended status to avoid duplicate charges.
4. Subscriptions will be deactivated on RaiseNow Manager. This will be a silent deactivation, meaning third party systems will not be notified and emails will not be triggered.
5. Exactly one day after the deactivation on RaiseNow Manager, subscriptions will be activated on RaiseNow Hub. This way we can ensure that no duplicate charges are executed or that planned charges are missed.