Info-only journal entry · Microsoft 365 Copilot

Moving Copilot between tenants after an acquisition

Copilot moves in three pieces: people and content, memory, and agents. Here's what moves and what doesn't.

Information-only Public documentation summary Owner-reviewed as of 2026-11-05 Not a code, adoption, or activity signal
Browse info-only entries
Original state to designed value

What this entry explores.

Customer-neutral framing only. This description does not establish deployment, adoption, or results.

01 / Original state

Before the pattern

Acquisition planning can treat Copilot as one movable product even though user content, personalization, and agent assets follow separate processes.

02 / Description

What this entry covers

A customer-neutral reading guide distinguishes the migration paths for Microsoft 365 content, Copilot memory and personalization, Copilot Studio agents, and other Power Platform assets.

03 / Designed value

Value hypothesis

The design is intended to help teams plan identity, content, agent, and governance work as separate migration steps.

Evidence label: Designed value: a concise map of distinct tenant migration paths and the decisions that remain for people to plan.

Synthetic overview

A high-level public-safe pattern.

People and content, memory and instructions, agents and flows, then governance and a pilot form separate migration stages.

Moving Copilot between tenants after an acquisition architecture People and content, memory and instructions, agents and flows, then governance and a pilot form separate migration stages. 01 People and content 02 Memory and instructions 03 Agents and flows 04 Govern and pilot
01 / People and content

Create target identities, map users, and plan Microsoft 365 content migration.

02 / Memory and instructions

Set expectations for personalization that has no documented migration path.

03 / Agents and flows

Move supported solutions, reconnect dependencies, and rebuild unsupported assets.

04 / Govern and pilot

Restore target-tenant controls, test representative users, and cut over in waves.

Capabilities

What the concept is designed to support.

  • Separates user content moves from identity creation and mapping.
  • Distinguishes Copilot memory and personalization from mailbox content.
  • Summarizes solution-based migration of Copilot Studio agents and required follow-up.
  • Highlights rebuild and governance work beyond Microsoft 365 migration tools.
Human control and guardrails
  • Identity creation and content migration remain separate steps.
  • No migration path is claimed for Copilot memory or personalization.
  • The description contains no customer-specific tenant details or private migration links.
Limitations and disclosure
  • Information-only summary of public documentation; no customer migration or tenant configuration is described.
  • This personal project log is not a Microsoft product or officially supported offering.
  • Migration requirements and preview features may change; verify current guidance before planning.