A billing migration is an operations migration
Moving away from Splynx is not only a data export. The migration touches customers, services, invoices, balances, payments, RADIUS usernames, MikroTik rules, support history, inventory, and the daily habits of finance and support teams.
The safest ISPAgents migration path is designed around coexistence. Import the data, connect the network, prove selected workflows, then move more ownership after the operator sees evidence.
Migration scope
| Data or workflow | What to verify | |---|---| | Customers | Names, contacts, billing address, service location, status, and account owner. | | Services | Plan, speed, package, IP assignment, router or NAS, and installation state. | | Finance | Balances, unpaid invoices, deposits, credits, refunds, tax, and statements. | | Access control | RADIUS username, PPPoE identity, static IP, DHCP lease, MikroTik queue, or address list. | | Support | Open tickets, customer notes, escalation state, and recent outage context. | | Inventory | Assigned CPE, router, ONT, antenna, serial number, warehouse stock, and technician stock. |
Cutover phases
| Phase | Outcome | |---|---| | Audit | Confirm what data exists in Splynx, UISP, MikroTik, FreeRADIUS, spreadsheets, and payment systems. | | Import | Load customers, services, plans, balances, and identifiers into ISPAgents. | | Connect | Attach payment providers, MikroTik routers, FreeRADIUS, UISP, and custom agents. | | Parallel run | Run one or two workflows in parallel, such as paid restore or overdue suspension. | | Finance signoff | Reconcile statements, balances, deposits, credits, and payment evidence. | | Operational cutover | Let support, finance, NOC, and technicians work from ISPAgents. |
What makes the migration credible
- Every imported customer has an owner, service state, and access identifier.
- Every active plan maps to a network policy.
- Every overdue account produces a preview before suspension.
- Every payment has reconciliation evidence.
- Every high-risk change has approval, audit trail, and rollback notes.
- Every team has a role-specific dashboard before cutover.
FAQ
Can a Splynx migration happen without downtime?
The target should be no customer-impacting downtime. ISPAgents should run in parallel first, then cut over controlled workflows only after billing, access, and support teams validate the result.
Should we use API, CSV, or both?
Use both when needed. API-based migration can keep records current during testing, while CSV and Excel imports help recover custom fields, finance exports, and operational data that lives outside the main system.