Skip to main content
Cisco Meraki

Switch Cloning

This article describes what configuration settings will be cloned when using the Clone feature in the Meraki dashboard. This powerful tool is perfect for both one-to-one and one-to-many configuration cloning.


Switch cloning is designed to copy all port-level and some switch-level configuration settings from a source switch to another. With the exception of cloning  an MS210/225 configuration to an MS250, cloning requires the source and destination switches to be the same model. In all cases, cloning requires the source and destination switches to have the same port density. Cloning requires the source or destination switch must not be part of a switch stack. The API endpoint aligns with what UI offers. 

Note: If the switches you are cloning are connected, the configuration will immediately take effect.

How to clone

The switch cloning process copies configurations from one source switch to one or more target switches. In the example screenshots below, Switch 1 is the source, Switch 2 is the target.

There is no way to revert cloning from the Meraki dashboard. Ensure you have selected the proper switch for both steps: the target switch is selected from the list under Switch > Switches, and the source switch is the device selected from the Edit... dropdown.


  1. Navigate to Switch > Switches and place a checkbox next to your target switch (or switches). 


  1. Select 'Edit', then 'Clone...'. 


  1. Select the switch you want your targets to look like. 


  1. Select 'Clone' to copy configurations from the source to the targets. 

Switch-level Configuration

STP Bridge priority (Switch > Configure > Switch settings)

Port Mirroring (Switch > Configure > Switch settings)

Port-level Configuration

The following settings will be cloned from the source switch to the destination switch:
  • Port Name
  • Port Tags
  • Interface state
  • Spanning tree
  • STP guard / BPDU guard
  • PoE
  • Link 
  • Port schedules (access only)
  • Interface Type
  • Adaptive Policy Group
  • Adaptive Policy Peer SGT Configuration
  • Access policy (access only)
    • (ignored if the source access policy doesn't exist in the destination network)
  • MAC whitelist (access only)
  • Whitelisted MACs (access only)
  • Sticky MAC whitelist (access only)
  • Whitelist size limit  (access only)
  • Native VLAN (trunk only)
  • Allowed VLANs (trunk only)
  • VLAN (access only)
  • Voice VLAN (access only)


Note that if cloning a non-PoE switch to a PoE switch, the PoE state of 'disabled' will be applied to the clone destination.

Switch Networks Bound to Templates

Switch networks bound to templates will not be able to clone using the Clone tool mentioned above. The correct way to duplicate switch configurations is using the Bind to profile tool, which is explained in our Switch Templates Deployment Guide.

  • Was this article helpful?