If creating a new organization by migrating an existing subaccount, see the following considerations and restrictions. For best practices, see Preparing for Subaccount Migration.
Non-SSO accounts: User access:
You must select users from the account to give access to the new organization; access is not inherited.
You can choose to migrate users into the organization or grant access as Org Collaborators. See Review Access Requirements of Users Before Migrating to an Organization for more information.
Users collaborating from a different NetCloud Manager account can only be added as a Org Collaborator.
Users from the subaccount and its child subaccounts migrate automatically. Their access to the account and other subaccounts is removed. Collaborators from another NetCloud Manager account become Org Collaborators automatically, and their original account access is not impacted.
SSO-enabled accounts: User access:
When you convert a SSO subaccount into an organization:
The new organization will be non-SSO by default. SSO settings from the parent account do not transfer automatically.
Users from the subaccount will be moved to the parent account as basic users without any permissions.
After migration, you can choose how to restore user access. Options include the following:
Keep the organization non-SSO and add the users as Org Collaborators from the parent account.
Add SSO to the new organization by setting up a new IdP (Identity Provider) configuration and assigning users to it.
LAN Solutions: When a subaccount has LAN Solution enabled:
The migration will fail if the subaccount has a group with LAN Solutions enabled.
Select a different subaccount to migrate or create a new organization rather than creating from a subaccount.
Roles & Permissions: Permissions migrate as configured, but review them after migration to align with the new organization structure.
Devices & Groups: All associated devices and groups will move to the new organization automatically.
Licenses: Licenses associated with asset will migrate with those assets.
Alert Rules & Configurations: Some rules may not migrate in full.
Integrations: API tokens and other integrations linked to the subaccount may need to be recreated or updated after migration.
Timing: Migrations can impact active users and workflows.