VPN Business Website Migration

This package moves a VPN provider's website and billing to new hosting, or from an old billing setup into WHMCS, while customers keep working VPN logins and the same renewal dates. It suits providers changing hosting, leaving a custom or abandoned billing system, or rebuilding a site that has fallen behind.

Billing first, VPN logins untouched

The website and billing are copied to the new server and tested privately through a hosts-file entry while the old system keeps taking payments. The provisioning link to your VPN backend is reconnected and tested with a real account: create, disable, restore. At cutover, the billing cron runs on one system only, because two systems running renewals together means double charges and accounts disabled by mistake.

• Your VPN servers, RADIUS users and WireGuard peers are not changed by a billing move.
• On Business, existing VPN usernames are kept and renewal dates are compared on sample accounts after the move.
• Old page addresses are redirected so links in reviews, emails and apps keep working.

Moving between billing systems

Premium covers imports from another billing system where it can export its data, such as a custom panel, Blesta or a spreadsheet, with record counts compared before and after. Passwords stored in a different format usually cannot be carried across, so I plan a password set email you approve before launch. The same plan includes a site redesign during the move and two weeks of fixes.

Configs and hostnames

Customers' VPN profiles keep working as long as the endpoint hostnames and keys stay the same. If you are also changing server hostnames, devices need new configs, so I plan a notice email and the dashboard change together. The method follows the same steps as my server migration work.