MIGRATE Platypus

Decades of billing history, moved without drama.

Platypus migrations are assisted: you export what the system gives you, our team maps it into a trial workspace, and billing continuity - balances, history, autopay - is the explicit goal.

// assisted migration - our team maps your export with you

01 The migration plan

Export, map, verify - with special care for the long billing history Platypus systems tend to carry.

01

Export your Platypus data

Pull client, service and billing exports. We will tell you which formats work best.

02

We map and import together

Our team maps decades-old records into clean ISPbox accounts in a trial workspace.

03

Verify and cut over

Compare balances, repoint provisioning, and start the next cycle in ISPbox.

02 What moves with you

Continuity for accounts that predate the cloud.

Long-lived Platypus installs carry real history - the migration keeps it.

Clients and services

Accounts and plans mapped to ISPbox packages, ready for RADIUS provisioning.

Balances and history

Open balances carry over; historical records are preserved for reference.

Payment flows

Subscribers move to modern online payments and autopay across four gateways.

03 The safety net

The legacy install stays untouched until ISPbox has proven itself against it.

Trial workspace first

The import lands in a workspace you inspect before anything goes live.

Parallel run

Platypus keeps billing while you verify - cut over at a cycle boundary.

A human on the line

One person owns your migration from first export to first ISPbox invoice.

Replace Platypus without losing your data

Send us a sample export and we will outline the import and go-live timeline.

Compare ISPbox with Platypus →