One of the common questions asked by MikroTik users is how to go about upgrading from ROSv6 to ROSv7.

Before upgrading, always make sure:

– The config is backed up using ‘export’ and ‘backup’ and the files have been moved off the router
– Console access is working (if applicable)
– A method to netinstall is available in case the upgrade fails for any reason

Understanding config migration

MikroTik added a helpful chart to the support docs that shows what config is automatically upgraded and what needs to be manually adjusted.

Upgrading to v7 – RouterOS – MikroTik Documentation

Exceptions and notes

BGP config migration has gotten better in the last few versions of v7. For the most part, it works without intervention but occasionally config will need to be removed and readded or edited.

Note the changes below to the structure of BGP menus and peerings as it has changed.

OSPF has come a long way in RouterOS v7 and is stable as well as interoperable with RouterOSv6. Interface templates have replaced network statements to advertise prefixes and form neighbor adjacencies, so be sure to look in that menu after upgrade to work with network statements in v7. Upgrading to v7 for OSPF normally works without issue or intervention.

MPLS is still a work in progress. Like the other protocols it has gotten better but still may need adjustments since it now includes the AFIs for IPv4 and IPv6 with LDP. Be sure to review the syntax pre and post upgrade as well as the operation state and be prepared to delete and re-add the configuration as needed if MPLS is not functional post upgrade. In general, MPLS and VPLS works between ROSv6 and ROSv7

Routing filters are also a work in progress. Most of the functionality and config upgrade works now when moving to v7 but the context sensitive help and tab complete is still being developed and filled in.

For more details, take a look at this article: MikroTik – RouterOSv7 first look – feedback on routing filters – StubArea51.net

User manager has no direct upgrade path available and must be migrated manually.