Mikrotik Export Configuration: A Comprehensive Guide
Mikrotik devices are widely used in networking environments due to their reliability, flexibility, and affordability. These devices offer a range of features and functionalities that make them a popular choice among network administrators. One of the key features of Mikrotik devices is their ability to export configuration, which is essential for maintaining and managing network settings. In this article, we will explore the concept of Mikrotik export configuration, its importance, and provide a step-by-step guide on how to export and import configurations.
Why Export Mikrotik Configuration?
Exporting Mikrotik configuration is crucial for several reasons:
Methods for Exporting Mikrotik Configuration
There are several methods for exporting Mikrotik configuration:
.cfg file..cfg, .txt)./export command to export the configuration./export file=configuration.cfg).Importing Mikrotik Configuration
Importing a Mikrotik configuration is a straightforward process:
.cfg, .txt)./import command to import the configuration./import file=configuration.cfg).Best Practices for Mikrotik Export Configuration
To ensure that your Mikrotik export configuration process is efficient and effective, follow these best practices:
Conclusion
Mastering the MikroTik Export Configuration: A Comprehensive Guide
Whether you are migrating to a new RouterBOARD, setting up a backup strategy, or troubleshooting a complex firewall rule, knowing how to properly use the Mikrotik export configuration command is an essential skill for any network administrator.
Unlike a standard binary backup file, an export generates a RouterOS script (.rsc). This script is human-readable, editable, and—most importantly—can be partially applied to other devices. 1. Why Use Export Instead of Backup?
MikroTik offers two primary ways to save your settings: .backup files and .rsc exports.
Binary Backup (.backup): Best for a full "system restore" on the exact same device. It includes sensitive data like passwords and user accounts but is not readable by humans.
Configuration Export (.rsc): Generates a plain-text script of the commands needed to recreate your setup. It is ideal for version control (GitHub), auditing, and moving configurations between different hardware models. 2. Basic Export Commands
The export command is executed via the Command Line Interface (CLI). You can access this through Winbox (New Terminal), SSH, or Telnet. Export the Entire Configuration To see your entire setup printed in the terminal: /export Use code with caution. Save Export to a File
To save the configuration to the router’s storage (which you can then download via Winbox > Files): /export file=my_config Use code with caution. This creates a file named my_config.rsc. 3. Advanced Export Techniques
One of the most powerful features of the MikroTik export tool is the ability to filter what you save. Export Specific Sections
If you only need your firewall rules or your IP addresses, you don't need the whole file. Navigate to the submenu and run export:
/ip firewall filter export file=firewall_only /ip address export file=addresses_only Use code with caution. The "Compact" Export (RouterOS v6 & v7)
By default, newer versions of RouterOS use "compact" export, which only shows values that differ from the factory default. This makes the file much cleaner and easier to read. /export compact Use code with caution. Exporting Without Sensitive Data
If you are sharing your configuration on a forum or with a consultant, you should hide sensitive information like Wi-Fi passwords and VPN secrets: /export hide-sensitive Use code with caution.
(Note: In RouterOS v7, sensitive data is hidden by default unless specified otherwise.) 4. How to Import a Configuration
Once you have your .rsc file, applying it to a new router is straightforward.
Upload the file: Drag and drop the .rsc file into the Files window in Winbox. Run the Import command: /import file-name=my_config.rsc Use code with caution. mikrotik export configuration
Pro Tip: Before importing a full configuration to a new router, it is best practice to reset the router to "No Configuration" to avoid IP conflicts or command errors. 5. Common Issues & Best Practices
Interface Names: If you export a config from a router with 10 ports and import it to one with 5, the script may fail when it looks for ether10. Always review the script in a text editor (like Notepad++) before importing.
Version Compatibility: While RouterOS is generally backwards compatible, moving a configuration from v7 back to v6 can cause syntax errors due to the new routing stack in v7.
Automated Backups: You can create a Scheduler script that runs /export file=daily_config every night to ensure you always have a fresh recovery point. Conclusion
The MikroTik export configuration tool is more than just a backup utility; it’s a powerful way to manage, share, and learn RouterOS. By using specific exports and cleaning up sensitive data, you can maintain a professional and secure networking environment.
To export a MikroTik configuration, you use the /export command in the terminal to generate a script-based .rsc file. Unlike binary .backup files, these are plain-text and human-readable, making them ideal for auditing or migrating settings between different hardware models. Core Export Commands
You can run these commands by opening New Terminal in WinBox or via SSH.
Export configuration via API - General - MikroTik community forum
In MikroTik's RouterOS, the export command is used to generate a script of configuration commands that can be used to recreate your settings on another device or for backup purposes. Unlike a binary .backup file, an export is a plain-text file that you can read and edit. Core Export Commands
The syntax varies depending on whether you want a full dump or just a specific section: Full Export: export file=myconfig
Generates a full configuration script and saves it as myconfig.rsc in the Files menu. Compact Export: export compact file=myconfig
(Default in newer RouterOS versions) Only exports settings that differ from the factory defaults. Section-Specific: /ip address export
Exports only the configuration for a specific menu (in this case, IP addresses). Terminal View: export
Running the command without file= prints the configuration directly to your terminal window. Key Parameters
show-sensitive: By default, RouterOS hides passwords and shared keys. Use export show-sensitive if you need to include passwords in the script.
terse: Compresses the output into fewer lines, making it harder to read but more efficient for automated processing.
verbose: Includes default values and additional comments, which is helpful for learning how specific features are structured. Best Practices for Backups
Binary vs. Script: Use .backup files for quick restores on the exact same device. Use .rsc exports when migrating to a different hardware model or when you need to audit specific settings.
Sensitive Data: Always be cautious when using show-sensitive. If you share this file for troubleshooting on forums, ensure you manually scrub your public IP addresses, passwords, and private keys.
Restoring: To apply an exported configuration, upload the .rsc file to a new router and run /import file-name=myconfig.rsc.
This paper provides a technical overview of the MikroTik configuration export process, a critical function in RouterOS management used for auditing, migration, and partial system replication. 1. Introduction: Export vs. Binary Backup
MikroTik offers two distinct ways to save configuration data, each serving a different technical purpose:
Export (.rsc): A human-readable text script containing RouterOS commands. It is ideal for migrating settings between different hardware models.
Backup (.backup): A binary, non-editable file that captures the entire state of the router, including MAC addresses and passwords. It is intended for restoring the exact same device. 2. Core Export Methodologies
The primary method for exporting configuration is through the Command Line Interface (CLI), accessible via Winbox, SSH, or Telnet. Global Full Export
To generate a complete script of all non-default settings, use the root level command:/export file=filename Partial (Sub-menu) Export Backup and Recovery : Exporting the configuration allows
Users can export specific modules (e.g., firewall rules or IP addresses) by navigating to that sub-menu:/ip address export file=address_config 3. Key Parameters and Visibility
Recent versions of RouterOS (v7+) introduced stricter security and verbosity controls for exports: Difference between backup and export-how to monitor changes
The MikroTik configuration feature allows you to generate a plain-text script of your router's settings, typically saved with a extension. This is distinct from a standard
, which creates a binary file used for full system restores on the same hardware. MikroTik community forum Key Uses of Exported Configurations Human-Readable Audit : Since the file is plain text, you can open it in or any text editor to review every setting manually. Hardware Migration
these scripts onto different MikroTik models to replicate settings. Configuration Templates
: Administrators often use exports to create "gold images" for mass-deploying new routers. Comparison: Export vs. Backup Export (.rsc) Backup (.backup) Plain-text script Binary file Not exported by default Fully encrypted with password Compatibility Cross-platform (any MikroTik) Device-specific (best for same model) Can be manually edited Cannot be edited Common Export Commands You can run these commands in the New Terminal Social WiFi Academy Full Export to File export file=myConfig Creates a file named myConfig.rsc Compact Export export compact
Shows only the settings that differ from the factory defaults. Specific Section /ip address export Exports only the IP address configurations. Hide Sensitive Info export hide-sensitive
Ensures secrets like VPN keys or local user passwords aren't visible. Social WiFi Academy How to Retrieve the Export and connect to your router. menu on the left panel. Locate your Right-click the file and select to save it to your computer, or simply drag and drop it to your desktop. Social WiFi Academy bash automation to periodically fetch these exports from multiple routers? Mikrotik Configuration Backups 11 Sept 2023 —
command allows you to dump your router's configuration into a plain-text script format (typically with a
extension). Unlike binary backups, these files are human-readable, editable in any text editor, and can be used to migrate settings between different hardware models. Core Export Commands To use these commands, open a New Terminal or connect via SSH. San Francisco Bicycle Rentals Configuration Management - RouterOS - MikroTik
Exporting a configuration in MikroTik RouterOS creates a readable
script file that can be edited or used to migrate settings to another device. Unlike a binary backup, an export allows you to see the exact commands used to configure the router. MikroTik community forum 1. Core Export Commands All exports are performed via the or via SSH. Configuration Management - RouterOS - MikroTik
For example, export configuration from /ip address the menu and save it to a file: [admin@MikroTik] > /ip address print Flags: X - How to export configuration from a MikroTik device?
Here’s a helpful, real-world story about using /export on a MikroTik router.
Title: The Night the Power Flickered
The Setup
Mariana ran the IT for a small hotel. Her network ran on a single MikroTik RB4011—handling guest Wi-Fi, the PMS (property management system), security cameras, and the staff network. She’d configured it over two years ago, adding rules as needed. It worked, but she’d never documented it.
The Incident
One stormy Tuesday, a brownout hit. The router rebooted. When it came back up, the guest Wi-Fi was gone. The cameras were unreachable. Staff couldn’t print. The only thing working was the wired management port Mariana was connected to.
Panic. She logged in via WinBox. The config looked… incomplete. A corrupted sector on the flash had wiped out half of the /interface bridge settings and all of the /ip hotspot profiles.
The Lesson from the Past
Mariana’s mentor had once told her: “On MikroTik, running config is not saved config. And saved config is not backed-up config.” He’d made her memorize one command:
/export file=backup-$(/system clock get date)
She’d run it every Friday, saved the .rsc file to her laptop.
The Recovery
She connected via SSH and typed:
/export
The current (broken) config scrolled by—short, missing entries. Then she opened her latest backup file from a week ago: backup-jan-12-2025.rsc. go to Files >
It was a clean, readable script. She saw exactly where the bridge VLANs were defined, where the hotspot server was bound.
She reset the router to defaults (after disconnecting the WAN cable):
/system reset-configuration no-defaults=yes skip-backup=yes
Then she dragged the backup-jan-12-2025.rsc file into WinBox’s Terminal and ran:
/import backup-jan-12-2025.rsc
The Magic of /export
Within 8 minutes, the hotel was back online. The guests never noticed. The PMS came back. Cameras started recording.
Mariana sat back, heart still racing. That night, she learned three things:
/export saved her job. It gave her a human-readable, version-controllable backup—not a binary mess.Pro Tips from her recovery:
| Command | Why it matters |
|---------|----------------|
| /export hide-sensitive | To share configs without exposing passwords |
| /export verbose | Shows default values—great for learning |
| /export compact | Removes comments and defaults, smaller file |
And her new favorite script—run by the router itself every Sunday at 3am:
/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"
The moral: A MikroTik without an exported config is just a puzzle waiting to break at 2 AM. With /export, it’s a recipe you can cook again perfectly, any time.
Restoring a configuration from an export file is known as "running a script." Since an export file is essentially a list of commands, the router executes them line-by-line to rebuild the configuration.
The Command:
/import file=my-router-backup.rsc
Crucial Warning: When importing a configuration, the router does not wipe the existing config first. It attempts to add the configuration on top of what exists.
/system reset-configuration before importing to ensure a clean slate.Summary
What export produces
Common usages
Important caveats & risks
Best practices
Commands & useful options
Quick checklist before sharing an export
Example safe-sharing workflow
If you want, I can:
export Instead of .backup?| 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) |
Key Takeaway: Use .backup for full disaster recovery of the exact same unit. Use export for documentation, migration, and troubleshooting.
Before looking at the content, it is important to know how to generate it safely.
/export compact
This hides default values, making the script shorter and easier to read./export
Shows every single setting, including defaults./export show-sensitive
Includes passwords and keys (handled carefully in the example below).You can export a configuration directly to your local machine without storing a file on the router first. Using SSH, run:
ssh admin@192.168.88.1 "/export compact" > router-config.txt
This command connects to the router, runs the export, and saves the output to a local file called router-config.txt on your computer.
Winbox is a popular graphical user interface (GUI) tool for managing Mikrotik devices. To export the configuration using Winbox: