Tenant-to-Tenant Migration with Orchestrator – Technical Overview (Microsoft 365 | Preview)
Tenant-to-tenant migration with Orchestrator in Microsoft 365 introduces a native, API-driven, and highly validated approach for cross-tenant migrations. It is designed for enterprise scenarios where sequencing, dependencies, and governance are critical. Note: This capability is currently in preview. Features and behavior may change before GA. Architecture and execution model Migration is executed through batches (jobs) managed via Microsoft Graph (Beta) User-level execution: one user failing validation does not block others in the same batch Mandatory Standalone Validation before migration submission Date-driven cutover using completeAfterDateTime Supported workloads (actual scope) Exchange Online Microsoft Teams ODSP (OneDrive for Business) Important clarification on SharePoint Orchestrator does not migrate shared SharePoint content such as Team sites, Channel sites, or collaboration sites. The ODSP workload covers personal user data (OneDrive) only. SharePoint team/workload sites remain out of scope and require separate tooling or processes. Critical prerequisites Identity Mapping (CTIM) is mandatory and must remain stable during migration Target users must not have Exchange mailboxes or OneDrive sites provisioned before migration Licenses must be assigned only after Identity Mapping (ExchangeGuid stamping) Migration apps and service principals (Teams, Meetings, CTMS) must be correctly provisioned Organization Relationships and Migration Endpoints must be in place Exchange autoforwarding must be enabled for Meetings migration Validation and lifecycle Standalone Validation acts as a full “what-if” check Key states include: Cancellation or user removal is possible only before cutover Post-migration cleanup After completion, tenants must be returned to a non-migration state: Remove Identity Mapping data Remove Organization Relationships Remove Migration Endpoints Revoke migration app permissions and service principals Decide whether to retain or remove MailUsers in the source tenant Skipping cleanup leaves the tenant in an exception state. When this approach fits Mergers and acquisitions Divestitures and tenant splits Regulated environments requiring strict control Scenarios where dependency-aware sequencing matters more than speed Technical conclusion Orchestrator is not a one-click solution. It delivers native orchestration, deep validation, and predictable execution when Identity Mapping, licensing order, and scope boundaries are fully understood. For experienced administrators and architects, it represents a major step forward in tenant-to-tenant migrations within Microsoft 365, even while still in preview.
SharePoint Modernization Framework - Help with migrating publishing pages
Hi all, I am working on a project to migrate SharePoint 2013 publishing pages to SharePoint Online (Modern). Using Sharegate I am able to get the content copied across to SPO, but when I try to conver the publishing pages to Modern, I get this error I tried to use the .NET Page Tranformation Class (https://github.com/pnp/PnP/tree/master/Samples/Modernization.PageTransformation) But I have facing issues in getting the right assembly reference for: using Microsoft.SharePoint.Client; using OfficeDevPnP.Core; using SharePointPnP.Modernization.Framework.Transform; Can anyone here help me with the dll/assemblies that I should be including in my VS project? I ones that I download online do not seem to work. Additionally if someone has the steps which are required to effectively transform the 2013 publishing pages to SPO Modern page, please share the details. Thanks in advance for the help! Manoj
SharePoint On-Premises migration
Hi, I have a question about SharePoint 19 On-Premises migration, I have 2 different SharePoint 2019 On-Premises farms, I need to migrate the documents libraries from one farm to another, the documents libraries its has a huge size its approximately more than 2TB, and it's from a different site collection. What is the best practice or plan to achieve this?Sharepoint migration connected Excel Queries
we have a problem at work that we can not find out, we ran Sharepoint migration manager and moved from onprem server to sharepoint online. Questions arose regarding EXCEL links if they still work after moving to sharepoint. We tested some excel sheets that had been moved to sharepoint, these turned out to have changed automatically from link to H: // share / HR / excel link to link "Sharepoint.company.com/sites/HR-bibliotek/EXCEL"…. Does this mean that sharepoint migration manager is changing all connected links to files connected that has been moved to sharepoint? I need to find som facts that sharepoint migration manager or excel workbooks change these connections to the files that have been moved to sharepoint online.
How to migrate from a Team Site Sharepoint to a Document Center
Hi , I would like to know if there is any tool to do a migration from a team site Sharepoint (Teams) to a Document center SharePoint , they both are in Sharepoint online and I know that Sharepoint migration tool only works for migrations from Sharepoint servers to online Sharepoint. Is there any procedure or tool that can help. Thank youRelink,Relink ALL, and MERGE option is missing under FILES within FORMS Library
I was trying to relink some records within a forms library after migrating to new site and all 3 options RELINK, RELINK ALL and MERGE options were there. later i found those missing and not sure how do i put it back. can someone please assist. The default RELINK VIEW is missing.Relinking All Infopath Forms in Library after Migrating to SPONLINE
We recently completed migrating one of our site to Online, which consist of several form library with over 10k records utilizing Infopath forms. After completion, i tried to open those documents, found out that it's still pointing to old site URL, and only opens with desktop infopath tool. Troubleshooting that i have done so far: 1)Updated Data connection to a new Site URL. 2) Made sure that open with browser feature is enabled at library setting . 3) Tired adding new record, edit it and didn't have any issues with a new record. 4) Tried running Repair.ASPX ( RELINK feature) within Form library and were able to relink 3k out of 7 k records. and have doing it for over 10 times now. 5) and now i am trying to relink every single records. And dont think its worth investing that time for relinking 7 k records individually. any help will be highly appreciated. Thanks IanMicrosoft SharePoint Migration tool did not show the all the existed lists
Microsoft SharePoint Migration tool did not show the all the existed lists when I had tried to do migration to a an on premises SharePoint List to SharePoint Online. Even if I had to select the option migration all lists and libraries to SharePoint online. There is nothing special on the report folder that contains logs.
