Migrations

You want to switch to InPlayer but you already have a large database of customers on another platform? No problem.

Our platform facilitates a quick and secure customer data migration, including migration of the customer payment data and subscriptions. This enables you to transfer your customers over to InPlayer without interrupting their access or making them re-purchase their passes.

Usually, a period of 2 weeks needs to be allotted for a migration.

Account migration

When migrating user accounts, the following customer information is required:

• Name,
• Email address,
• Passwords and information about the encryption format (InPlayer uses md5 encryption, so this is a prefered encryption format),
• Any other customer metadata you want to transfer over.

If you are unable to provide the customer passwords for whatever reason, or if the password encryption of your old platform is not bcrypt, unsalted md5, or unsalted sha1, we can still migrate the accounts, but they would need to set up new passwords when logging in for the first time.

Access migration

If, along with the account migration, you also wish to transfer the customers’ active accesses, you would need to provide us with the access expiration date for each customer.

If you are unable to provide the individual access information for whatever reason, we can simply grant all customers the same access that will be set to expire on a certain date.

Payment details migration

This migration is the most complete one, since it provides a seamless transition of your customers’ payments and subscription from your old platform to InPlayer.

There are two scenarios for this migration, depending on the payment processor that was used on your old platform:

Stripe

Stripe is the credit card payment processor used by InPlayer. If you used Stripe on your old platform, the payment information can be transferred very easily.
This usually takes from 3 to 5 business days.

Other payment processors

A different approach is taken if your old platform used a different solution than Stripe. In this case, a direct connection between the two systems needs to be made so they can exchange the required information.
This usually includes providing the following info:

• Credit card details (in an encrypted format),
• Customer IDs,
• Transaction IDs,
• SCA Transaction IDs/information,
• Any other metadata that was pushed to the payment processor.

Note that payment or subscription history cannot be migrated between payment processors.

Note also that it can take anywhere between a few days, to a few weeks for the previous payment processor to transfer the data to Stripe. After that, the aforementioned period of 2 weeks needs to be allotted for the actual migration process.

Subscription migration

After a successful payment details migration, a migration of all active subscriptions is also possible. This enables you to keep charging your customers without interruption and without asking them to provide their payment details again.

Subscription migration can only be done for users with an active credit card subscription.

For subscription migration, the following customer info is required:

• Email address,
• Old customer ID (or any unique customer identifier Stripe will be importing from the old payment provider),
• Subscription amount,
• Subscription currency,
• Subscription billing frequency,
• Last billing date,
• Next billing date.

To discuss the details of the migration process, make sure to contact your InPlayer account manager, or send us an email on support@inplayer.com.

To learn more, you can also download our migration guide here.