Migrating from one 365 tenant to another

We recently converted a few hundred users PCs from their old 365 tenant to our tenant (company purchase).

Here's what we did

From the PC perspective, we had the users do the conversion of the machine.  They followed a 50-step guide with pictures of what to do, had around 200 users do it themselves.  IT would remote in once in a while when something occurred that didn't match the document but was minimal overall.

CONVERSION SYNOPSIS

We the user add a local 'other users' account to the computer.  This account was given administrative privileges and allowed them to use this account to facilitate the switching from one 365 domain to another.  This conversion for us, resulted in NO data loss.  Our users were still able to access their old 365 tenant /user account and get data.  Prior to the migration, we had users export their browser bookmarks into a file on the computer which they could import upon conversion.

From a OneDrive and Outlook email perspective, we used a 3rd party tool to migrate this data from one tenant to another.  We did develop procedure to do this all manually; however, the tool was absolutely worth the purchase to ease the migration as it was almost flawless.

Once they added the local admin account, it was then logged into.  The account name was "conversion" in this example

They disjoined from the work/school domain 

When disjoined, MS has you do an account check to ensure you can log back into the computer. 
Users just used the local admin "conversion" account they created.

Computer is rebooted and the users log back into the local account

They re-add themselves to the new 365 account.

It's important that they use this option and not the top one.

Assuming you have MFA setup, they will be challenged to setup their MFA access

Once this authentication is working, they will then be prompted to JOIN the new tenant.

We used a sperate tool to migrate email and OneDrive, but it could be manually done, but its time consuming.

BitLocker keys transferred during this process

The original 365tenant user account was still on the machine and could be accessed.

Once users confirmed their data was done, they self-deleted the admin account and their old user account.

The actual conversion from one tenant to another only took about 30 minutes.  

We had contingency in place in case users had issues and needed to revert back to the original tenant, which they could, but it wasn't needed.

Provisioning a 365 user from a powershell one at a time

" We can’t show the OneDrive settings. If this is a new user, their OneDrive might not be set up yet. Try again in a few minutes. "

I tried to provision my new users using scripts, but I got nowhere.  So I used the following script.  I had to do with on a PER user basis, but is what it is.  (Created an AutoHotkey macro to do the actual work for me since I had a few hundred users)

If its a new user, the user has to "soak in 365" for a few hours before this will sometimes work.  
Ensure that you have the proper licenses in place for the user

1>

Create a file "singleconvert.ps1" and put in the code below.  Replace TENANT ID and COMPANYINC with your information.  Bottom of this page shows were to find Tenant ID

Param(
    [Parameter(Mandatory = $False)]
    [String]$SharepointURL = "https://COMPANYINC-admin.sharepoint.com/",

    [Parameter(Mandatory = $False)]
    [String]$tenantID = "TENANTID",

    [Parameter(Mandatory = $True)]
    [String]$UserEmail = ""
)

# Connect to services
Connect-MgGraph -TenantId $tenantID -Scopes 'User.Read.All'
Connect-SPOService -Url $SharepointURL

Write-Host "Checking if user $UserEmail exists..."

try {
    $u = Get-MgUser -UserId $UserEmail -Select UserPrincipalName, AssignedLicenses

    if ($u) {
        Write-Host "User found. Requesting OneDrive provisioning for $($u.UserPrincipalName)..."

        Request-SPOPersonalSite -UserEmails @($u.UserPrincipalName) -NoWait

        Write-Host "Provisioning request submitted successfully."
        Write-Host "Note: OneDrive creation is asynchronous and may take time."
    }
}
catch {
    Write-Error "Could not find user $UserEmail or unable to query Microsoft Graph."
}

Disconnect-SPOService
Disconnect-MgGraph

2>
Open up a powershell window as Admin and go to the directory you have saved your script

3>

Run the script

.\singleconvert.ps1

You'll see the following syntax appear

4>
Paste in the email of the user and press enter

5>
You will be prompted to login with a user that has privileges to work in the 365 tenant.

6>
You will get a subsequent prompt (likely) to enter in your credentials for a user that has 365 admin privileges

When the script is done (about 5 seconds) you'll see this.   

7>
Check your tenant again.  In my experience, if the script is run, and assuming the rest of your licenses are good, it only took a few minutes for the status to change in 365

NOTE:

The script isn't perfect.  It sometimes will error out for now reason.  If you see an error, try running it 2 or 3 more times.

How to find your Tenant ID

You can find your Tenant ID (at time of writing) but going to portal.azure.com, logging in and selecting "Microsoft Entra ID"

It will show you tenantID on the screen.

Configure NDI on VLC

This will show you how to configure VLC to broadcast as an NDI source.

1>

Download the NDI tools for your computer.  Windows 11 is used in this example

https://ndi.video/tools/vlc-plugin-2/

2>

Install the NDI tools

...it can take some time just as it says....

It will ask you to register...you don't have to if you dont want to.

3>

Launch VLC

4>

Go to Tools > Preferences

5>

In the Video section, set the Output to NDI video output.

6>
Do the same for Audio.

AUDIO -> Output Module -> NDI Audio Output

8>

Click on SAVE.  

9>
Restart VLC

10>

Open up a media file and start playing.  

11>

Go to your NDI receiving device and go through the methedology of that device to receive an NDI.

In this example OBS is being used. 

VLC can't receive NDI, but OBS is free, and if you install the NDI plugin components, takes mere minutes, it can receive NDI broadcasts with ease to a display device.

Pre-provision OneDrive script syntax example

At time of writing, April/2026 when you pre-provision one drive for a migration, this URL in microsoft provides you a PowerShell script

Pre-provision OneDrive for users in your organization - SharePoint in Microsoft 365 | Microsoft Learn

This script that you can download from Microsoft site looks like this:

You just have to change your 365 tenant ID, but doesn't give any real meaningful example of what you put in, so here's what worked.  And I changed my $true to $false.  I only modified the very top section, but here's the syntax in case you are having issues.

Ran the PowerShell as admin.  Entered in my user/pass for tenant admin credentials

Script ran:

Rotate Screen in windows with keyboard

This option may work with some graphics cards.
Use the Settings app option if problems are encountered

Ctrl + Alt + Up arrow – rotates to landscape mode.

Ctrl + Alt + Down arrow – rotates the screen upside down.

Ctrl + Alt + Right arrow – rotates the screen 90 degrees (right).

Ctrl + Alt + Left arrow – rotates the screen 90 degrees (left).

To return to the normal orientation, use the "Ctrl + Alt + Up arrow" keyboard shortcut.

Pull my production site into the staging site in GoDaddy

Pull my production site into the staging site

1. On your My Products page, next to Managed Hosting for WordPress, select Manage All.
   

   

   
   

   
   

   
   
   
   
   
   
2. For the website you want to pull into staging, select Settings from the  menu.
   
   
   
3. In the Staging Site section, select Actions and then select Sync Sites.
   
4. Select Pull production to staging.
    Note: Choose to Overwrite content if you're syncing your sites for the first time or if you're certain you want to overwrite the staging site database. If you do not choose to Overwrite content, only files will be pulled into staging.
5. Select Sync.

Syncing your staging site from your production site may take a few minutes based on the size and complexity of your site.