Office 365 – Migrating Users Tenant-to-Tenant – Part Four Data Migration with Quest On Demand
Full run through of a project to migrate 8k users and their data between two 365 tenants.
Part Four goes through the data migration with Quest On Demand
Full run through of a project to migrate 8k users and their data between two 365 tenants.
Part Four goes through the data migration with Quest On Demand
So let say we have a situation. Our Office tenant has been running for 5 years and gathered some 60000 users all have their licenses assigned directly. Some by On-boarding scripts, some by joiner processes, some by service request, some seemingly by random dice rolls or monkeys whose time would be better spent typing out… Read More »
Full run through of a project to migrate 8k users and their data between two 365 tenants.
Part Three runs through setting up the users on the new tenant
Script to build out a full environment in an Azure free trial.
Okay first things first – I am not a coder, software engineer, programmer or anything else. Any script that I write has to meet only a few criteria
Does what its meant to
Doesn’t break crap
Is easy to reuse when I find it in my “Folder of Infinite Script-Holding”
Provides decent feedback when its running
Full run through of a project to migrate 8k users and their data between two 365 tenants.
Part Two goes through the scripts for scoping the project, identifying objects for migration and reporting data.
I use Powershell ISE for everything, even running single lines. I have my environment set up with a profile which checks the module installation and update version on every load. I have shared it here.