Applies To
Call2Teams - Partners
Overview
If a client or the users of a 'Source' account need to be moved between Partners or other Sub Accounts, there are several ways this can be achieved.
Accounts are structured in a hierarchy, which can result in several account or sub-account layers.
Client accounts or Internal-Use accounts are usually sub-level accounts of a Native Partner Base Account.
Note: In some cases a 'Source Account' maybe a 'Proof of Concept' or 'Trial' Account.
Migrating Users and Services
This method expects the Microsoft 365 tenant to remain the same between accounts.
This is suitable for accounts where the services and users wish to be moved to a brand new sub-level account under any Native Partner.
If the Partner or Reseller differ from the Source Partner or Reseller, we will need written permission from both the source and the new provider.
To do this, raise a Service Desk case with us and include this written permission.
Create the new Sub-Level Client Account under the desired target Base account but do not create any Users or Services or Administrators at this stage.
Ensure that sufficient licences of the required types are added to the account.
We will check these at least match the existing source account and advise of any discrepancies.
We will perform the account migration and advise when it is completed.
All Users, Services and Administrators will then have been migrated away from the old Source account and will appear in the newly created target client account.
The old source account will expire after a 14-day cooling off period. Partners may amend Administrators on the new Sub/Client account as they wish.
Can I Move Users/Accounts Myself?
Yes.
This may be preferable in some cases, especially if there is a change in the Microsoft Tenant.
Create the new client/sub account first and begin to add the services as would be done for any new client.
For a large volume of users to add, consider using the bulk import option.
When ready, remove the users, licenses and services from the old account and Sync the new one.
Residual Calling Policies
Any residual policies in the Microsoft Admin portal that might cause conflict following a migration may need to be removed before a new Sync can be performed.
Simply remove anything that contains call2teams.com.
Domain Conflicts
Call2Teams sets up two domains for a Microsoft Tenant. If, following any of the above processes, there are more than two domains, or any conflict exists, it is safe to remove these and perform a fresh Sync.