Migrate from spreadsheets to ISPAgents
Prepare customer and service records for a guided migration pilot. Clean your spreadsheet, map every plan and keep finance and network changes under separate review.
Review before importing
Start with a customer list your team trusts
When customer names live in Excel, plan changes arrive in chat and receipts sit in another sheet, agree who owns each fact before uploading anything. Preserve the original files. Build one reviewed working copy with stable customer and service references, and resolve conflicting names, status notes and plan labels with the team.
Use the free ISP migration checklist to record owners, source systems, cutoff time and rollback decisions. If some records come from Splynx, also use the Splynx migration worksheet.
Keep chat archives with your existing access controls. Copy only relevant customer and payment references into the worksheet; do not upload entire conversations as a customer import. A chat screenshot alone does not establish a verified payment or the right customer.
Clean the working copy before choosing an import format
Use French or English labels that your team understands while cleaning the source. Keep a mapping from each source label to the field agreed with the pilot owner. Ask for the pilot template before converting this working copy; the suggestions below are preparation categories, not accepted product headers.
| Information to review | Preparation task |
|---|---|
| Customer reference and name | Preserve the original reference and resolve duplicate or conflicting records. |
| Phone and country | Check country codes and formatting with the record owner; retain the source value for comparison. |
| Service reference and access identity | Preserve the existing PPPoE username or MAC where relevant, without copying passwords. |
| Source plan label | Map every distinct label, including blank and retired plans, to an agreed destination plan. |
| Service address or installation location | Have operations verify the location and identify uncertain entries. |
| Service status | Agree the meaning of each source status; do not guess how it maps to a destination state. |
Preserve the original workbook and review formulas before exporting values. Check that CSV export retains leading zeros, accented names and identifiers, and that delimiters and quoting keep each value in its intended column. Review the agreed format with the pilot owner using a small, access-controlled sample.
Phone formatting does not prove ownership, delivery or messaging consent. A shared number or matching name alone is not enough to merge two customer accounts.
Map every source plan before the pilot
Create a mapping sheet with the source label, intended destination plan, owner and decision. Check price, currency, billing interval and upload/download rates with finance and operations. Resolve missing or ambiguous labels instead of assigning an arbitrary default.
Keep catalog edits and changes to existing services on a separate approved work list. Agree who may make those changes and when the mapping must be reviewed again. Preserve the original labels so the team can explain each decision later.
A service linked to a catalog plan is not proof that its bandwidth policy has reached a router. Review subscriber management and ISP billing scope separately.
Agree the validation and reconciliation checks
Before the pilot, ask its owner which checks the agreed flow performs and which require manual review. Use this worksheet to record the evidence your team needs; it is not a list of automatic ISPAgents validations.
| Operator check | Evidence to retain |
|---|---|
| Completeness and CSV structure | Required information agreed with the pilot owner; reviewed sample export. |
| Identity stability and duplicates | Source-to-destination customer and service references, with decisions on conflicts. |
| Phone, address and status | Record-owner review and an exception list for uncertain values. |
| Plan mapping | Approved source-label mapping and review of resulting service associations. |
| Result reconciliation | Counts of attempted, accepted, rejected and linked records where reported, with unresolved exceptions. |
Agree how results and rejected records will be retained before starting. Keep customer information access-controlled. Compare the outcome with the source copy and retain any job reference provided by the pilot owner.
Keep identities stable when correcting records. Distinguish newly created records from links to existing records so that neither duplicates nor missing customers disappear inside an aggregate total. Review the actual results before retrying.
Keep credentials out of working spreadsheets
Never put PPPoE passwords, RADIUS shared secrets or router administration credentials in the CSV, messaging apps, screenshots or support tickets. Identify the credential owner and agree a separate approved credential-handling process before any access work.
An access identifier is not proof that authentication works. Existing FreeRADIUS, Managed RADIUS and MikroTik operations remain guided pilot paths with separate qualification. Customer preparation is not authorization to rotate credentials, provision routers or change access.
Keep separate owners for finance, devices and communications
- Chat history: extract essential facts manually and have their owner verify them. Preserve conversation records under the team's existing access controls; do not assume a customer import moves chat history.
- Finance: reconcile opening balances, unpaid invoices, receipts, credits and deposits in the current system. Agree any finance migration separately. ISP customer billing foundations remain a guided pilot.
- Devices: verify serials, subscriber associations, sites, router inventory and configuration backups separately. An identifier in a spreadsheet is not evidence of enrollment or provisioning.
- Access, payments and messages: keep each workflow under its existing owner until a separate pilot has been rehearsed and approved.
- Exceptions and recovery: resolve source conflicts with their owners. Ask how partial results and retries are handled; do not assume a failed batch has undone earlier writes.
Payment-provider clients and WhatsApp/SMS delivery remain roadmap pending provider qualification. Keep your current payment instructions and reminder process until a separately scoped workflow is proven. Review mobile-money pilot readiness and WhatsApp integration roadmap. For UISP records, use the UISP CRM migration worksheet.
Rehearse, reconcile, then decide on cutover
Agree a small representative sample while the existing customer, finance and access systems remain authoritative. Include incomplete records, duplicate identities and ambiguous plans so the team can rehearse exception handling. Increase the scope only after customer/service counts and plan associations match the reviewed source.
Before cutover, record a freeze window or a delta log for payments and record edits. Keep the old access path available, name a recovery owner and agree stop conditions. If a check fails, pause further changes and reconcile the outcome before retrying.
There is no fixed migration duration: data cleanup, plan decisions and exception review determine the schedule. The cutover and rollback checklist gives your team the evidence to make that decision.
Frequently asked questions
How should I prepare French or English spreadsheets?
Use clear labels your team understands in the working copy. Ask the pilot owner to provide the agreed template and explain its required fields before converting the data. The preparation columns below are not accepted ISPAgents import headers.
Does a customer migration prove that balances and access are correct?
No. Finance must reconcile balances and payment evidence separately, and operations must verify the approved access path. A reviewed customer record is not evidence that a payment settled or a subscriber can authenticate.
What should I do with chat notes and workbook formulas?
Have the record owner turn relevant chat notes into verified facts. Preserve the original workbook, review calculated values and prepare a separate working copy. Agree the destination format with the pilot owner.
Download the ISP migration checklist.
Use it before a vendor comparison call to audit customer data, billing state, access mappings, payment rules, and cutover readiness.
Invoices, balances, statements, credits, refunds, deposits
RADIUS, MikroTik, CPE, connector, approval, rollback
Jobs, photos, GPS, signatures, equipment used
Imports, API sync, validation, reconciliation, cutover
Continue the operations map.
Splynx Migration
Guided pilot: External references, import preview/apply jobs, connector profiles, and sync-run records are foundations for a guided pilot. Live UISP and Splynx adapters still require implementation.
Open pageMigrationMigrate from Splynx to ISPAgents
Guided pilot: External references, import preview/apply jobs, connector profiles, and sync-run records are foundations for a guided pilot. Live UISP and Splynx adapters still require implementation.
Open pageSolutionsAutomatic Internet Suspension Software — Guided pilot
Guided pilot: Preview, queued jobs, approvals, result recording, and a mock-safe worker can be evaluated in a guided pilot. Live router/RADIUS mutation remains gated; automated suspension and restoration are not a shipped promise.
Open pageSolutionsCustomer Self-Service Foundations — Guided pilot
Guided pilot: Field-job lifecycle, serialized stock, basic tickets and subscriber portal flows have narrow synthetic-data proof and remain guided pilots. Physical installs and invite email delivery are unproven. The technician PWA, dispatch board, dedicated stock workspace and IPAM remain roadmap.
Open page