Maxio and SaaSOptics
Monk imports your existing customers, invoices, payments, and credits from Maxio Advanced Billing (formerly Chargify) and SaaSOptics so you can move billing and collections to Monk without losing history or open balances. Both are run as a guided migration by the Monk team, with a dry run before any data is written.Supported entities
Authentication
- Maxio: an API key and your Maxio subdomain.
- SaaSOptics: an API token and your SaaSOptics account ID.
- Credentials are used only for the duration of the migration and are stored encrypted while it runs.
Multi-entity, currency, and parent-child
- Entities: Each Maxio site or SaaSOptics account is migrated into one Monk org. Run additional migrations for additional sites or accounts.
- Currency: Invoice, line, and payment amounts are stored exactly as the source reports them, in the source currency. Monk does not recalculate invoice totals.
- Paid history: Invoices already paid in the source arrive in Monk as paid, so historical collections activity is not re-triggered.
- Customer hierarchy: Customers are imported as top-level accounts.
Configuration options
- Dry run: preview what will be created, updated, or skipped before committing.
- Status filter: import only open invoices, or open and paid history.
- Invoice selection: scope a SaaSOptics migration to a specific list of invoice numbers.
- Pricing mapping: map source products and price points to Monk catalog items.
Sync and reliability
- Migrations are idempotent: records are keyed on their source IDs, so re-running a migration skips anything already imported instead of creating duplicates.
- Each run produces a summary of created, updated, and skipped records.