Most providers already run a system. Moving shouldn't mean a weekend of downtime.
Import
Customers, plans, balances and invoices from a CSV export. The import wizard maps the columns.
Run side by side
Connect one site first. Watch payments activate customers there while the rest of your network stays on the old system.
Move routers one at a time
Each router is one connection. Move them in batches or individually — roll back any router at any time.
Go live when the numbers match
Collections and active-customer totals reconcile across both systems. Then retire the old one.
A named migration engineer
One person assigned to your move, from import to go-live.
A reconciliation report
Before you retire the old system, a side-by-side comparison of active customers and collections.
Move at your own pace
No weekend cut-overs. Run both systems as long as you need.
Splynx
What moves, field mapping, timeline and what to check.
UISP
Customers, sites and devices — what transfers and what to watch for.
MikroTik User Manager
Profiles, users and limitations — from User Manager to plan-based billing.
Mikhmon
Vouchers, users and hotspot profiles — what changes when you move.
Another system
Spreadsheets, a free tool or something else — tell us what you run and we will map the move.
Most providers finish within two to three weeks. Small networks with fewer than five routers often finish in days.
No. You move routers one at a time while both systems run. Customers stay online throughout.
CSV. Export customers, plans and balances from your current system — the import wizard maps the columns.
Yes. Each router is moved independently. Disconnect it from DataRadius and it returns to your previous setup.
Yes. Every account includes a named migration engineer who reviews your import and answers questions throughout.
Point your payment callbacks to DataRadius when you are ready. Existing payment methods and accounts carry over.