There are two type of Umbrella organizations: standalone orgs and child orgs. A child org belongs to an Umbrella console, which could be either an ISP Console, an MSP console, an MSSP console, a Multi-Org Console, a Secure Trials Console, or an Umbrella Partner Console. A standalone org does not belong to any console.
It is possible for Umbrella Support to do the following:
- migrate/move a standalone org to a console;
- migrate a child org from its console (so it becomes a standalone org);
- migrate a child org from its console to a different console.
However, note that it is not possible to do the following:
- migrate an NFR (Not For Resale) org;
- migrate an org that is in the middle of a subscription term;
- migrate org configurations only rather than migrating an entire org;
- merge two orgs together into one org;
- convert an org into a console;
- convert a console into an org.
If you would like Umbrella Support to perform a migration, please start a new case and supply the following information:
- the Umbrella IDs of the orgs to be migrated (if all child orgs of a console are to be migrated, just specify ALL);
- the Umbrella ID of the source console (required only if child orgs are being migrated out of a console);
- authorization from a full admin of the source console (required only if child orgs are being migrated out of a console);
- the Umbrella ID of the destination console (required only if orgs are being migrated to a console);
- authorization from a full admin of the destination console (required only if orgs are being migrated to a console);
- authorization from a full admin of the standalone org (required only if a standalone org is being migrated to a console);
- information on when you would like the migration to take place.
The Umbrella ID of an org can be seen in the browser URL when you logged in to the org. For example, if the URL is https://dashboard.umbrella.com/o/123654/#/overview then the org's Umbrella ID is 123654. (Umbrella IDs for child orgs of a console can also be seen in the console, in Customer Management.)
Similarly, the Umbrella ID of a console can be seen in the browser URL when you are logged in to the console. For example, if the URL is https://dashboard.umbrella.com/msp/987012#/mspsettings then the console's Umbrella ID is 987012.
Cases can be started with Umbrella Support via the support portal, or by sending an email to email@example.com.
What will be migrated
The following will be migrated completely, with no noticeable changes:
- all Deployments, such as registered Networks, Roaming Computers, Active Directory components, etc;
- all Policies and Policy Components that were created at the org level;
- all Reporting;
- all User Accounts (with one possible exception, listed below in "What will not be migrated");
- all API Keys.
Note that during a migration, Umbrella services will continue to function as before. In other words, there will be NO interruptions to DNS resolution or other Umbrella functionality during a migration.
What will not be migrated
- Centralized Settings are policy-related settings that are created at the Umbrella console level and shared with child orgs. Centralized settings are never migrated.
- For example, if an org is moved from one console to another, any Security Settings that were shared by the source console to that org will not necessarily be the same in the destination console. Furthermore, Security Settings in the destination console won't necessarily be shared to the newly migrated org.
- This also applies to other Centralized policy-related Settings such as Content Settings, Destination Lists, Block Pages, Custom Integrations, etc.
- If a user belongs to both an org and a destination console, the user will be removed from the org when the org is migrated to the destination console.
- For orgs migrated from an MSP to an MSSP, note that org Deployment Parameters (for deploying the Umbrella Roaming Client) are not visible in MSSP consoles.
- For orgs migrated from an Umbrella console integrated with a PSA (either Autotask or ConnectWise) to another such PSA-integrated console, any PSA IDs will not be retained by the migration.
Please note that orgs are migrated to an Umbrella MSSP Console, all users at the MSSP Console level must log in to Umbrella using their Cisco ID and password. For details, please see the knowledge base article How to log in to the Umbrella Partner Console or MSSP Console.
Also note that if a user belongs to multiple Umbrella consoles, when logged in to one console they can see and navigate to the other console(s) by using the drop down menu at the top right hand side. That menu is labelled Search for organization name and address (e.g. ACME, New York).
Things to check after a migration
To be safe, it is recommended that the following be checked after a migration:
- Verify that the migrated org has the correct Umbrella Package, License End Date, and Number of Seats; this information can be verified via the org's Umbrella dashboard --> Admin --> Licensing page.
- If the org was migrated to a console, verify that the proper Centralized Settings are shared to the migrated org. This can be verified via the Umbrella destination console --> Centralized Settings.