UISP CRM migration · Guided pilot

Migrate from UISP CRM to ISPAgents

Run beside UISP first. Review customer and service records in a guided pilot while your team keeps its existing billing and network workflow in control.

Review the migration path
Illustrative migration worksheet

Coexist first, migrate later

prepare
Export
guided pilot
Review
operator signoff
Decide
MapClients → customersReview
MapServices → servicesReview
KeepUISP network operationsIn place
Planning illustration, not a live sync or migration result. Site references and unsupported fields need manual review.
Page type
Migration
Primary search
migrate from UISP CRM to ISPAgents
Updated
2026-10-15

Start beside UISP CRM

If UISP already supports your daily work, start with a copy of an export. Keep UISP as the operating source of truth while your team reviews the sample in ISPAgents. Use the UISP CRM comparison and UISP integration scope to agree what the pilot will actually evaluate.

Map clients, services and sites before importing

This is a proposed mapping worksheet, not a guarantee that every source field has a supported import destination. The guided pilot confirms each destination before applying records.

Source informationProposed ISPAgents destinationReview before applying
UISP client ID, name and contact detailsCustomer record with a stable external referencePreserve the source ID; resolve duplicates and shared phone numbers.
Service ID, client link, plan and statusService linked to the reviewed customerConfirm plan names, billing periods and customer ownership; do not infer an access policy.
Site ID, name and service locationCustomer/service site reference where supportedReview site associations manually. Keep unsupported site fields in the mapping worksheet; no automatic site import is promised.
PPPoE username and router/NAS labelAccess-identity mapping for pilot reviewMatch the correct service. Keep passwords and shared secrets out of exports.
Balances, invoices and payment referencesReconciliation worksheet firstKeep finance authoritative in UISP until the operator validates the scoped billing foundation.

What moves now, and what waits

Guided pilot now: review customer/service records, external references and import preview/apply results using the partial CRM and Customer 360 foundation. Connector profiles and sync-run records are foundations, not proof of working live sync.

Keep in UISP during the pilot: network monitoring, provisioning, device configuration and your existing access-control process. Keep billing, collections and customer communications on their current workflow unless a separate, tested scope is approved. Read-only export review does not change subscriber access.

Later, after separate proof: live UISP sync/write-back needs implementation. ISPAgents customer billing is a guided pilot foundation; AR aging and a USD statement read have narrow proof, while tax and refunds remain unqualified. Live payment-to-access changes remain gated. Moving a record does not enable those workflows.

Cutover gates and rollback

  1. Save a dated source export and record who owns each field and workflow.
  2. Clean duplicate IDs, missing contacts, inconsistent plan names and ambiguous site links.
  3. Review a small sample: expected customers, service links, rejected rows and unsupported fields.
  4. During parallel review, keep updates in UISP and log changes for a fresh, reviewed export. Do not assume automatic synchronization.
  5. Before any cutover, reconcile records and finance evidence, assign an owner, and document the exact workflow being transferred.
  6. If validation fails, stop applying records and continue operating in UISP. Retain the export and import-job evidence; agree manual correction or cleanup with the pilot team. Do not assume one-click import rollback.

The timeline follows these gates. Set review dates after the sample reveals cleanup effort; there is no promised completion time or zero-downtime guarantee.

For the assessment, bring a sanitized column list and the workflow you want to move first. Use the migration planning guide to prepare, then book a migration assessment through the page CTA.

Frequently asked questions

Can ISPAgents sync directly with UISP CRM today?

No live UISP adapter is claimed. External references, import preview/apply jobs, connector profiles and sync-run records are guided pilot foundations. Start with a reviewed export; automatic sync and write-back require further implementation.

Can I upload an ordinary UISP CSV export without preparation?

CSV import has no source-column mapping step yet. The guided pilot must manually align export headers and rows with accepted CRM fields before preview. Keep stable source IDs and resolve rejected rows before applying the sample.

Does the pilot replace UISP Network?

No. Keep your current network management, monitoring, provisioning and access-control workflow in place. A customer-record pilot does not authorize network changes or promise a network migration.

How long does a UISP CRM migration take?

There is no fixed migration deadline. Agree the schedule after reviewing export quality, unsupported fields and reconciliation work. Progress from sample review to parallel operation and a separate cutover decision only when the operator signs off.

Migration asset

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.

Comparison worksheet
Billing proof

Invoices, balances, statements, credits, refunds, deposits

Access proof

RADIUS, MikroTik, CPE, connector, approval, rollback

Field proof

Jobs, photos, GPS, signatures, equipment used

Migration proof

Imports, API sync, validation, reconciliation, cutover

Next step

Discuss the scope for your network.