How to Migrate an Omada Controller using the Migration Feature
OC200 , OC300 , Omada Software Controller( V4 V5 )
Recent updates may have expanded access to feature(s) discussed in this FAQ. Visit your product's support page, select the correct hardware version for your device and check either the Datasheet or the firmware section for the latest improvements added to your product.
One of the features offered by your TP-Link Omada Controller is its Migration feature. The Migration feature allows users to migrate the configurations and data from an existing or old Omada Controller to a new Controller. The Migration function includes Site Migration and Controller Migration, covering all the needs for migrating both a single site and/or the whole Controller.
For the ER7212PC 3-in-1 router, this feature allows Omada administrators to migrate the configurations and data from the current Controller to any other Controller that has the same, or higher firmware version. The ER7212PC cannot import any configurations or data from any other Omada Controllers.
For controller v5.13.11.41 and above, only configuration files from a controller with the same first three segments in its version number (Major.Minor.Patch) can be imported.
I. Site Migration
Site Migration allows the administrator to export a site from the current Controller to any other Controller that has the same firmware version. All the configurations and data of the site will be migrated to the target Controller. The process of migrating configurations and data from one site to another Controller can be summarized in three steps: Export Site, Migrate Site and Migrate Devices.
Step 1: Export configurations and data of the site to be migrated to a backup file.
A. Go to Settings → Migration. On the Site Migration tab, click the Start button as shown.
B. Select the site being imported to the second Controller using the Select Site drop-down list.
C. Select where you want to export and save the backup file.
D. Click Export to download the current site’s file. If you have backed up the file, click Skip.
Step 2: Migrate Controller
In the target Controller, import the backup file of the Current Controller.
A. Log in to the target Controller, then go to Settings → Maintenance → Backup & Restore. Click Browse to locate and choose the backup file of the previous Controller. Then, click Restore to upload the file.
B. After the file has been imported to the target Controller, go back to the previous Controller and click Confirm.
Step3: Migrate Devices
Migrate the devices from the original site to the target Controller.
- Enter the IP address or URL of your target Controller into the Controller IP/Inform URL input field. In this case, the IP address of the target Controller is 10.0.3.23.
Note: Make sure you enter the correct IP address or URL of the target Controller to establish communication between Omada managed devices and your target Controller. Otherwise, Omada managed devices cannot be adopted by the target Controller.
- Select the devices to be migrated by clicking the box next to each device. By default, all the devices are selected.
- Click Migrate Devices to migrate the selected devices to the target Controller.
- Verify that all the migrated devices are visible and connected on the target Controller. When all migrated devices are in Connected status on the Device page of the target Controller, click Forget Devices on the previous site to finish the migration process.
- When the migration process is completed, the configuration and data will be migrated to the target Controller. You can delete the previous site if necessary.
II. Controller Migration
Controller Migration allows Omada administrators to migrate the configurations and data from the current Controller to any other Controller that has the same firmware version. The process of migrating configurations and data from the current Controller to another Controller can be summarized in three steps: Export Controller, Migrate Controller and Migrate Devices.
Step 1: Export Controller
Export the configurations and data of the current Controller as a backup file.
- Navigate to Settings → Migration.
- On the Controller Migration tab, click the Start button as shown in the following image.
- Select the length of time, in days, that data will be backed up in the Retained Data Backup, and where you want to export and save the data.
- Click Export to export the configurations and data of your current Controller as a backup file. If you have backed up the file, click Skip.
Step 2: Migrate Controller
In the target Controller, import the backup file of the current Controller.
- Log in to the target Controller and navigate to Settings → Maintenance → Backup & Restore.
- Click Browse to locate and choose the backup file of the previous Controller. Then, click Restore to upload the file.
- After the file has been imported to the target Controller, return to the previous Controller and click Confirm.
Step 3: Migrate Devices
Migrate the devices on the current Controller to the target Controller
- Enter the IP address or URL of your target Controller into Controller IP/Inform URL input field. In this case, the IP address of the target Controller is 10.0.3.23.
Note: Make sure the correct IP address or URL of the target Controller is entered to establish the communication between Omada managed devices and your target Controller. Otherwise, Omada managed devices cannot be adopted by the target Controller.
- Select the devices to be migrated by clicking the box next to each device. By default, all devices are selected.
- Click Migrate Devices to migrate the selected devices to the target Controller.
- Verify all the migrated devices are visible and connected on the target Controller. When all the migrated devices are in Connected status on the Device page of the target Controller, click Forget Devices on the previous Controller to finish the migration process.
When the migration process is completed, the configuration settings and data are migrated to the target Controller. You can uninstall the previous Controller if necessary.
Related FAQs
Looking for More
Is this faq useful?
Your feedback helps improve this site.
What’s your concern with this article?
- Dissatisfied with product
- Too Complicated
- Confusing Title
- Does not apply to me
- Too Vague
- Other
Thank you
We appreciate your feedback.
Click here to contact TP-Link technical support.
TP-Link Community
Still need help? Search for answers, ask questions, and get help from TP-Link experts and other users around the world.
We have updated our Policies. Read Privacy Policy and Terms of Use here.
This website uses cookies to improve website navigation, analyze online activities and have the best possible user experience on our website. You can object to the use of cookies at any time. You can find more information in our privacy policy .
We have updated our Policies. Read Privacy Policy and Terms of Use here.
This website uses cookies to improve website navigation, analyze online activities and have the best possible user experience on our website. You can object to the use of cookies at any time. You can find more information in our privacy policy .
Basic Cookies
These cookies are necessary for the website to function and cannot be deactivated in your systems.
TP-Link
SESSION, JSESSIONID, accepted_local_switcher, tp_privacy_base, tp_privacy_marketing, tp_smb-select-product_scence, tp_smb-select-product_scenceSimple, tp_smb-select-product_userChoice, tp_smb-select-product_userChoiceSimple, tp_smb-select-product_userInfo, tp_smb-select-product_userInfoSimple, tp_top-banner, tp_popup-bottom, tp_popup-center, tp_popup-right-middle, tp_popup-right-bottom, tp_productCategoryType
Youtube
id, VISITOR_INFO1_LIVE, LOGIN_INFO, SIDCC, SAPISID, APISID, SSID, SID, YSC, __Secure-1PSID, __Secure-1PAPISID, __Secure-1PSIDCC, __Secure-3PSID, __Secure-3PAPISID, __Secure-3PSIDCC, 1P_JAR, AEC, NID, OTZ
Zendesk
OptanonConsent, __cf_bm, __cfruid, _cfuvid, _help_center_session, _pendo___sg__.<container-id>, _pendo_meta.<container-id>, _pendo_visitorId.<container-id>, _zendesk_authenticated, _zendesk_cookie, _zendesk_session, _zendesk_shared_session, ajs_anonymous_id, cf_clearance
Analysis and Marketing Cookies
Analysis cookies enable us to analyze your activities on our website in order to improve and adapt the functionality of our website.
The marketing cookies can be set through our website by our advertising partners in order to create a profile of your interests and to show you relevant advertisements on other websites.
Google Analytics & Google Tag Manager
_gid, _ga_<container-id>, _ga, _gat_gtag_<container-id>
Google Ads & DoubleClick
test_cookie, _gcl_au