How to migrate Omada Controller with 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.
Migration function allow users to migrate the configurations and data of an old Controller to a new Controller. Migration function include Site Migration and Controller Migration, covering all the needs to migrate both a single site and the whole Controller.
For ER7212PC, the 3-in-1 router, it 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. While the ER7212PC is not allowed to be imported with any configurations and data from any other Omada Controllers.
For controller v5.13.11.41 and above, only the configuration file from the controller with the same first-three-part version number(Major.Minor.Patch)can be imported.
I. Site Migration
Site Migration allows the administrators to export a site from the current Controller to any other Controller that has the same or higher 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 a site to another Controller can be summarized in three steps: Export Site, Migrate Site and Migrate Devices.
Step1: Export configurations and data of the site to be migrated as a backup file.
A. Go to Global View> Settings> Migration. On the Site Migration tab, click start button on the following page.
B. Select the site to be imported into the second Controller in the Select Site drop-down list. Select where you want to export and save the backup file. Click Export to download the file of the current site. If you have backed up the file, click Skip.
Step2: Migrate Site: In the target Controller, import the backup file of the original site.
A. Start and log in to the target Controller, click the top right corner of the screen and select the top left side, and select , and then the following window will pop up. Note that for Controller v 4.3.0 and above, only the file from the Controller with the same major and minor version number can be imported.
B. Enter a different name for the new site. Click Browse to upload the file of the site to be imported and click Import to import the site
C. 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 which are on the original site to the target Controller.
A. Enter the IP address or URL of your target Controller into Controller IP/Inform URL input filed. In this case, the IP address of the target Controller is 10.0.3.23.
Note: Make sure that you enter the correct IP address or URL of the target Controller to establish the communication between Omada managed devices and your target Controller. Otherwise Omada managed devices cannot be adopted by the target Controller.
B. Select the devices that are 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.
C. Verify that 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 on the target Controller, click Forget Devices on the previous site to finish the migration process.
D. When the migration process is completed, all the configuration and data are 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 or higher 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.
Step1: Export Controller Export the configurations and data of the current Controller as a backup file.
A. Go to Global View> Settings> Migration. On the Controller Migration tab, click start button on the following page.
B. 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.
Step2: Migrate Controller: In the target Controller, import the backup file of the current Controller.
A. Log in to the target Controller, 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 on the current Controller to the target Controller
A. Enter the IP address or URL of your target Controller into Controller IP/Inform URL input filed. In this case, the IP address of the target Controller is 10.0.3.23.
Note: Make sure that you enter the correct IP address or URL of the target Controller to establish the communication between Omada managed devices and your target Controller. Otherwise Omada managed devices cannot be adopted by the target Controller.
B. Select the devices that are 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.
C. Verify that 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 on the target Controller, click Forget Devices on the previous Controller to finish the migration process
When the migration process is completed, all the configuration and data are migrated to the target Controller. You can uninstall the previous Controller if necessary.
Related FAQs
Looking for More
Questa faq è utile?
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
We'd love to get your feedback, please let us know how we can improve this content.
Grazie
We appreciate your feedback.
Click here to contact TP-Link technical support.
Questo sito utilizza i cookies per migliorare l'esperienza di navigazione, analizzare le attività online e offrire agli utenti una migliore user experience. Puoi disattivare o rifiutare il loro utilizzo in qualunque momento. Per maggiori informazioni consulta la nostra privacy policy .
Questo sito utilizza i cookies per migliorare l'esperienza di navigazione, analizzare le attività online e offrire agli utenti una migliore user experience. Puoi disattivare o rifiutare il loro utilizzo in qualunque momento. Per maggiori informazioni consulta la nostra privacy policy .
Basic Cookies
Questi cookies sono necessari per il corretto funzionamento del sito e non possono essere disattivati nel tuo sistema.
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
Analytics e Marketing Cookies
I cookies analitici ci permettono di analizzare le tue attività sul nostro sito allo scopo di migliorarne le funzionalità.
I marketing cookies possono essere impostati sul nostro sito dai nostri partner pubblicitari allo scopo di creare un profilo di tuo interesse e proporti contenuti pubblicitari rilevanti su altri siti.
Google Analytics & Google Tag Manager
_gid, _ga_<container-id>, _ga, _gat_gtag_<container-id>
Google Ads & DoubleClick
test_cookie, _gcl_au