Microsoft Forms tenant-to-tenant migration: options, limitations, and checklist

Microsoft Forms is often overlooked in Microsoft 365 tenant-to-tenant projects, but surveys, quizzes, registration forms, file-upload questions, Power Automate flows, Teams tabs, and embedded links can all break if they are not included in the migration plan.

What Microsoft Forms migration really means in 2026

Microsoft Forms tenant-to-tenant migration is the process of moving or recreating forms, quizzes, polls, response history, ownership, and integrations from one Microsoft 365 tenant to another. It is common during mergers, acquisitions, divestitures, rebranding, and tenant consolidation projects.

Unlike Exchange Online, OneDrive, SharePoint Online, or Microsoft Teams, Microsoft Forms does not have a comprehensive native Microsoft tenant-to-tenant migration tool that preserves everything. In most projects, Forms migration is a controlled rebuild, duplicate, export, archive, and reconfigure process rather than a full-fidelity migration.

That distinction is important: form URLs, form IDs, response collection links, QR codes, embed codes, collaborators, ownership, and connected workflows usually cannot be preserved across tenants. A successful Forms migration therefore depends on discovery, impact analysis, user communication, and careful post-migration validation.

Migration options for Microsoft Forms

There are several practical approaches, depending on how important each form is and what must be preserved.

1. Duplicate or recreate the form in the target tenant. Where available, a form owner can share a form as a template or duplicate link so another user can recreate the form structure in the destination tenant. This can help copy questions and layout, but it is not a complete migration. It does not preserve the original form ID, response link, permissions, historical responses, integrations, or all settings.

2. Manually rebuild critical forms. For business-critical quizzes, external forms, regulated workflows, and forms with complex branching or file uploads, manual rebuild and testing is often the safest approach. This also gives the team an opportunity to remove obsolete forms and standardize naming, ownership, and permissions.

3. Export responses for archive or reporting. Historical responses can usually be exported to Excel for retention, audit, or reporting. In many cases, response history is archived rather than re-imported into a newly created form, because Forms does not provide a full native response import process that recreates the original response experience.

4. Move ownership within the same tenant where applicable. Microsoft Forms supports some ownership changes inside the same tenant, such as moving a personal form to a Microsoft 365 group. This can help with pre-migration cleanup, but it is not a cross-tenant migration method.

5. Evaluate third-party tools carefully. Some Microsoft 365 migration platforms may include limited Forms-related capabilities, but support varies. Validate the exact scope before relying on a tool: questions, quizzes, branching, themes, collaborators, responses, file-upload questions, ownership mapping, and workflow connections are not always supported.

What can and cannot be migrated

Use this matrix during planning and vendor validation.

Item	Typical migration result
Form title, description, and questions	Often recreated manually or copied by template/duplicate link, depending on form complexity.
Quiz questions and scoring	May need manual validation; points, correct answers, feedback, and settings should be checked carefully.
Branching logic	Must be tested after recreation; complex branching can require manual adjustment.
Themes and formatting	May not transfer exactly; validate branding in the target tenant.
Collaborators and co-owners	Usually need to be recreated in the target tenant.
Ownership	Must be assigned to a target-tenant user or Microsoft 365 group; original ownership cannot simply be preserved across tenants.
Historical responses	Usually exported to Excel for archive/reporting; not always re-imported as native Forms responses.
File-upload questions	Require separate handling because uploaded files are stored in OneDrive for Business or SharePoint, depending on form ownership.
Sharing links and public response links	New links are generated; old links generally cannot be preserved.
QR codes and embed codes	Must be regenerated and redistributed.
Teams tabs and SharePoint page embeds	Must be updated to point to the new form.
Power Automate flows	Must be reviewed and reconnected or rebuilt in the target tenant.
Excel workbooks, Power BI reports, and downstream reporting	Must be reconnected to exported data or new response sources.
Analytics and response summaries	May not migrate with full fidelity; validate reporting requirements before cutover.

Pre-migration discovery checklist

Before moving anything, inventory Microsoft Forms usage across the source tenant. The goal is to identify which forms are still active, who owns them, and what business processes depend on them.

Recommended discovery items include:

• Personal forms owned by individual users.
• Group forms owned by Microsoft 365 groups or Teams-connected groups.
• Form owners, collaborators, and business stakeholders.
• Active forms that are still collecting responses.
• Forms shared externally or configured for anonymous responses.
• Quizzes used for training, compliance, onboarding, or education.
• Forms with file-upload questions.
• Response volumes and retention requirements.
• Forms embedded in Microsoft Teams, SharePoint pages, intranet portals, or public websites.
• Forms connected to Power Automate flows, Excel workbooks, Power BI reports, CRM systems, ticketing systems, or third-party applications.
• Forms used in regulated, HR, finance, customer-facing, or operational processes.

This inventory should be coordinated with the broader Microsoft 365 tenant-to-tenant migration plan, including Exchange Online, SharePoint Online, OneDrive, Teams, Microsoft Entra ID users and groups, Microsoft Entra external users, app registrations, and Power Platform workloads.

Recommended migration process

Step 1: Classify forms. Separate forms into categories: retire, archive only, recreate, recreate with responses exported, or rebuild with integrations.

Step 2: Prepare the target tenant. Create target users, Microsoft 365 groups, Teams, SharePoint sites, and required permissions. Make sure identity mapping is aligned with the Microsoft Entra ID migration plan.

Step 3: Export response data. Export responses to Excel where historical data must be retained. Store the archive in the appropriate SharePoint site, OneDrive location, records repository, or compliance location in the target tenant.

Step 4: Recreate forms. Use template/duplicate links when appropriate, or manually rebuild forms in the target tenant. Validate questions, required fields, branching, quiz scoring, themes, and settings.

Step 5: Handle file uploads. Identify where uploaded files are stored in the source tenant. Personal forms typically store uploaded files in the owner’s OneDrive for Business, while group forms typically store files in the associated SharePoint location. Migrate or archive those files as part of the OneDrive or SharePoint migration workstream, and do not assume they will automatically reconnect to the new form.

Step 6: Reconnect integrations. Update Power Automate flows, Teams tabs, SharePoint pages, Excel reporting files, Power BI datasets, public website embeds, intranet links, and third-party integrations.

Step 7: Communicate new links. Because form URLs, IDs, QR codes, and embed codes generally change, notify users and external audiences before cutover. Replace links in emails, documents, Teams channels, SharePoint pages, websites, and automated messages.

Step 8: Validate after cutover. Submit test responses, check notification flows, verify file uploads, confirm permissions, and validate reports. Keep the source forms available in read-only or controlled access mode for an agreed retention period when business or compliance requirements allow.

Common issues and how to avoid them

Broken response links are the most common user-facing issue. Treat every active Forms link as a dependency that must be replaced.

Power Automate flows often fail after migration because connectors, form IDs, owners, permissions, and target lists or mailboxes change. Rebuild and test flows instead of assuming they will continue to work.

File-upload questions need special attention. The form may be recreated, but the uploaded files live in OneDrive or SharePoint and must be handled by the correct migration workstream.

Permissions and ownership should not be left with individual users when the form supports a business process. For important forms, consider group ownership where appropriate so continuity does not depend on one employee account.

External and anonymous forms require change management. Public links, QR codes, website embeds, and partner communications must be updated on a planned schedule.

Historical response data should be treated as records. If full native response migration is not possible, export, label, store, and document the data so users know where to find prior responses.

Where Microsoft Forms fits in a tenant-to-tenant migration

Microsoft Forms should be included in the application and collaboration discovery phase, not treated as an afterthought. Forms often connect multiple workloads: Microsoft Entra ID for users and groups, Teams for collaboration, SharePoint and OneDrive for files, Power Automate for workflows, Excel and Power BI for reporting, and app registrations or third-party services for integrations.

For small tenants, Forms migration may be a short checklist. For larger organizations, it can become a business-process migration task because forms are frequently used for HR requests, training quizzes, customer feedback, safety checks, event registration, onboarding, and internal approvals.

The safest approach is to decide early which forms must be rebuilt, which responses must be retained, which links must be replaced, and which workflows must be reconnected before users are moved to the target tenant.

Key takeaways

• Microsoft Forms does not have a full native tenant-to-tenant migration tool comparable to major Microsoft 365 workloads.
• Most Forms migrations are handled through recreation, template-based duplication, response export, archive, and reconfiguration.
• Form URLs, form IDs, sharing links, QR codes, embed codes, permissions, and integrations generally change across tenants.
• File-upload questions require separate OneDrive or SharePoint handling.
• Power Automate flows, Teams tabs, SharePoint embeds, Excel workbooks, Power BI reports, and public website links must be updated and tested after migration.

Planning a Microsoft 365 tenant-to-tenant migration? IT Partner can help you discover Microsoft Forms dependencies, migrate the core Microsoft 365 workloads, rebuild critical forms, reconnect Power Automate and collaboration integrations, and prepare a practical cutover plan.