Graph application permissions
- Source team, channel, member, tab, app, and setting reads
- Destination group, team, channel, membership, tab, and tag writes
- Protected `Teamwork.Migrate.All` approval for message import
Microsoft Teams
A Microsoft Teams migration tool for connected services.
The Microsoft Teams migration tool assesses teams, channel types, owners, members, guests, tabs, apps, and identity gaps. It reconstructs supported workspace structure through Microsoft Graph, can use Microsoft migration mode for channel messages when protected-API approval is present, and routes files, recordings, and meetings through their owning Microsoft 365 services. Use it to migrate Microsoft Teams to another tenant with an MS Teams migration pass that reconciles structure, membership, and settings per team.
Conditional · API dependent Split delivery pathTeam structure is Graph reconstruction. Channel-message import is conditional on Microsoft `Teamwork.Migrate.All` protected-API approval and opt-in migration mode. Files and recordings move through SharePoint/OneDrive; meetings move with Exchange calendars.
BridgeAD Cloud WorkloadsCollaboration migration workspace
Collaboration structure coordinated across servicesTeams and channels, memberships, files, meetings, API dependencies, execution state, and validation evidence remain part of one delivery view.
Product view ยท synthetic demonstration dataOperator experience
Assess readiness before creating the job.
The Teams workspace combines assessment, capability boundaries, job telemetry, and per-team outcomes. Operators can identify unmapped owners, shared-channel trust, unavailable tabs, and custom apps before choosing the destination route or enabling message import.
- Connection health, permissions, and protected-API eligibility checks
- Team and channel inventory with owner, member, guest, tab, and app counts
- Readiness classification and per-team findings
- Job creation from assessed, ready teams
- Team, channel, message, membership, tab, and tag counters
- Per-team validation and completion evidence
Capability scope
Use the delivery path that matches the artifact.
BridgeAD exposes Microsoft-native import, Graph reconstruction, cross-service migration, and manual remediation as different states. That distinction prevents a successful team-shell job from being mistaken for complete workspace fidelity.
| Area | Status | BridgeAD handling | Important boundary |
|---|---|---|---|
| Team shell and settings | Supported · Reconstructed | Creates or resolves the Microsoft 365 group and team idempotently, then applies supported member, messaging, and fun settings. | Team photos and sensitivity labels are not currently applied. |
| Channels | Supported · Reconstructed | Recreates standard, private, and shared channel structure with membership type preserved. | Shared-channel B2B Direct Connect trust must be re-established and validated in the destination. |
| Owners and members | Supported · Mapped identities | Maps source identities, adds resolvable owners and members, and counts skipped assignments. | Unmapped identities are skipped. Guest accounts must be invited and governed in the destination. |
| Channel messages | Conditional | With protected-API approval, opt-in native migration mode imports posts and replies with original author and timestamp and resumes from channel watermarks. | Requires new destination teams in Graph migration mode. Attachments are deferred to SharePoint and counted; reactions are not preserved. |
| Tabs | Supported · subset | Re-pins supported app-backed tabs with name, application, URLs, and available configuration. | Tabs backed by custom, unpublished, or unavailable apps are reported for manual recreation. |
| Team tags | Supported · Reconstructed | Recreates tags by display name with mapped members after membership exists. | Requires `TeamworkTag.ReadWrite.All`. Unmapped members are counted; tags with no mapped member need manual recreation. |
| Channel files | Conditional · Cross-service | Resolves source and destination backing-site URLs and coordinates binary transfer through the SharePoint migration service. | Files do not move through the Teams message engine and need a sequenced SharePoint pass. |
| Apps, bots, and connectors | Supported · Inventory (apps re-published manually) | Inventories installed apps and classifies store versus organization-published or sideloaded apps during assessment. | Secrets, webhooks, consent grants, bot configuration, and custom publishing are never copied automatically. |
| Validation | Supported | Compares destination teams, channels, mapped membership, and recorded item outcomes; reports mismatches and errors per team. | Cross-service content and manual remediation have their own evidence and sign-off. |
Cross-service dependencies
Teams does not own all the data users see in Teams.
A professional migration sequence assigns each artifact to the service that stores it. BridgeAD makes these dependencies visible so the collaboration plan is not reduced to team and channel provisioning.
| Artifact | Owning path | Required action | Boundary |
|---|---|---|---|
| Channel files and wiki content | SharePoint | Run the backing site through the SharePoint content pass after destination team and channels exist. | Assess unsupported pages or legacy wiki behavior separately. |
| Meeting recordings and transcripts | SharePoint / OneDrive | Include organizer OneDrive and channel-site recording locations in the content scope. | Retention, labels, and meeting metadata are separate controls. |
| Calendar meetings and webinars | Exchange | Migrate calendar items with the organizer mailbox and communicate link changes. | Webinar registration data is not migrated. |
| Meeting join URLs | Administrator action | Recreate or update recurring meetings after cutover so new destination-tenant URLs are issued. | Source-tenant join URLs are not portable. |
| Personal and group chats | BridgeAD private-chat workflow | Select source users, preview mapped members, re-create 1:1 and group chat shells, and deliver full history as self-contained HTML transcripts in each user's destination OneDrive. | Requires source protected-API approval (`Chat.Read.All`). Native in-chat history injection remains dependent on Microsoft's cross-tenant chat-migration API. |
| App secrets and webhooks | Application owner | Republish custom apps, re-consent permissions, rotate credentials, and recreate connectors. | Secrets and tenant-scoped integration endpoints are never copied. |
Prerequisites
Resolve identity and API eligibility first.
Teams migration behavior depends on Microsoft Graph roles, destination identities, group and channel constraints, and whether Microsoft has approved the tenant application for protected message-import APIs.
Mappings and collaboration policy
- Destination owners and members exist and are mapped
- Guest invitation and access-review process agreed
- Shared-channel cross-tenant trust designed and tested
Content and cutover plan
- SharePoint/OneDrive and Exchange passes scheduled
- App owners and manual remediation tasks assigned
- User communications cover chats, join links, and app changes
Migration workflow
Migrate Teams between tenants in dependency order.
A tenant-to-tenant Teams migration starts with mapped owners and members before tags and private-channel membership can be applied. Backing sites must be addressable before files move. Teams private chat migration has its own protected-API eligibility and OneDrive transcript evidence path.
Assess
Inventory teams, channels, identities, tabs, apps, archived state, and cross-tenant requirements.
Map
Resolve owners and members, destination naming, guest handling, trust, and app remediation.
Preview
Choose users or assessed teams, validate protected-API access, and review the dry-run result before creating destination artifacts.
Run and monitor
Reconstruct teams or private chats, watch per-item progress, cancel at safe boundaries, and coordinate SharePoint and Exchange passes.
Validate
Compare structure and membership, review skipped items, download chat transcripts and evidence, and close accepted work.
Delivery boundaries
Plan for the workspace users will experience after cutover.
A structurally complete team can still have changed meeting links, unconfigured apps, or governance variance. Private-chat history is retained as OneDrive transcripts rather than inserted into destination chat threads.
Graph reconstruction
- Team shells, supported settings, and channel structure
- Mapped owners, members, private/shared channel members
- Supported tabs, team tags, telemetry, and validation
Messages and private chats
- Protected-API application approval
- Channel posts through migration mode
- Private-chat shells plus full-history OneDrive transcripts
Experience remediation
- Guests, custom apps, secrets, connectors, and policies
- Webinars, join URLs, and Teams Phone
- Files, recordings, and calendars through other services
Frequently asked questions
Microsoft Teams migration questions
Can BridgeAD preserve channel-message authors and timestamps?
Yes, only through Microsoft Graph migration mode when the application has Microsoft protected-API approval and native import is enabled. That path creates new destination teams in migration mode, imports posts and replies, and then completes migration mode before normal use.
Are message attachments migrated with the post?
No. Messages with attachments are imported without those attachments and counted. The underlying files are migrated through the relevant SharePoint or OneDrive content pass.
What happens to guests and unmapped members?
Mapped destination identities are added. Unmapped users are skipped and counted. Guests must be invited and governed in the destination tenant, and their access should be reviewed before the workspace is released.
Can custom apps and connectors be copied?
Installed apps are inventoried and classified, but organization-published or sideloaded apps need republishing. Secrets, webhooks, consent grants, bot configuration, and connectors must be recreated by the application owner.
How are private and shared channels handled?
The channel membership type is preserved during reconstruction. Private-channel members depend on identity mapping. Shared channels additionally require destination cross-tenant access and B2B Direct Connect trust to be established and tested.
Related services
Sequence every Teams dependency.
Teams migration is strongest when identity, content, mailbox, and governance work share one assessed scope and one cutover plan.