Cross-Tenant Shared Data Migration — Pricing, Plans & Scope

Cross-Tenant Shared Data Migration is a Microsoft migration offer available in the Commercial segment, because the current offer set lists only Commercial availability for this product. Buyers should treat it as a migration-related purchase option and confirm the exact migration scenario, covered workloads, and quantity basis before ordering.

Cross-Tenant Shared Data Migration includes availability of the named Microsoft migration offer for Commercial customers, because the source offer set lists the product with annual-commitment purchasing options. The source does not specify workload-specific rights, tooling, services, or a unit of measure, so those details should be confirmed with IT Partner before the subscription is configured.

Do not assume implementation services, discovery, remediation, backup, project management, end-user communications, or post-migration cleanup are included, because the source offer set does not define those service components. If your migration requires hands-on planning or execution support, confirm whether those services are purchased separately through IT Partner or another provider.

No, Cross-Tenant Shared Data Migration is listed as an annual-commitment offer, because the current Commercial offer set shows a one-year term only. Monthly billing, where selected, is a payment schedule for the annual commitment rather than a monthly-term subscription.

Yes, monthly billing is listed for the Commercial annual commitment, because the offer set includes both annual upfront billing and monthly billing on the one-year term. Annual upfront billing is the lower listed per-unit option, while monthly billing spreads payment across the annual commitment.

No, a trial is not listed for Cross-Tenant Shared Data Migration, because the source offer set marks the product as having no trial. Buyers should validate scope and prerequisites before purchase rather than relying on a trial period.

Confirm the quantity basis before ordering, because the source offer set does not specify the Microsoft-defined unit of measure, assignment model, or whether licensing is based on users, data objects, tenants, or another measure. IT Partner should validate the correct quantity against Microsoft’s current rules for your migration scenario.

No, do not treat this SKU as a base productivity license, because the source describes it as a migration offer and does not grant workload-specific Microsoft 365, Teams, SharePoint, or Exchange service rights. Any required base services or user licenses should be confirmed separately before the migration plan is finalized.

Not necessarily, because the source offer set does not confirm which workloads are covered, including Teams-connected content, shared channels, chats, or Teams files. If Teams is in scope, confirm the supported Teams migration scenarios, prerequisites, and tooling requirements with IT Partner before purchase.

The name suggests shared data migration is in scope, but the source does not specify the exact workloads covered, because no Microsoft workload entitlement details are included in the offer data. Confirm whether SharePoint sites, Teams-connected files, OneDrive content, or other shared data scenarios are covered before relying on the SKU for those workloads.

Do not assume it is required for Microsoft 365 Copilot, because the source offer set does not mention Copilot, semantic indexing, or Copilot-specific migration rights. If Copilot readiness or tenant consolidation is part of your project, validate the licensing and data-governance requirements with IT Partner.

The current source data does not confirm whether Cross-Tenant Shared Data Migration is an add-on or what prerequisite product may be required. Because prerequisites can affect eligibility and ordering, confirm any required base subscriptions, tenant configuration, and admin permissions before purchasing.

Possibly, but those business scenarios should be confirmed against Microsoft’s current documentation, because the source offer set does not list supported use cases by transaction type. IT Partner can help validate whether your merger, acquisition, divestiture, or restructuring project matches the supported purchase and migration scope.

Confirm this before purchase, because the source offer set does not state whether licensing is required in the source tenant, target tenant, or both. This is a critical ordering detail for cross-tenant projects and should be validated against Microsoft’s current rules for your scenario.

Review identity, admin permissions, cross-tenant access settings, data residency, retention, eDiscovery, sensitivity labels, and audit requirements, because a cross-tenant migration can affect regulated data and governance controls. The SKU listing does not define security configuration or compliance outcomes, so those controls should be designed and documented as part of the migration plan.

No, do not treat the SKU as a compliance guarantee, because the source offer set does not define residency, regulatory, retention, or audit commitments. Residency and compliance depend on the Microsoft cloud environment, tenant configuration, workload behavior, and the customer’s governance requirements.

Not from the current Commercial offer set, because the source lists Commercial as the only present segment. Government, GCC, GCC High, DoD, and residency-specific requirements should be validated through the appropriate government cloud licensing channel rather than assumed from a Commercial SKU.

Not in the current source offer set, because it lists only the Commercial segment and does not show Charity, nonprofit grant, Education, student, or faculty variants. Nonprofit and education buyers should ask IT Partner to confirm whether a separate eligible offer exists before planning budget or eligibility.

Usually a CSP relationship or subscription administration transfer is a billing and partner-management change rather than a data migration, so it should not by itself require workload downtime. However, eligibility, timing, renewal state, and Microsoft commerce rules should be checked before the transfer so the subscription remains continuously covered.

The Microsoft offer remains the same Commercial product and term structure when purchased through CSP, because the listed offer is the same Cross-Tenant Shared Data Migration annual-commitment SKU. Partner invoices, taxes, billing dates, and applicable commercial terms can vary, so confirm the final quote and transfer timing with IT Partner.

For annual-commitment CSP subscriptions, increases are typically easier than reductions, because reductions or cancellations are usually restricted after Microsoft’s cancellation window and then handled at renewal. The exact rules for this offer and its quantity basis should be confirmed before ordering, especially because the source does not specify whether the unit behaves like a seat, migration entitlement, or another measure.