Migrate Payment Gateway Tool Guide

The Migrate Payment Gateway tool lets you bulk update the payment gateway and payment tokens on your existing PayKickstart subscriptions using a CSV file. Use it when you have moved your customers’ payment data from one payment gateway to another and need your PayKickstart subscriptions to keep billing through the new gateway.

This tool does not export your data or move subscriptions off PayKickstart. It updates subscriptions that are already managed in PayKickstart so they charge through a different gateway and the new tokens.

You arrange the transfer of customer and payment tokens directly between your old and new payment processors first (for example, a Stripe to Stripe data copy, or asking your new processor to request the transfer from the old one). PayKickstart is not involved in that step. Once the tokens exist in your new gateway, this tool simply points your existing PayKickstart subscriptions to the new tokens.

Before you begin

• Your subscriptions are already managed in PayKickstart. (If they are not yet in PayKickstart, use Import Subscriptions instead.)

• You have already transferred the payment data/tokens directly between your old and new gateways, and you have the new customer and payment tokens from the new gateway (for a Stripe copy, these come from Stripe’s mapping file).

• Your PayKickstart user has permission to manage subscriptions (the tool checks this when it validates your file).

Understanding the CSV columns

Each row of the CSV updates one subscription. Here is what each identifier means and where to find it:

• subscription ID: the PayKickstart subscription to update. It looks like PK-XXXXXXXXXX and is shown on the subscription’s details page (Payments → Subscriptions).

• gateway ID: PayKickstart’s ID for a payment gateway integration on your account. You will find it on each integration card under Configure → Integrations (the Gateway ID value). “Old” is the integration the subscription bills through today; “new” is the integration it should bill through after the migration.

• customer ID: the customer’s identifier inside the payment gateway (for Stripe, it starts with cus_). You can also see the current one on the subscription’s details page next to the payment gateway name.

• payment profile ID: the identifier of the customer’s saved payment method inside the gateway (for Stripe, a payment method or card ID). With a Stripe data copy, customer IDs stay the same and payment method IDs change, so the new payment profile ID is typically the value that differs.

Step 1: Prepare your CSV file

Open Tools → Migrate Payment Gateway, then click File sample to download the template. Use the template exactly: the tool checks the header row on upload and shows “One or more header(s) not match with what system expect” if it differs. The template is semicolon (;) delimited and contains these columns:

• subscription ID

• old gateway ID

• old customer ID

• old payment profile ID

• new gateway ID

• new customer ID

• new payment profile ID

Fill in the old and new identifiers for each subscription, keyed by its PayKickstart subscription ID, using the new values your new gateway provided after the token transfer (for a Stripe copy, the new values come from the mapping file).

Step 2: Upload the CSV file

On the Migrate Payment Gateway screen, drag and drop or select your completed CSV under Upload CSV file, then click Next Step. PayKickstart validates the file, including that every subscription ID is valid and belongs to your account.

Step 3: Review the CSV file data

On the CSV file data step, PayKickstart shows the rows it read, a few records per page. Review every subscription and token carefully. If a row should not be migrated, use Remove record to take it out before confirming.

Step 4: Confirm and accept the disclaimer

On the Confirm data step, review the changes and accept the disclaimer (you must accept it before the migration can run). PayKickstart then updates the payment gateway and tokens on file for each subscription, one at a time, exactly as provided in your CSV. Each update is recorded in your event log, so you have a full audit trail of what changed.

After the migration

We always recommend checking your previous gateway account for any remaining active subscriptions, so customers are not billed in two places. Confirm that a few rebills process correctly through the new gateway before relying on it fully.

Good to know

• Test a small batch first. Validate that payments continue uninterrupted on a few subscriptions before migrating all of them.

• This tool re-points existing subscriptions only. It does not import new subscriptions (use Import Subscriptions) and does not export subscriptions out of PayKickstart.

• Accuracy is your responsibility. PayKickstart cannot be held liable for mismatched data (customers, products, gateways, payment dates, or subscription status). Subscriptions cannot be deleted once charged.

• You can cancel before confirming. Up until you confirm, you can cancel the migration and start over with a corrected file.

Related

• Importing Active Existing Subscriptions into PayKickstart

• Switching Campaign Payment Gateways

• Migrating Your Existing Stripe Customers to Connect+

If you have any questions about the Migrate Payment Gateway tool, reach out to our support team via live chat or at support@paykickstart.com, and we would be happy to help.