API integration makes migration safer
ISPs using Splynx should be able to evaluate ISPAgents without manually duplicating every record. API integration can support coexistence while the operator validates customer data, service identifiers, balances, payments, and access control behavior.
What to synchronize
| Data | Why it matters | |---|---| | Customers | Support and finance need reliable names, contacts, account state, and location. | | Services | Access workflows depend on the right plan, service identifier, NAS, router, and policy. | | Invoices and balances | Finance must reconcile old and new systems during migration. | | Payments | Restoration and collection actions need clear payment evidence. | | RADIUS and router mapping | Access automation needs accurate user, NAS, policy, queue, or address-list references. |
Coexistence workflow
Start read-only, import the baseline, compare counts and balances, then run a single controlled workflow such as paid restoration. Expand only after the team can explain every difference.
FAQ
Is API integration required for every migration?
No. CSV and Excel may be enough for smaller migrations. API integration is useful when the ISP needs coexistence or repeated sync during testing.
What should not be automated first?
Avoid high-risk access changes until identifiers, policies, balances, and rollback steps are verified.