MIGRATE VISP

Retire the legacy stack without losing your subscriber history.

There is no one-click VISP exporter, so we do this one together: you export what VISP gives you, our team maps it into ISPbox, and you verify everything in a trial workspace before cutover.

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

01 The migration plan

An assisted import: you bring the export, we bring the mapping, and nothing goes live until you say so.

01

Export your VISP data

Pull subscriber, service and balance exports from VISP. We will tell you exactly which reports we need.

02

We map and import together

Our team maps the export into ISPbox - packages, statuses, balances - into a trial workspace you can inspect.

03

Verify and cut over

Compare balances, point routers and RADIUS at ISPbox, and start the next cycle here while VISP stays read-only.

02 What moves with you

Subscribers, services and what they owe.

The goal is billing continuity: every account starts in ISPbox with the balance it had in VISP.

Subscriber accounts

Contact data, addresses and account status for every active and suspended subscriber.

Services and packages

Plans mapped to ISPbox packages with speeds and pricing, ready for RADIUS provisioning.

Open balances

Outstanding amounts carry over so dunning and collections continue without a reset.

03 The safety net

Assisted does not mean risky - the process is built around a verification step you control.

Trial workspace first

The import lands in a workspace you can inspect for as long as you need before going live.

Parallel run

Keep VISP running while you verify. Cut over at a cycle boundary, not mid-month.

A human on the line

The same person maps your data and answers your questions - no ticket queue roulette.

Ready to move past VISP?

Tell us about your deployment and we will scope the import within a day.

Compare ISPbox with VISP →