Migrate to Advanced Billing

Move your existing customers, subscriptions, and card data into Advanced Billing from another billing system or legacy vault. Our support staff is trained to assist with migrations from a number of systems.

Migration from legacy systems

To get started, submit a migration request by contacting support@maxio.com or submitting a request while logged into the application to indicate you wish to migrate your data to Advanced Billing.

Include the following information:

• Name of the system you're migrating from
• How many active paying customers you need to import
• How many canceled (inactive) customers you need to import
• Where the credit card data is currently stored (legacy system vault or payment gateway)

Once we receive your request, we reply with additional details and instructions tailored to your specific needs.

The migration process is slightly different for each legacy system.

Configure and test your Advanced Billing account

Set up your Advanced Billing account and confirm your payment gateway connection works as expected:

1. Inside Advanced Billing, set up your products, components, coupons, and settings (email notifications, dunning strategy, churn reason codes, etc.).
2. Thoroughly test your Advanced Billing setup against the Advanced Billing test gateway while your site is in test mode to ensure it's configured properly and ready to go live.
3. Clone your test site. You may want to change the subdomain of your test site before cloning, since each subdomain must be unique and can't be reused for the production site.
4. Enter your live payment gateway credentials into your production site under Settings > Payment Gateway and perform a test transaction to ensure transactions process successfully with no errors.
5. Switch your production site to live mode. To change a site from test to live mode, it must not have any active subscriptions. Cancel each individual subscription, or clear test site data using the Clear Data button.

Import customers, subscriptions, and card data into Advanced Billing

Once the Advanced Billing account setup is complete, you can begin importing your subscribers and credit card data. Advanced Billing offers the ability to import via CSV file or Subscriptions API.

• If the card data is already stored in an Advanced Billing-supported payment gateway: obtain an export of your subscription data, including gateway vault tokens for each subscription, then format the data using the Advanced Billing provided CSV file or Subscriptions API for import.
• If the card data is stored in an unsupported gateway: you have the option of switching to an Advanced Billing supported payment gateway, or submit a request to add support for your gateway. Submit a gateway support request by emailing support@maxio.com or submitting a request while logged into the application. We track all requests to gauge user demand and may add support for a payment gateway if multiple merchants request it or, in some cases, for an additional one-time fee.
• If the legacy system you're migrating from has its own vault: your customers' credit card data is stored in the legacy system's vault rather than your payment gateway. You need to have the data exported from the legacy system and imported to an Advanced Billing supported payment gateway. Then obtain an export of your subscription data, including new gateway vault tokens for each subscription, and format the data using the Advanced Billing provided CSV file or Subscriptions API for import.

Cost

Migration pricing depends on your import method:

• Self-service CSV or API import: free of charge
• CSV import assistance: $150/hour
• API import assistance: $250/hour

Migration FAQs

How much time will the process take?

Migration time varies for each import, so we can't provide a definitive timeframe. This depends on the speed at which your legacy system can export subscription data, whether your card data is currently stored in a payment gateway already supported by Advanced Billing, the format of the data provided, how many subscriptions you're importing, and whether you need Advanced Billing developer assistance or are importing on your own.

Can I import my data to a test account?

We don't recommend importing live subscriptions into a site in test mode. To switch an Advanced Billing site from test to live mode, you can't have any active subscriptions. Since Advanced Billing imports subscriptions in an active state, you need to cancel all active subscriptions before updating to live mode and then reactivate them. This causes changes in next renewal dates and affects the customer's statement(s).

Can I import historical transactions?

Advanced Billing can't import transaction data.

Can I set an expiration date during import?

Yes. If your products expire, you can specify the expires_at timestamp at the time of import using the CSV import method, or the Subscriptions Override API after the subscription is created.

Can I import canceled subscriptions?

Yes, see the CSV import documentation or the API import documentation, depending on your import method.

Will my customers be charged right away when I import?

You can specify a next billing date during import to delay the first renewal, or set the next billing date to NOW to process immediately. For more information, see the Import Subscriptions from a CSV documentation.

Is there a chance my customers will be double billed?

Coordinate disabling renewals and new signups in your legacy system during the import process.

Will my customers receive email notifications when I import them to Advanced Billing?

You can turn off email notifications during import, under Settings > Emails, to avoid sending any communication. If you have Billing Portal (Settings > Billing Portal), Statement (Settings > Statements), or Invoice (Settings > Invoice Billing) emails enabled, you may also want to turn those off.

Advanced Billing never sends emails for imported canceled subscriptions.

Will signup_success webhooks be generated when I import my customers to Advanced Billing?

Yes, if enabled, Advanced Billing generates a signup_success webhook for each imported subscription. The subscription's status is either active or canceled, depending on how it was imported. When acting on the webhook, adjust your internal logic based on this status.