How to bring data over from an old system

Who does this

ISP administrator (screens) and the server operator (command line)

Permission

Add subscribers (subscriber import), Add packages (package import), Add and change routers, setup scripts (router import); command line needs server access

Steps

1. Subscribers: Subscribers → Import. Download Download a sample file, fill it (CSV or Excel, up to 5,000 rows, first row names the columns), choose Import type = Add new subscribers or Update existing subscribers, optionally a Partner, upload and click Check the file.

   Nothing is saved until you confirm: the next page shows Ready to import and Rows with problems. Imported expiry dates are set as already paid (no invoices); subscribers without an expiry stay not activated.

2. Packages and policies: Packages → Import and Policies import accept CSV exports.

   Both have export buttons for backup.

3. From a router: on the router's page open Import from router. Tabs read the router's PPP profiles (turn them into packages and policies, typing a price for each new package), IP pools and PPPoE users, then click Import ticked profiles and so on.

   Reads only; nothing on the router changes. Ticked rows are saved together or not at all, and it can be run again safely.

4. Whole system: the server operator can import a full backup of another billing system with 'isp import-old-radius --file <backup.sql.gz> --isp <code>' (a dry run unless --apply is added; --steps picks steps), and isp import-django for the Django-based predecessor.

   Imported customers sign in with their old password and are asked to choose a new one. Use Settings → Billing → Pause automatic billing during the transition.

5. Check the result in Logs and reports → Failed imports.

   Rows that failed are listed with the reason.

Good to know

• Always run the command line import as a dry run first.
• Platform → Move subscribers moves customers between ISPs inside saRa.