Move your existing PPPoE customers into ISPMan

Use this walkthrough when you already have PPPoE subscribers, whether in a spreadsheet, another billing system or just as PPP secrets on a MikroTik, and you want ISPMan to manage their billing and authentication.

The aim is a switch-over where nobody loses service: the packages exist first, the customers come in with their current expiry dates, and only then does the router start authenticating against ISPMan.

Step 1: Onboard the router

If the PPPoE router isn’t in ISPMan yet, add and onboard it first. Go to Devices → All Devices → Add, then use Script on the device page. Launch a new hotspot from zero covers this in Steps 1–2. Wait until the device page shows the online-only buttons.

Step 2: Recreate your packages

Go to Services → PPPoEs → Packages and create one package for each plan you sell today. Match the speeds (Upload Speed (Mbps), Download Speed (Mbps)), the Price and the validity (Expires After / Expires After Value, for example 1 month).

Step 3: Build the import file

The importer takes a CSV or Excel (.xlsx) file with a header row. The supported columns are:

Column	Notes
`name`, `email`, `phone_number`	Customer contact details. Use a phone number if you want SMS reminders to work.
`username`, `password`	The PPPoE credentials the customer’s router dials with. Keep them identical to the old system so the CPE needs no changes.
`account_number`	The account the customer pays to.
`package_id` or `package_name`	Must match a package from Step 2.
`device_id`	The router the customer connects through.
`paid_until`	Current expiry, as `YYYY-MM-DD`.
`assigned_ip_address`	Optional fixed IP.
`is_active`	`true` / `false`.
`negotiated_price`, `is_free`	A special price for this customer, or `free`.
`branch` / `branch_id`	Optional, if you use branches.

Let the Assistant do the work. If your customers live on a MikroTik, a spreadsheet, or both, open Assistant and ask it to prepare a PPPoE customer import. It can read the router’s PPPoE secrets, combine them with your spreadsheet (matched on username), match profiles to your packages, and give you back a file ready to import. It doesn’t import anything by itself, so you get to review the file first.

Step 4: Import

Go to Services → PPPoEs and click import.
In Import PPPoE Customers, upload the file under Upload customer file (CSV or Excel) or paste the CSV text.
If every customer shares the same values, you can set Paid Until for All Customers, Device for All Customers or Package for All Customers rather than putting them in the file.
Submit. You’ll see Imported N PPPoE customers successfully. If any rows fail, you’ll see Import failed: … errors with a summary. Fix those rows and import them again.

Step 5: Switch the router over

On the device page, click + PPPoE to create the PPPoE server (Server Name, interface and network). If you’d rather run the setup yourself, More → PPPoE Server Script generates a ready-to-run RouterOS script that you can copy or download.
Pick one test customer. Have them redial (or disable and re-enable their PPP client), then check PPPoE → Auth Logs. You want to see an Access-Accept.
Once the test works, disconnect the remaining sessions in small batches so they redial against ISPMan.

Step 6: Check and tidy up

PPPoE → Auth Logs: look for Access-Reject rows. The Reason column tells you whether it was a wrong password, an unknown username or an expired account. See PPPoE customer can’t connect.
PPPoE → Sessions: the online count should climb back to roughly what you had before.
Settings → PPPoE Network and the PPPoE Authentication Policies card in Settings: decide whether to enforce MAC binding and passwords now, or after everyone has connected at least once.