Move from Maxio to yRecurring.
Maxio's exports arrive by email and in-app notification when they are ready, and it stores no card data of its own, so the cards are already in your gateway. The move is the CSVs, a dry run and one parallel cycle.
See how Maxio and yRecurring compare →What is different about leaving Maxio
Product families dissolve into one catalog
Maxio groups products and their components in product families, and a component only works with products in its own family. yRecurring has one catalog; add-on compatibility rules say which plans each add-on goes with, which covers what the family boundary did.
Every price point becomes a price
A Maxio product or component can have several price points. Each becomes its own yRecurring price, so customers on an older price point stay on exactly what they pay today.
Components change shape
Quantity-based components become add-ons with a per unit price, on/off components become add-ons with a flat price, and metered or event-based components become metered prices on a meter, built in the app.
1. Export from Maxio
The Export button above each list: Billing, then Subscriptions, Customers or Transactions; export settings under Config, then Settings, then CSV Exports.
- Subscriptions
- Customers
- Transactions
- Products and components
- Invoice line items
As documented by Maxio on 24 September 2026: their export guide.
2. Saved cards
Maxio stores no card numbers; the vault is your gateway's. Connect the same gateway to yRecurring and import the saved payment methods as token references. If you also want to change gateways, Maxio's FAQ says to work with the gateway directly to export the vault; do the platform move first and the gateway move later, if at all.
Source: Maxio documentation, read 24 September 2026. How yRecurring imports them: migrating saved payment methods.
3. What carries over
| In Maxio | In yRecurring | Notes |
|---|---|---|
| Customer: reference, email, organization, address, VAT number | Customer The reference, if you set one, is the natural external id; otherwise the Maxio customer id. | The reference, if you set one, is the natural external id; otherwise the Maxio customer id. |
| Product, in its product family | Product, kind plan The family name can go into the product name if you sell the same plan in several families. | The family name can go into the product name if you sell the same plan in several families. |
| Product price point | Price One price per price point. | One price per price point. |
| Quantity-based or on/off component | Product, kind add-on Per unit or flat price; attached to subscriptions after the import. | Per unit or flat price; attached to subscriptions after the import. |
| Metered or event-based component | Meter and metered price Built in the app; usage flows from the next period. | Built in the app; usage flows from the next period. |
| Subscription: product, state, current period start and end, next assessment | Subscription The next assessment date becomes the next billing date. | The next assessment date becomes the next billing date. |
| Invoice and invoice line items | Invoice Historical, one summary line with the total; the line items stay in the export. | Historical, one summary line with the total; the line items stay in the export. |
| Transaction of type payment | Payment Recorded against its invoice. | Recorded against its invoice. |
| Payment profile | Saved payment method The vault token in your gateway, with brand, last four and expiry. | The vault token in your gateway, with brand, last four and expiry. |
Records go in dependency order: customers and catalog, then subscriptions, then invoices and the payments that settle them. Each row keeps your old system's id, so running a file again skips what is already there instead of copying it; customers, products and prices can be set to update instead. What you can import.
What stays in Maxio, and what to do instead
They stay in your accounting tool. yRecurring sends invoices, payments and credit notes to QuickBooks or Xero from Grow, or exports them as CSV.
Attach the add-ons, with their quantities, to each subscription in the app after the import and before the parallel cycle.
Model a committed quantity as an add-on at that quantity, or as a prepaid wallet if customers draw it down; check the first test invoice either way.
Maxio's metrics history stays in Maxio. Export the reports you want to keep before the account closes.
4. The cutover, in five steps
- 01Export
Export subscriptions, customers and transactions from the Billing lists, then products and components; the files arrive by email.
- 02Connect
Start the free trial and connect the same payment account you charge through today.
- 03Dry run
Upload the files. The import maps the columns, cleans the values, and shows every row it would create before it writes one.
- 04Parallel cycle
Run one billing cycle in test mode beside Maxio and compare the invoices line by line.
- 05Switch
At a renewal, turn charging on here and cancel the Maxio subscriptions at the end of their current period.
Questions about leaving Maxio
See how Maxio and yRecurring compare → What you pay today, next to a flat plan: the fee calculator →
What about revenue recognition schedules?
They stay in your accounting tool. yRecurring exports invoices, payments and credit notes in open formats for it; it does not produce recognition schedules itself.
Our gateway is Authorize.Net. Can the cards be fetched directly?
Yes. Authorize.Net is one of the gateways yRecurring reads directly, with Stripe, GoCardless and Paystack: connect the same account and fetch the saved customer profiles. Cards in Braintree or Adyen come in by file upload of the vault tokens.
Will my customers get emails during the import?
No. Imported invoices, payments and subscriptions are historical records; the importer never sends a customer email for them. The first message a customer gets from yRecurring is the first invoice or receipt you choose to send.