Microsoft Copilot App Merger: Migration Checklist
Treat the app merger as a records, permissions, and workflow migration—not a cosmetic navigation update.
Bottom line
A practical Copilot app-merger checklist for inventories, exports, permissions, acceptance tests, communications, and rollback.
Editorial accountability
Who checked this guide
- Evaluation type
- Research-based verification
- Last materially checked
- Evidence
- 4 listed sources
Hands-on testing is identified explicitly. Research-based coverage uses cited product documentation and other named sources; it does not imply every paid plan was used. Read the full methodology.
Editorial basis
What this guidance is based on
- Editorial basis
- Source-led analysis
- Primary references
- 4
- Products covered
- 1
- Last checked
- 2026-10-01
Important limits
- • Tenant, platform, license, and rollout timing can change the migration path.
- • This guide does not replace Microsoft's tenant-specific administration guidance.
In this guide
*This operational guide was reviewed against Microsoft's Copilot release, support, privacy, and administration materials on October 1, 2026. Exact availability varies by plan, tenant, platform, and rollout ring.*
Short answer
Before a Copilot app merger reaches your users, inventory every affected workflow, preserve important artifacts, re-check identity and sharing, test critical jobs in the destination app, and keep a time-bounded rollback path. A familiar feature name does not guarantee identical storage, permissions, connectors, retention, or output.
1. Build the affected-work inventory
List the old app, feature, owner, users, data source, outputs, recurring prompts, agents, connectors, licenses, compliance boundary, and business deadline. Mark features that are removed, renamed, relocated, or only partly reproduced. Separate official Microsoft statements from assumptions based on similar labels.
Use the [Copilot app-merger change analysis](/articles/microsoft-copilot-app-merger-features-removed-2026) to identify announced feature removals before completing the inventory.
2. Preserve what matters
Export or document saved prompts, instructions, notebooks, agents, files, conversation records, templates, automations, and sharing lists where the product permits it. Record the source URL, date, owner, and retention requirement. Do not bulk-copy sensitive chat history merely because migration is happening.
3. Revalidate access
Test with ordinary user, manager, guest, and restricted accounts. Confirm the destination respects source permissions, sensitivity labels, conditional access, data-loss prevention, retention, eDiscovery, and deletion. Remove obsolete connectors and broad delegated permissions before reauthorizing anything.
4. Replay business tasks
Create a test pack of real but safe work: document summaries, searches, drafts, meeting follow-up, spreadsheet analysis, and one denied-access case. Compare completeness, citations, formatting, sharing behavior, latency, and reviewer correction. A migration is complete only when the task works—not when the new icon opens.
5. Communicate the delta
Tell users what moved, what disappeared, where records live, which behavior changed, when the old route ends, how to report a problem, and what not to copy. Provide one-page instructions for the top workflows instead of a generic product tour.
6. Stage rollout and rollback
Pilot with a representative group, pause new configuration in the retiring app, monitor access and failure events, then expand by team. Define who can stop the rollout and how work continues manually. Preserve a reconciliation list so actions taken in both systems are not duplicated.
Bottom line
The risk in an app merger is silent change: missing history, broader access, broken automation, or a feature that looks equivalent but behaves differently. Inventory, export, test, stage, and reconcile.
Sources and verification
Product details and claims were checked against the following primary sources.
Frequently asked questions
What should I back up before a Copilot app merger?
Preserve business-critical prompts, instructions, agents, templates, files, outputs, connector settings, owners, and sharing rules where export is supported.
Will Copilot permissions stay the same after migration?
Do not assume they will. Test source access, labels, guest behavior, connectors, retention, and deletion with representative accounts.
How do I know the new Copilot app is equivalent?
Replay the same business tasks and compare evidence, output, permissions, latency, correction effort, and downstream actions.
Do I need a rollback plan for a SaaS app merger?
Yes. Define a manual or legacy path for critical work, a stop authority, and a method for reconciling work performed during the transition.
Tools mentioned in this article
Microsoft Copilot
Workplace AI grounded in Microsoft 365 apps, organizational data, and governed agents
Microsoft Copilot is strongest for organizations already operating in Microsoft 365, but licensing, permission hygiene, content quality, agent usage, and change management determine the return.
Read next
