MikroTik Migration Guide
Complete Guide for Migrating your MikroTik Router into Alternet ISP Billing System
Last Updated: October 19, 2025
1. Introduction
This guide provides comprehensive instructions for migrating your MikroTik router configuration to the Alternet ISP Billing System ISP management platform. The migration tool allows you to seamlessly transfer:
- Bandwidth Profiles
- IP Pools
- Service Plans
- Hotspot Users
- PPPoE Users
- Static Leases
- Client Recharge History
⚠️ Important Notes Before Starting
- Backup your current MikroTik configuration
- Perform migration during off-peak hours
- Test with a small subset of data first
- Ensure you have proper credentials for your MikroTik router
- Verify network connectivity between the migration server and your router
2. Prerequisites
Required Access
- MikroTik router IP address and administrative credentials
- RouterOS API access enabled (port 8728)
- Read access to all configuration sections
Data Preparation
Before starting migration, ensure you have:
- Created bandwidth profiles in Alternet ISP Billing System
- Set up service plans that match your MikroTik profiles
- Prepared client data in CSV format (if using bulk import)
- Organized recharge history data (if migrating billing data)
3. Migration Types
The migration tool supports several migration types to suit your needs:
Full Migration
Migrates all supported data types: Hotspot users, PPPoE users, Static leases, Bandwidth profiles, IP pools, and Plans.
Hotspot Only
Migrates only Hotspot users and their related configurations.
PPPoE Only
Migrates only PPPoE users and their configurations.
Static Leases Only
Migrates only static DHCP leases.
Combination Migrations
Custom combinations like Hotspot+PPPoE, Hotspot+Static, or PPPoE+Static.
4. Step-by-Step Migration Process
Step 1: Connect to MikroTik Router
Enter your MikroTik router details:
- Router IP Address
- Port (default: 8728)
- Username and Password
- Select target router in Alternet ISP Billing System
- Choose migration type
Use the "Test Connection" button to verify connectivity.
Step 2: Data Import (Optional)
Before migration, you can import additional data:
- Clients via CSV: Import client details including names, contact information, and credentials
- Recharge History via CSV: Import billing and recharge records
Download CSV templates from the migration interface.
Step 3: Migration Steps
The migration process follows this sequence:
- Bandwidth Profiles: Speed limits and burst settings
- IP Pools: IP address ranges and allocation settings
- Plans: Service packages and pricing
- Hotspot Users: Web-based authentication users
- PPPoE Users: Point-to-Point Protocol over Ethernet users
- Static Leases: Fixed IP address assignments
Step 4: Preview and Configuration
For each step, you can:
- Preview the data to be migrated
- Set actions (Create, Update, Skip) for each item
- Configure recharge settings for client accounts
- Set expiration dates and status
Step 5: Execute Migration
Once configured:
- Click "Migrate" for each step
- Monitor real-time progress
- View success/failure logs
- Continue to next step when complete
5. CSV Import Specifications
Clients CSV Format
PPPOEPassword, MAC, Location, Status, ServiceType, Balance
Accepted Status Values:
- Active
- Inactive
- Banned
- Disabled
- Limited
- Suspended
- Deactivated
- Pending
Accepted Service Type Values:
- PPPoE
- Hotspot
- Static
- Others
Recharges CSV Format
expiration, expirytime, status
💡 Important Notes for Recharges Import
- Username must exist in customers table
- Planname must exist in plans table
- Status accepts only "on" or "off" values
- Dates should be in YYYY-MM-DD format
- Times should be in HH:MM format (24-hour)
6. Troubleshooting
Connection Issues
- Verify router IP address and port accessibility
- Check username/password credentials
- Ensure RouterOS API is enabled on the router
- Confirm firewall rules allow API connections
Migration Failures
- Check for duplicate entries in the target system
- Verify data formats match expected values
- Ensure required fields are populated in CSV files
- Check system logs for detailed error messages
Best Practices
- Start with bandwidth profiles and plans migration
- Import clients before recharge history
- Use the preview feature to verify data before migration
- Test migration with a small dataset first
- Keep backup of original CSV files
7. Support
If you encounter issues during migration:
- Check the system logs for detailed error information
- Verify all prerequisites are met
- Ensure your CSV files follow the required format
- Contact support with migration ID and error details
Need Help?
Contact our support team on info@al.co.ke or Call/WhatsApp on +254793800039.