Product / Billing and network workflows
Move subscribers with a controlled migration plan
Start with a backup and a small representative import. Check the resulting plans, credentials, billing state and expiry before moving the rest of the network.
Prepare a clean export
Review customer names, usernames, service type, plan, account number, balance, expiry, status, router mapping and applicable IP details. Remove duplicates and transfer credential-bearing files through a protected channel.
Choose an available import path
The subscriber CSV importer supports account and service fields. The MikroTik PPPoE import flow can read router secrets/profiles and offers a dry run with explicit expiry handling. Confirm the source mapping for your actual deployment.
Validate before switching access
Test a pilot account’s login, package, outstanding balance and expiry. Check renewals and payment callbacks before the broader cutover. Keep a rollback plan and the original configuration backup.
Agree what is outside the import
Do not assume a complete historical payment ledger, every source-system field or an arbitrary router configuration will migrate automatically. Confirm the required scope with support; zero downtime is not guaranteed.
Go deeper
Setup documentation
Questions and boundaries
Before you start
Is this a universal one-click migration?
No. CSV mapping and supported MikroTik PPPoE imports cover specific data and workflows. Validate a pilot and agree the remaining scope before switching production service.
Should I send subscriber passwords through the contact form?
No. Use the contact form to discuss scope. Arrange a protected method before transferring any credential-bearing export.
Related workflows
Plan a pilot for your network
Discuss device compatibility, payment requirements and migration scope before a full rollout.
Contact the team