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. Please note that product availability varies by region, and certain models may not be available in your region.
The migration function allows users to migrate the configurations and data of an old Controller to a new Controller. The migration functions include Site Migration and Controller Migration, covering all the needs to migrate both a single site and the whole Controller.
Before proceeding with migration, please check the following notes:
- The ER7212PC, a 3-in-1 router, supports configuration and data migration only between ER7212PC devices running the same or higher firmware version. Configurations cannot be imported or exported between the ER7212PC and software controllers, hardware controllers, or the Omada Central Controller.
- For controller versions 5.13.11.41 and higher, controller migration is supported only when importing a configuration file from a controller with the same Major.Minor.Patch version number (e.g., 5.13.11).
I. Site Migration
Site Migration allows administrators to export a site from the current Controller to any other Controller with the same or higher firmware version. All the site's configurations and data 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.
Step 1: Export configurations and site data to be migrated as a backup file.
A. Go to Global View> Settings> Migration. On the Site Migration tab, click the start button on the following page.
B. Select the site imported into the second Controller in the Select Site drop-down list. Then, choose where you want to export and save the backup file. Click Export to download the file for the current site. If you have backed up the file, click Skip.
Step 2: In the target Controller, import the backup file of the original site.
A. Start and log in to the target Controller. Under “Global View,” select “Dashboard” in the menu, and click on import site.
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
Note:
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.
C. After importing the file to the target Controller, return to the previous Controller and click Confirm.
Step 3: Migrate Devices: Migrate the devices on the original site to the target Controller.
A. Enter your target Controller's IP address or URL into the Controller IP/Inform URL input field. In this case, the IP address of the target Controller is 10.0.3.23.
Note:
Ensure you enter the target Controller's correct IP address or URL to establish communication between Omada-managed devices and your target Controller. Otherwise, the target controller cannot adopt Omada-managed devices.
B. Click the box next to each device to select it for migration. By default, all 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 to 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 with 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.
Step 1: 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 the start button on the following page.
B. Select the time and 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.
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 importing the file to the target Controller, return to the previous Controller and click Confirm.
Step3: Migrate Devices: Migrate the devices on the current Controller to the target Controller
A. Enter your target Controller's IP address or URL into the Controller IP/Inform URL input field. In this case, the IP address of the target Controller is 10.0.3.23.
Note:
Ensure you enter the target Controller's IP address or URL to establish communication between Omada-managed devices and your target Controller. Otherwise, the target controller cannot adopt Omada-managed devices.
B. Click the box next to each device to select it for migration. By default, all 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 to 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
All the configuration and data are migrated to the target Controller when the migration process is completed. If necessary, you can uninstall the previous Controller.
Get to know more details of each function and configuration please go to Download Center to download the manual of your product.
Întrebări similare:
Citește despre:
A fost util acest FAQ?
Părerea ta ne ajută să îmbunătățim acest site.
Ce probleme ai avut cu acest articol?
- Nemulțumit de produs
- Prea complicat
- Titlu confuz
- Nu se aplică pentru mine
- Prea vag
- Alt motiv
Mulțumim
Apreciem părerea ta.
Acest site web folosește cookie-uri pentru a îmbunătăți experiența navigării web, a analiza activitățile online și a oferi utilizatorilor cea mai bună experiență pe site-ul nostru. Te poți opune utilizării cookie-urilor în orice moment. Poți afla mai multe informații în politica de confidențialitate .
Your Privacy Choices
Acest site web folosește cookie-uri pentru a îmbunătăți experiența navigării web, a analiza activitățile online și a oferi utilizatorilor cea mai bună experiență pe site-ul nostru. Te poți opune utilizării cookie-urilor în orice moment. Poți afla mai multe informații în politica de confidențialitate .
Cookie-uri de bază
Aceste cookie-uri sunt necesare pentru funcționarea site-ului web și nu pot fi dezactivate în sistemele tale
TP-Link
SESSION, JSESSIONID, accepted_local_switcher, tp_privacy_banner, tp_privacy_base, tp_privacy_marketing, 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
Cookie-uri de analiză și marketing
Cookie-urile de analiză ne permit să analizăm activitățile tale de pe site-ul nostru web a îmbunătăți și ajusta funcționalitatea site-ului.
Cookie-urile de marketing pot fi setate prin intermediul site-ului nostru web de către partenerii noștri publicitari pentru a crea un profilul intereselor tale și a-ți afișeze reclame relevante pe alte site-uri web.
Google Analytics, Google Tag Manager
_gid, _ga_<container-id>, _ga, _gat_gtag_<container-id>
Google Ads și DoubleClick
test_cookie, _gcl_au