Free operator worksheet

ISP migration checklist

Prepare a controlled ISP or WISP migration, from customer records to cutover and rollback. Copy or print this checklist; no email or account is required.

Tick items here or print a blank copy. Ticks stay on this page until you reload; they are not saved or sent. Use Print / save PDF to keep your progress.

How to use this checklist

Copy this page into your team's working document or print it. Mark each item complete only when an owner has recorded evidence. These are operator preparation steps, not a promise that a destination platform automates them. For ISPAgents, customer import and billing foundations remain a guided pilot.

DecisionFill in before starting
Migration owner and backupName the people who can pause the work.
Pilot scopeList the customer IDs, sites and workflows included.
Authoritative recordsName the current customer, balance and access systems.
Change windowRecord the date, timezone and stop/go decision time.
Stop conditionsDefine unacceptable record mismatches, balance differences and access failures.
Recovery ownerRecord who can restore each source system and reconcile later changes.

1. Customers and source records

Starting with Excel or Google Sheets? Follow the spreadsheet migration guide for CSV preparation, plan-label mapping and reconciliation guidance. For an incumbent billing system, use the Splynx migration worksheet.

2. Plans and services

3. Balances and payment evidence

Agree any opening-balance or invoice-history migration separately with finance. Evaluate ISP billing foundations separately as a guided pilot; do not retire the current finance system based on a successful customer import.

4. Devices, routers and access identities

Use the subscriber management scope to separate available customer/device records from pilot workflows. ISPAgents MikroTik operations and RADIUS paths need their own guided pilot qualification.

5. RADIUS and PPPoE credential handling

6. Rehearsal and cutover day

7. Rollback and follow-up

A checklist is complete when its evidence is reviewed, not when the import button succeeds. Keep the spreadsheet playbook beside this worksheet during the pilot.

Continue with the FreeRADIUS readiness checklist, router access audit checklist, and UISP migration worksheet.

Can I use this checklist without an account?

Yes. Read, tick, print or save it as a PDF without signing up or providing an email. Ticks are not saved after a reload.

Can ISPAgents map any CSV export automatically?

No. CSV import has no column-mapping interface yet. Guided import is part of the pilot: agree the fields and prepare the file together before reviewing import preview/apply results.

Do I have to replace Splynx or UISP first?

No. Keep the current system authoritative while evaluating an agreed sample. ISPAgents coexistence and import foundations are a guided pilot; working live Splynx and UISP adapters remain roadmap.

Does a completed checklist authorize live cut-over?

No. It prepares a review. Live router/RADIUS changes remain gated; each proposed workflow needs proven adapter support, credential handling, monitoring, rollback evidence and operator approval.

Optional: discuss your checklist findings with an operator.