Skip to main content

Import & Export Tools

MapZ provides tools to import network maps from other systems and export your maps for backup or sharing.

Importing from MikroTik Dude

MapZ can import network maps from MikroTik Dude, making it easy to migrate your existing network diagrams to MapZ.

Prerequisites

Before importing:

  • Export your Dude map as XML from MikroTik Dude
  • Ensure you have a Zabbix server configured in MapZ
  • Have the XML file accessible on your computer

Export from MikroTik Dude

  1. Open MikroTik Dude
  2. Open the map you want to export
  3. Go to FileExportXML
  4. Save the XML file to your computer

Import to MapZ

  1. In MapZ, navigate to SettingsImport
  2. Select "Dude XML Import"

Import Menu

  1. Click "Choose File" and select your Dude XML file
  2. Click "Upload"

Upload XML

  1. Review the import preview:
    • Number of hosts to be imported
    • Number of connections
    • Map dimensions
    • Any warnings or issues

Import Preview

  1. Configure import options:

    • Create Missing Hosts: Automatically create hosts in Zabbix if they don't exist
    • Map Zabbix Server: Select which Zabbix server to use for the imported hosts
    • Preserve Positions: Keep original node positions from Dude
    • Import Connections: Include connections between hosts
  2. Click "Import" to start the import process

What Gets Imported

From Dude to MapZ:

Dude ElementMapZ EquivalentNotes
DevicesHost NodesPositioned on map
Device NamesHost LabelsUsed as display labels
ConnectionsEdges/LinksBetween host nodes
Device PositionsNode PositionsX,Y coordinates preserved
LabelsText ObjectsStatic text elements
Device IconsNode IconsBest-effort mapping

Not Imported:

  • Dude-specific monitoring settings
  • Custom scripts
  • Alerts and notifications
  • Historical data
  • User permissions

Post-Import Steps

After importing, you'll need to configure monitoring:

  1. Link Hosts to Zabbix

    • If hosts don't exist in Zabbix, create them
    • Configure Zabbix monitoring for each host
    • Add appropriate templates
  2. Configure Interfaces

    • Add network interfaces to hosts
    • Map interfaces to Zabbix items
    • Set up interface monitoring
  3. Adjust Styling

    • Customize node colors
    • Adjust connection styles
    • Add icons and labels
  4. Add Monitoring

    • Add monitored items to hosts
    • Configure thresholds
    • Set up graphs
  5. Verify Connections

    • Check that connections are correct
    • Add missing connections
    • Remove incorrect connections

Import Troubleshooting

"Invalid XML File" Error

Cause: XML file is corrupted or not a valid Dude export

Solution:

  • Re-export from Dude
  • Verify file is not empty
  • Check file encoding (should be UTF-8)

"Host Not Found in Zabbix" Warning

Cause: Hosts in Dude map don't exist in Zabbix

Solution:

  • Enable "Create Missing Hosts" option
  • Or manually create hosts in Zabbix first
  • Ensure hostnames match exactly

Positions Are Incorrect

Cause: Different map sizes between Dude and MapZ

Solution:

  • Manually adjust node positions
  • Use "Arrange" tools to organize nodes
  • Consider creating a new layout

Connections Missing

Cause: Connection data not in XML or import option disabled

Solution:

  • Ensure "Import Connections" is enabled
  • Verify connections exist in Dude map
  • Manually add missing connections

Migration Best Practices

  1. Test Import First

    • Import to a test map first
    • Verify all elements imported correctly
    • Make adjustments before production import
  2. Clean Up Dude Map

    • Remove unused elements before export
    • Ensure hostnames are consistent
    • Organize map layout
  3. Prepare Zabbix

    • Create host groups in advance
    • Set up templates
    • Configure monitoring items
  4. Document Differences

    • Note any Dude-specific features you use
    • Plan how to replicate in MapZ
    • Document custom configurations

Exporting Maps

Export your MapZ maps for backup, sharing, or documentation.

Export Formats

MapZ supports multiple export formats:

JSON (Full Data)

  • Complete map data including all settings
  • Can be re-imported to MapZ
  • Best for backups and migration
  • Includes all node properties and connections

PNG (Static Image)

  • Raster image of the current map view
  • Good for documentation and presentations
  • Configurable resolution
  • Transparent background option

SVG (Vector Image)

  • Scalable vector graphics
  • Best for printing and high-quality displays
  • Can be edited in vector graphics software
  • Maintains quality at any size

PDF (Document)

  • Portable document format
  • Good for sharing and archiving
  • Includes map metadata
  • Print-ready format

Exporting a Map

  1. Open the map you want to export
  2. Navigate to SettingsExport

Export Menu

  1. Select the export format
  2. Configure export options (varies by format)
  3. Click "Export"
  4. The file will download to your computer

Export Options by Format

JSON Export

Options:

  • Include Credentials: Include Zabbix server credentials (not recommended)
  • Include History: Include historical data and metrics
  • Compress: Create a compressed .zip file

Use Cases:

  • Backup before major changes
  • Migrate maps between MapZ instances
  • Version control of map configurations

PNG Export

Options:

  • Resolution: Width and height in pixels
  • Background: Transparent or solid color
  • Include Legend: Add a legend to the image
  • Quality: Image quality (1-100)

Recommended Settings:

  • For Web: 1920x1080, Quality 85
  • For Print: 3840x2160, Quality 95
  • For Thumbnails: 800x600, Quality 75

SVG Export

Options:

  • Include Fonts: Embed fonts in SVG
  • Optimize: Reduce file size
  • Include Metadata: Add map information

Use Cases:

  • High-quality printing
  • Further editing in Illustrator/Inkscape
  • Scalable documentation

PDF Export

Options:

  • Page Size: A4, Letter, Legal, Custom
  • Orientation: Portrait or Landscape
  • Include Metadata: Map name, date, author
  • Include Legend: Add legend page

Use Cases:

  • Professional documentation
  • Sharing with stakeholders
  • Archival purposes

Batch Export

Export multiple maps at once:

  1. Navigate to SettingsMap Management
  2. Select multiple maps (Ctrl+Click or Shift+Click)
  3. Click "Batch Export"
  4. Choose export format
  5. All maps will be exported as a .zip file

Batch Export

Scheduled Exports (Premium)

Automatically export maps on a schedule:

  1. Navigate to SettingsScheduled Exports
  2. Click "Create Schedule"
  3. Configure:
    • Maps: Which maps to export
    • Format: Export format
    • Frequency: Daily, Weekly, Monthly
    • Destination: Local download or cloud storage
  4. Click "Save Schedule"

Supported Destinations:

  • Local download (email notification)
  • Google Drive
  • Dropbox
  • Amazon S3
  • FTP/SFTP server

Re-importing Exported Maps

Importing JSON Maps

  1. Navigate to SettingsImport
  2. Select "MapZ JSON Import"
  3. Choose your JSON file
  4. Review import settings:
    • Overwrite Existing: Replace map if it exists
    • Create New: Create as a new map
    • Merge: Merge with existing map
  5. Click "Import"

Import Conflicts

If a map with the same name exists:

Overwrite

  • Replaces the existing map completely
  • All current data is lost
  • Use for restoring from backup

Create New

  • Creates a new map with a different name
  • Original map is preserved
  • Use for duplicating maps

Merge

  • Combines nodes and connections
  • Resolves conflicts based on node IDs
  • Use for collaborative editing

Best Practices

For Backups

  1. Regular Exports

    • Export maps weekly or after major changes
    • Use JSON format for complete backups
    • Store in multiple locations
  2. Version Control

    • Include date in filename (e.g., map-2025-01-22.json)
    • Keep last 5-10 versions
    • Document major changes
  3. Test Restores

    • Periodically test importing backups
    • Verify all data is preserved
    • Ensure process is documented

For Migration

  1. Plan Ahead

    • Document current Dude setup
    • Identify custom features
    • Plan MapZ equivalent configurations
  2. Migrate in Stages

    • Start with a small test map
    • Validate the process
    • Then migrate production maps
  3. Parallel Running

    • Keep Dude running initially
    • Verify MapZ monitoring is working
    • Gradually transition users

For Sharing

  1. Choose Appropriate Format

    • PNG/PDF for viewing only
    • JSON for collaboration
    • SVG for editing
  2. Remove Sensitive Data

    • Don't include credentials
    • Remove internal IP addresses if needed
    • Sanitize host names if required
  3. Include Documentation

    • Add a README with context
    • Explain map purpose and scope
    • Document any custom configurations

Troubleshooting

Import Fails

Check:

  • File format is correct
  • File is not corrupted
  • File size is within limits (50MB max)

Solution:

  • Try re-exporting the file
  • Split large maps into smaller sections
  • Contact support with error message

Export Takes Too Long

Cause: Large map with many nodes

Solution:

  • Export in smaller sections
  • Use lower resolution for images
  • Export during off-peak hours

Imported Map Looks Different

Cause: Different screen sizes or zoom levels

Solution:

  • Adjust zoom level
  • Rearrange nodes as needed
  • Check map settings for differences
  • Map Management: See Map Configuration
  • Backup Strategy: Regular exports ensure data safety
  • Migration Tools: Smooth transition from other platforms
Migration from Dude

The Dude XML import is designed specifically for MikroTik Dude users. It handles most common map elements automatically, but you'll need to configure Zabbix monitoring separately.