The compact parameter makes the script cleaner by avoiding the verbose set commands, making it easier to read and edit. /export file=compact_config compact Use code with caution. C. Full Example: Secure, Clean Backup
/system scheduler add name="email-backup" interval=7d \ on-event="/export file=auto-backup; /tool e-mail send to=\"it@hotel.com\" subject=\"Router Config\" file=auto-backup.rsc"
| Feature | .backup file | export file | | :--- | :--- | :--- | | Format | Binary (not readable) | Plain text (readable/editable) | | Restore target | Same RouterOS version & hardware | Any RouterOS device (any version/hardware) | | Editing | Not possible | Yes (e.g., change IPs or interfaces) | | Automation | Difficult | Easy (use with scripts/Ansible) |
Be aware that the hide-sensitive parameter may not always conceal all potentially sensitive data. For example, Forum discussions have pointed out that private WireGuard keys generated through the Back to Home (BTH) feature are not flagged as "sensitive" and can appear in a hide-sensitive export. Always manually review your exported script for any private keys, public IP addresses, or other information you wouldn't want to share.
Manually exporting configurations leaves room for human error. You can automate this process using the built-in RouterOS Scripting and Scheduler tools to generate an export daily or weekly. Script: Export and Email Configuration mikrotik export configuration
When importing to a different model, always review the script first. Interfaces might be named differently (e.g., sfp-sfpplus1 ), which can cause the script to fail if not adjusted. that you can use for your next export? Difference between backup and export-how to monitor changes
Exported configurations often include the physical MAC addresses of the original router's ports. Lines containing mac-address=XX:XX:XX:XX:XX:XX .
For enterprise use, consider automating backups. You can use tools like Ansible to bulk-export router configs, or a RouterOS script with a scheduler to create timestamped .rsc files and upload them to an FTP server. The community project "mikrotik-backup" is a good example of automating the creation of both .backup and .rsc files.
export/import ROS configuration - Beginner Basics - MikroTik Forum The compact parameter makes the script cleaner by
Are you moving configuration to the or a different model ?
Warning: Running an import on top of an existing configuration can cause IP conflicts and script errors. Always reset the router with before importing a full system script.
To generate an export, open the in Winbox or via SSH and use the following commands:
/export show-sensitive
Before importing a configuration script, the target router should ideally have no conflicting settings. Go to -> Reset Configuration . Check No Default Configuration . Click Reset Configuration . Step 2: Upload the .rsc File
This comprehensive guide covers everything you need to know about exporting, filtering, and importing MikroTik configurations. Why Use export Instead of backup ?
Ideal for keeping a version-controlled history of your network changes. 1. How to Export Full Configuration