Preparing for ISP Migration
Before migrating to a new ISP or onboarding with a service like CENTRANET, it is essential to prepare the MikroTik router properly. This begins with identifying the required services—such as Hotspot for captive portal authentication or PPPoE for subscriber sessions—and documenting the router model, RouterOS version, upstream connection type, and any intermediate devices like switches or VLANs. For automatic setup, RouterOS 7.20 or newer is required, along with a clean hard reset and active internet connectivity. However, for live networks, always confirm the appropriate migration workflow with support before erasing any configuration, as retention options do not replace required preparation steps.
Creating a Secure Backup
The first critical step is creating an encrypted RouterOS binary backup. This binary format preserves the full configuration, including MAC addresses, and should be stored in a protected, off-router location. Record the device model, RouterOS version, and backup date alongside the file. Verify the backup exists and that the password is accessible through your secure process. MikroTik advises that binary backups are intended for recovery on the same device and same RouterOS version. Note that if The Dude or User Manager is installed, their configurations are not included in the system backup and require separate backup mechanisms.
Additionally, generate a readable configuration export for reviewing network layout. However, exports are not complete substitutes for binary backups: system user passwords, installed certificates, and SSH keys are not exported, and sensitive values are hidden by default. Keep upstream connection details, VLAN assignments, and recovery instructions accessible only to authorized technicians. Avoid sharing backups, subscriber credentials, or enrollment commands in public forums.
Understanding Clean-Reset Precautions
A factory reset and an empty configuration are not the same. A normal reset reloads default settings, while using no-defaults=yes clears configuration without loading defaults. The skip-backup=yes option suppresses the automatic pre-reset backup. Never execute reset commands without understanding these parameters, as a clean reset can remove IP addresses, routes, firewall rules, and management settings essential for your current connection—treat it as a service interruption.
Never perform a reset remotely via the only connection you are about to erase. Prepare a local technician, a cabled computer, and a documented recovery method before initiating a reset. If using a physical reset button, consult the exact device instructions—do not assume timing from another model applies. After an empty reset, rebuild the minimum protected management and upstream connectivity needed for enrollment. An empty router does not automatically regain internet access simply because the provider’s cable is connected. Keep customer connections offline until the intended configuration is fully ready.
Verifying Internet Connectivity
Determine how your ISP delivers service: DHCP, static addressing, or PPPoE. Obtain the correct settings through an authorized channel. If VLAN tagging is required, record the VLAN ID—do not assume the WAN connection is untagged or on a specific Ethernet port.
Verify connectivity in stages: first confirm the physical link and expected WAN address or PPPoE session. Then validate the default route, test reachability to a known public IP, and check DNS resolution. MikroTik’s first-time configuration guide separates IP connectivity testing from DNS validation.
CENTRANET requires the router itself to reach the internet via HTTPS. A laptop browsing through another network does not satisfy this requirement. Confirm the router can reach the enrollment endpoint using the prescribed workflow, and investigate any DNS, routing, or HTTPS errors before proceeding.
Maintain two separate tests: (1) the router reaching CENTRANET, and (2) a subscriber reaching the internet. Either can succeed while the other fails. Document which test you performed to ensure the next troubleshooting step targets the actual issue.
Preserving Management Access
Label your management cable and note its router port before making changes. Identify the management IP address and the authorized account to be used. Confirm reconnection via this path before configuring customer-facing services.
During local preparation, WinBox can connect via MAC address when local network and router settings allow, but do not assume this will work across routed networks or after every configuration change. MikroTik’s initial setup documentation describes neighbor discovery and MAC-based connection when IP access is unavailable.
Use a strong, unique administrator password and isolate management services from customer networks. MikroTik recommends keeping management services off the public internet and using a VPN for remote access. Hardening guidance also advises disabling MAC management services in production.
Establish and test the intended management route before removing any temporary recovery method. CENTRANET’s provisioning guide identifies internet and management connections as protected during customer port assignment. Review the discovered layout carefully, especially when multiple services share a switch. A port label in your notes must match the physical cable and the interface displayed on the router.
Preparing Customer Addressing and Authentication
For Hotspot, plan the customer interface, IPv4 subnet, address pool, DNS service, and portal identity. MikroTik documents an IPv4 dependency for reliable Hotspot operation and warns that device-mode settings can interfere with the feature. Validate these prerequisites before attributing portal failures to billing issues.
If using multiple internet links, have the routing design reviewed. MikroTik notes Hotspot restrictions involving the default routing table and PCC load balancing. Do not assume an existing multi-WAN configuration will work unchanged with a captive portal.
For PPPoE, prepare the customer-facing interface, subscriber address pool, PPP profile, and authentication method. MikroTik’s PPPoE server example illustrates how these components integrate. Use your own reviewed address plan rather than copying example ranges into a live network.
If another billing system or RADIUS server already manages accounts, clarify which system owns credentials and service policies before migration. Avoid conflicting changes from dual systems. Prepare one test account per service and exclude real customer records from test screenshots or support examples.
Practical Preparation Checklist
Before generating the enrollment command, verify:
- Router model and installed RouterOS version are recorded; automatic setup requires 7.20+.
- The selected setup or migration workflow is understood.
- An encrypted binary backup is downloaded, with its password securely available.
- A readable export and upstream connection details are retained privately.
- Any reset has an agreed maintenance window and local recovery plan.
- WAN, management, and customer cables are labelled.
- The router has working IP connectivity, DNS, and outbound HTTPS access.
- Management access is tested and protected from customer traffic.
- Hotspot or PPPoE interfaces and address pools are planned.
- Existing authentication dependencies have been reviewed.
- Test devices, test accounts, and an acceptance checklist are ready.
Enrolling and Testing
Generate the registration-specific command in CENTRANET’s Router Fleet workflow and review it before executing in MikroTik Terminal. Follow the discovery, configuration, and verification states. A completed terminal command is only one part of onboarding.
Test from an actual customer port. For Hotspot, validate portal access, authentication, DNS, and browsing. For PPPoE, establish the test session, confirm the assigned address, and verify browsing. Separately test expiry, suspension, and reconnection through the agreed workflow.
Where paid access is involved, confirm payment provider setup before an agreed test transaction. Validate the payment record, router account installation acknowledgement, and customer browsing independently. A payment confirmation alone does not prove delivered connectivity.
Ready to prepare your site? Contact CENTRANET with your router model, RouterOS version, upstream connection type, and whether you need Hotspot, PPPoE or both. Ask to confirm the reset or migration path before changing a live router; leave passwords and customer records out of the enquiry.