Migration Method No. 2

This migration method has the following key features:

A new Microsoft 365 application instance with its own application endpoint, database, resources, and service plans is created.
Existing Microsoft 365 subscriptions, which are based on service plans of your existing Microsoft 365 application instance, are removed. New Microsoft 365 subscriptions are created based on service plans of the new Microsoft 365 application instance. This allows you to switch from one configuration of resources and service plans to another.
The Microsoft accounts of your customers are re-registered in CloudBlue Commerce.
Existing cloud subscriptions, which have reseller relationships with your Direct CSP Provider account, are suspended. New cloud subscriptions, which obtain reseller relationships with the Indirect CSP Provider account of Ingram Micro, are created.

Important: During migration, customer accounts must remain the same: Existing Microsoft 365 subscriptions, which belong to an old application instance, must be removed from these customer accounts, and then new Microsoft 365 subscriptions, which belong to a new application instance, must be created for the same customer accounts.

To perform migration using this method, follow these steps:

Working together with Ingram Micro staff, send all your customers invitations from the Indirect CSP Provider account of Ingram Micro. All your customers must accept these invitations.
Working together with Ingram Micro staff, create and configure a Microsoft 365 application instance for Ingram Micro Syndication. This application instance must have its own application endpoint, database, resources, and service plans. To do this, use the instructions in The Ingram Micro Syndication Scenario.
For the Microsoft 365 application instance that is configured to use your Direct CSP Provider account, run the readCSPAccounts.py script with the --ignore-disabled option. In addition to the standard output files, the script creates the existsSubs_PARTNER_SUBDOMAIN.csv or existsSubs_PARTNER_TENANT_ID.csv output file that contains cloud subscriptions to be migrated. For details on running the script, see Importing Tenant Subscriptions from the Microsoft Cloud to CloudBlue Commerce.

Note: You can remove rows from the output file to exclude Microsoft accounts from migration, but you must not modify the content of rows. Also, you can use the --account-domain-list option of the readCSPAccounts.py script to specify which Microsoft accounts you need to migrate.
Check the following:
- The importSubs_PARTNER_SUBDOMAIN.csv or importSubs_PARTNER_TENANT_ID.csv output file must be empty. If there are any rows, this means that there are cloud subscriptions that are not registered in CloudBlue Commerce. You must import, remove, or ignore them (these cloud subscriptions will be migrated only if you import them).
- The errorSubs_PARTNER_SUBDOMAIN.csv or errorSubs_PARTNER_TENANT_ID.csv output file must be empty. If there are any errors, you must process them before migration.
- The existsSubs_PARTNER_SUBDOMAIN.csv or existsSubs_PARTNER_TENANT_ID.csv output file must not contain The cloud subscription with the CspId '...' (offer id '...' and limit '...') is an active add-on and is not represented by an Odin Automation subscription messages. If there are such messages, this means that there are cloud subscriptions that are not registered in CloudBlue Commerce. You must either remove or ignore them (in both cases these cloud subscriptions will not be migrated).
Create verification users for the Microsoft accounts of your customers by running the t1t2_migration.py script on your management node (the script is in the same directory as readCSPAccounts.py):
1. The t1t2_migration.py script requires the requests Python module. Install the module by running this command:
```
pip install requests
```
2. Prepare the identifier of the Microsoft 365 application instance that is configured to use your Direct CSP Provider account (this is the same application instance identifier that you used in step 3).
3. Perform the initial validation by executing one of these commands:
  - ```
  python t1t2_migration.py validate --o365-app-instance-id APP_INSTANCE_ID --file existsSubs_PARTNER_SUBDOMAIN.csv
```
- ```
python t1t2_migration.py validate --o365-app-instance-id APP_INSTANCE_ID --file existsSubs_PARTNER_TENANT_ID.csv
```
4. Create these verification users by executing one of these commands:
  - ```
  python t1t2_migration.py create_vrf --o365-app-instance-id APP_INSTANCE_ID --file existsSubs_PARTNER_SUBDOMAIN.csv
```
- ```
python t1t2_migration.py create_vrf --o365-app-instance-id APP_INSTANCE_ID --file existsSubs_PARTNER_TENANT_ID.csv
```
  Note: You can use the -–dry-run option to perform a dry run.
For every customer that has Microsoft 365 services, prepare and write down the following information:
- The CloudBlue Commerce account identifier
- The name of the Microsoft 365 initial subdomain
- The names of all Microsoft 365 licenses and their limits
Remove all Microsoft 365 subscriptions from CloudBlue Commerce, and wait for the respective Microsoft 365 tasks to be processed.
Register the Microsoft accounts of your customers using the information that you prepared in step 6. When registering, you must take into account the following:
- Service plans of the Microsoft 365 application instance that works in Indirect CSP Reseller (through Ingram Micro) reseller mode must be used.
- Your customers must obtain the same licenses with the same limits as they had before migration.
To register Microsoft accounts in CloudBlue Commerce, use the instructions in Registering New Customers with Existing Microsoft Accounts.

Remove the verification users by running one of these commands on your management node:

python t1t2_migration.py delete_vrf --o365-app-instance-id APP_INSTANCE_ID --file existsSubs_PARTNER_SUBDOMAIN.csv

python t1t2_migration.py delete_vrf --o365-app-instance-id APP_INSTANCE_ID --file existsSubs_PARTNER_TENANT_ID.csv

After you perform these steps, your new and existing customers will be provided with Microsoft 365 services within the Ingram Micro Syndication program.