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.
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 |
|---|---|---|
| Customers | Customers | Name, email, address, tax ids, your own customer id kept as the external id |
| Products and components | Products and prices | One product, many prices: currency, billing period and pricing model per price |
| Subscriptions | Subscriptions | With their renewal dates, so nobody is charged early or twice |
| Invoices and invoice line items | Invoices | Historical, marked as imported; they never email your customers |
| Transactions | Payments | Recorded against the imported invoices |
| Credit notes | Credit notes | Historical, against the imported invoices |
| Saved cards | Saved payment methods | As token references from your payment gateway, never card numbers |
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 a second run updates instead of duplicating. What you can import.
4. The cutover, in five steps
- 01Export
Run the Maxio exports above, on the day you are ready to import them.
- 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
Turn charging on at a renewal boundary and stop Maxio charging the same day.
Questions teams ask
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.
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.
Could someone be charged twice while both systems run?
Not if the renewal dates come across, which the import keeps. Run yRecurring in test mode beside the old platform for one cycle, compare the invoices, then switch charging on at a renewal boundary and turn the old platform's charging off the same day.
How long does a migration take?
A catalog of a few plans and a few hundred customers is an afternoon: export, dry run, import, one test invoice. The saved cards decide the rest, and that depends on whether your current platform holds them or your gateway does.
Can you do the migration for us?
Yes. Book a demo and bring your export; we import it live with you on the call, so you leave with a working environment on your own data.
Bring your Maxio export to a call.
We import it live with you, dry run first, so you leave with a working environment on your own data. Or start the trial and run the import yourself; it is built for that.