What every project team needs to understand before migrating a single account
Tenant-to-tenant migrations – whether driven by AD to Entra ID projects, re-platforming, mergers, acquisitions, divestitures, or consolidation programmes – are amongst the most complex IT transformation projects an organisation will ever undertake. Without understanding what you have, who depends on it, and in what order it can safely move, projects run the risk of severely disrupting business operations.
Imagine the HR shared mailbox is migrated to a new domain before the individual user mailboxes are moved and no one can access it. Or you’ve moved the entire HR team in one go but their mail doesn’t work when they log on. The system that’s there to support your employees – sickness, grievance, bereavement – is now broken. Now think about that level of disruption across the other areas of your business, and you can see why tenant migrations keep project leaders awake at night!
This is where specialised platforms like ManagementStudio transforms a chaotic, spreadsheet-driven exercise into a structured, controlled programme. But what are the key factors organisations should consider before writing a single migration script?
Identify What You Can Leave Behind
The natural migration approach for many organisations is to lift-and-shift everything; take what you have today and relocate it somewhere else. It’s understandably perceived to be less complex, easier to manage, and quicker to deliver – but in a tenant-to-tenant migration, this can result in expensive project delays and business disruption. Before committing to move a dataset – whether that’s a file share, a SharePoint site, or a set of user accounts – the first step for the project team is to understand whether that data or resources are still actively used.
ManagementStudio provides a powerful mechanism to understand and manage this. Resources like file shares and SharePoint sites can be modelled as objects within the platform and linked to users through their associated Active Directory group. ManagementStudio can build a real-time baseline of exactly who has access to each share and at what permission level – read, read/write, owner – without requiring manual interrogation of AD. Workflow-driven surveys can then be sent directly to the relevant users and stakeholders to ask: is this share still needed? Does this data need to follow you to the new tenant?
The goal is not to move everything; it is to move the right things. Every dataset that can be retired before migration reduces cost, complexity, and risk.
Understanding the Interdependencies
A user isn’t just an AD account. They are a collection of resources: a mailbox, a set of file share permissions, a member of distribution groups, a consumer of SharePoint sites, and potentially a licensed user of multiple enterprise applications. Moving that user in isolation without understanding their full dependency map is how projects create outages. And no-one wants that!
ManagementStudio addresses this through its unified data model; we combine data from fragmented or disparate sources and present this back in a way that enables you to make informed decisions based on all the information available to you. Users, devices, applications, file shares, SharePoint sites, and enterprise apps are all brought into a single project view and these records are continuously enriched by the platform. When a project manager looks at a user, they can see not just their account details but everything that user touches across the estate. That’s powerful!
With particularly complex solutions – think of a business-critical ERP system like SAP as an example – ManagementStudio allows teams to create a conceptual model that ties together all the users, servers, applications, and enterprise apps that comprise that service and where it’s deployed. When the project asks, “what does it take to move SAP?”, the answer is visible in one place. This is contextualisation at scale, and it is something that a spreadsheet simply can’t replicate.
Shared Resources Require Phased Migration Planning
Mailbox migrations are a particularly good example of why phased planning matters. Consider a six-person HR team with individual mailboxes and a shared HR mailbox. Taking a ‘big bang’ approach by migrating all six users and the shared mailbox simultaneously is high-risk. If any part of the process fails, the entire HR team loses access to their primary communication channel overnight.
A structured, phased approach is far safer. Consider migrating a subset of individual mailboxes first, then cut the shared mailbox over once that initial cohort has landed successfully in the new tenant. The remaining users may be temporarily orphaned and unable to access the shared mailbox, but this is only for a short, planned window. More importantly, the service that HR provides to the business isn’t disrupted.
The key is that the project retains control and visibility at every stage, which is made possible with ManagementStudio’s Deployment Units (DUs). A DU is a logical group of migration objects – e.g. users, mailboxes, or devices – that are to be migrated together over a specific timeframe, making it easier to co-ordinate, schedule, and communicate a migration wave. A DU for the HR team might span several migration cycles, with pre-checks built in to confirm that prerequisite waves have completed successfully before the next phase proceeds to mitigate service disruption.
Validate User Data Before Migration Day
Migrating user data is one of the more nerve wrecking activities for a project team; you don’t want to be the one responsible for a user losing access to their work and leaving them unable to do their job!
In a tenant-to-tenant migration, user profile data like desktop files, documents, application settings that exists only on a local machine or a legacy network share will not automatically move to the new tenant. Project teams must know, in advance, where each user’s data lives, who has access, and whether it’s still required in the new world.
We’ve seen many of our customers move data into OneDrive in modern Microsoft environments, and there are well-established tools for OneDrive-to-OneDrive migration between tenants. However, users who have not redirected their data to OneDrive before migration day risk losing it. This is a communication and readiness challenge as much as a technical one, and it requires direct, personalised engagement with users – tracked and managed through ManagementStudio’s Users module – to confirm readiness before any migration action is taken.
Tooling Provides the Mechanism; ManagementStudio Provides the Oversight
Third-party tools are widely used to deliver the technical mechanics of tenant-to-tenant migrations, like moving mailboxes and synchronising directory objects. These are powerful but often narrow in their remit; they execute the migration, but they won’t help you understand what to migrate, in what order, or what the downstream impacts will be.
ManagementStudio occupies the layer above these tools, providing a business-centric baseline of the estate, the communication workflows, and the operational oversight that transforms a migration from a technical event into a managed programme. The combination of real-time contextual understanding and structured communication is what separates a migration that succeeds from one that consumes the project team for months after go-live.
How Do You Ensure a Smooth Migration?
Domain migrations are hard and we shouldn’t pretend otherwise. But the difference between a project that achieves its objectives on schedule and one that derails is rarely the migration tooling itself – it is the quality of data that underpins the decision making and planning. Knowing your estate, understanding your dependencies, and communicating clearly with your users are the foundations of every successful migration. ManagementStudio is built to deliver exactly that.
But planning is only part of the picture. In the next blog about tenant-to-tenant migrations, we’ll look at some of the real-world challenges faced by our customers and how you can overcome them.
