Guide · ISP software migration

Changing software is a project. Give it a plan.

Your customers still need their connection while you change the system behind it. Start with a small test, clear responsibilities, and a way back if something does not work.

Free for up to 40 subscribers.

The everyday work

Keep the useful details close.

Customer records

Map identifiers, contacts, service locations, status values, and the relationships between accounts and subscriptions.

Billing cutover

Reconcile balances and unpaid invoices. Choose which system issues the next bill to avoid billing the same service twice.

Network access

Test authentication, profiles, IP assignments, and service controls on a non-production account before a live cutover.

Recovery and ownership

Keep backups, a rollback decision point, named owners, and a list of checks for the morning after the switch.

Why it is different

Agree on what moves before moving anything.

List the records you need: customers, contacts, subscriptions, plans, balances, invoices, tickets, and network assignments. Ask both vendors what can be exported and imported. Treat payment tokens and access credentials separately; their portability must be confirmed, not assumed.

A connected workflow

Prove a small move before a large one.

01

Map a sample export

Use a small, authorized sample to check field mappings and record relationships. Transfer it through an agreed secure channel.

02

Reconcile and test

Compare record counts and balances. Test activation, authentication, invoice generation, and staff access.

03

Schedule the cutover

Agree on a change window, staff coverage, customer communications, and rollback criteria. Verify services and billing afterward.

Common questions

A few things you might be wondering.

Can I migrate from Splynx, Sonar, or Powercode to SkyBase?

We need to review your exports, network dependencies, and required records first. A comparison page is not a guarantee that every field, payment token, historical record, or integration can be transferred.

Can you promise zero downtime?

A reliable estimate needs a tested plan for your network. Agree on the expected interruption, validation checks, and rollback procedure before changing live services.

Should I email a full customer database for a quote?

Start with record counts and a list of fields and integrations. Arrange an appropriate secure transfer only when a sample is needed for an agreed migration review.