easysubscription.io

Support Help

How can we help ?

Migrate from Authorize.net

4 min read


Overview

Merchants moving off Authorize.net for recurring billing can migrate existing subscription contracts to Shopify using Easy Subscriptions. If Shopify Payments is your primary gateway, Authorize.net connects as a secondary gateway so it can keep billing existing contracts while new and updated subscriptions bill through Shopify Payments.

This guide assumes you have already completed Shopify’s core Subscriptions API migration. If you have not, complete that step first, since the Authorize.net specific process described here depends on it.

Before starting, pause billing in your current subscription app. Pausing prevents customers from being charged twice while payment methods and contracts are being transferred.

Step by Step Migration Guide

Step 1: Connect Authorize.net as a Secondary Payment Gateway

Unlike Braintree, Authorize.net does not connect through OAuth. Instead, you need your Authorize.net API Login ID and Transaction Key on hand. Go to the following URL, replacing {shop} with your Shopify store name:

https://admin.shopify.com/store/{shop}/settings/payments/third-party-providers/44859393?secondarySubscriptionGateway=true

Enter your API Login ID and Transaction Key when prompted. Once verified, you return to Shopify’s payment settings and a confirmation banner confirms the connection succeeded.

Step 2: Open Easy Subscriptions

From Shopify admin, go to Apps, then Easy Subscriptions.

Step 3: Go to Import Settings

Inside Easy Subscriptions, click Settings, then find the Import Subscription section.

Step 4: Download the CSV Template

Click Download to get the sample CSV file. This template defines the exact column structure Easy Subscriptions requires for import.

Step 5: Export Existing Subscription Data

Export subscription data from your current Authorize.net connected app. Include customer details, product names, billing intervals, and cycle dates.

Step 6: Format the CSV File

Match your exported data to the sample template’s columns, including Subscription ID, product details, and payment intervals. Map each field carefully, since mismatched columns are the most common cause of failed imports.

Step 7: Import the Data to Shopify

Return to the Import Subscription section in Easy Subscriptions and upload the completed CSV. Processing time depends on how many subscribers you are importing.

Step 8: Review the Import Logs

Download the Import Logs to confirm the import completed correctly. Missing or mismatched entries appear here so you can fix and re-import them.

Step 9: Resume Billing

Once the import log confirms a clean migration, reactivate billing. Recurring orders are now manageable directly from Shopify admin through Easy Subscriptions.

Tips for a Smooth Migration

  • Keep billing paused until the import log confirms a clean migration.
  • Have your API Login ID and Transaction Key ready before starting Step 1, since the connection cannot be verified without them.
  • Use a fresh copy of the CSV template each time, since Easy Subscriptions may update the required format.
  • Review import logs closely, since a single mismatched column can affect many rows at once.
  • Contact support if import logs show unresolved errors after a re-import attempt.

Frequently Asked Questions

What do I need before connecting Authorize.net to Shopify?

You need your Authorize.net API Login ID and Transaction Key. These are required to verify and authorize the secondary gateway connection.

Do I need Shopify Payments to migrate from Authorize.net?

If Shopify Payments is your primary gateway, Authorize.net connects as a secondary gateway to keep billing existing contracts. New and updated subscriptions bill through Shopify Payments going forward.

What happens if a customer’s Authorize.net payment method ID is missing?

Shopify uses that customer’s default payment source instead. Migration is not blocked by a missing payment method ID.

Will my customers be double billed during migration?

Only if billing is not paused beforehand. Pause billing in your current app before starting the CSV import, and do not resume it until the import logs confirm a clean import.

What happens if some subscriptions fail to import?

The Import Logs flag exactly which rows failed and why. Most failures are formatting mismatches with the CSV template. Fix the flagged rows and re-upload the file.

How long does the migration take?

Connecting the payment gateway and preparing the CSV file typically takes under an hour. Import processing time depends on subscriber volume.

Latest Improvements

Browse Articles