The single biggest reason ISPs stay on an aging billing system is fear of the migration. Nobody wants to risk their subscriber database or knock customers offline. So we built the SAS4 importer to be boring and safe — and we tested it on a real production database of 294,000 subscribers.
What gets migrated
- Subscribers — usernames, passwords, contact details, status and expiry.
- Profiles / packages — your speed plans and their attributes.
- Managers / resellers — the reseller tree and permissions.
- Balances — reseller wallets and subscriber balances, so accounting stays intact.
How the import works
You point ISP Boost at a copy of your SAS4 database. It reads the tables it recognises, maps them onto ISP Boost's schema, and loads everything in batches. Because you import from a copy, your live SAS4 system keeps running untouched while you verify the result — there's no risky in-place conversion.
Tested at scale. The importer was validated on a real 294K-subscriber SAS4 dump — so it's proven on production-sized data, not just a demo.
Keeping customers online
Your customers authenticate against your NAS (MikroTik and others). During migration your existing setup keeps serving them. When you're ready to cut over, you re-point the NAS shared secret / RADIUS server to ISP Boost — the subscriber records are already there, so logins keep working. No mass password reset, no bulk re-provisioning. See the MikroTik + FreeRADIUS guide for the RADIUS side.
The migration in 4 steps
- Install ISP Boost on a fresh server (one command).
- Export a copy of your SAS4 database.
- Run the importer and review the imported subscribers, profiles, managers and balances.
- Cut over — point your NAS at ISP Boost when you're happy. Customers stay online.
Migration shouldn't be a leap of faith. Import from a copy, verify, then cut over on your schedule.
Already comparing platforms? See ISP Boost vs SAS4 / SAS Radius or the full 2026 roundup.
