Microsoft Forms Migration Comparison 2026: Automated vs Manual Options Compared

Quick Answer

Microsoft has no native tool that migrates Microsoft Forms between tenants, so every Forms migration is either automated with a third-party tool or done manually. Based on Microsoft and vendor documentation, there are four real options:

• Apps4.Pro automated Forms migration moves personal and group forms, quizzes, branching, themes, settings, collaborators, file upload attachments, and responses in bulk. It is the only third-party tool we found that documents Microsoft Forms tenant-to-tenant migration.
• Manual Duplicate copies one form’s structure at a time into the target tenant. Responses, attachments, sharing, and collaborator permissions stay behind.
• Manual Excel export keeps a static snapshot of past responses, but no working form.
• Microsoft native tools (Migration Orchestrator and Cross-Tenant User Data Migration) do not include Forms.

For forms with responses, uploads, quizzes, or many owners, automated migration is the only option that keeps everything together. Manual Duplicate and Excel export suit a handful of simple forms or archiving.

Key Takeaways

• Migration Orchestrator supports four workloads: Exchange mailboxes, OneDrive, Teams chats, and Teams meetings. Forms is not one of them (Microsoft Learn).
• Manual Duplicate copies structure only, one form at a time. Responses, file upload attachments, sharing, collaborator permissions, quiz grading rules, and answer explanations must be rebuilt or are lost.
• Manual Excel export is a safety net, not a migration: old responses are never linked to the new form, and uploads appear only as file links.
• Forms data is deleted 30 days after a user account is deleted, and forms of hard-deleted accounts cannot be recovered (Microsoft Learn).
• Sharegate states it does not support Microsoft Forms (ShareGate help), and other major migration tools do not document it.
• Apps4.Pro migrates responses as live data in the target form. Because of API limits they are posted by the migration service account, and incremental runs and group-level permissions are not supported (Apps4.Pro guide).

What a Microsoft Forms Migration Has to Handle

Microsoft Forms looks simple during a tenant-to-tenant migration but becomes messy when moved manually. Admins must handle long lists of forms, re-create questions, rebuild branching and quiz logic, and avoid missing live surveys.

The hardest parts are preserving existing responses and file upload attachments while keeping themes, sharing links, and permissions intact. Manual work does not scale, and gaps such as forgotten forms, lost history, and inconsistent settings are common.

• Forms belong to people, not sites. Personal forms are tied to the account that created them, not to a SharePoint site or mailbox that other migration tools already move.
• Responses and files live in different places. Responses are stored with the form, while files uploaded by respondents are stored in OneDrive or SharePoint, so both must move and stay linked.
• Group forms depend on groups. The matching Microsoft 365 group must exist in the target before group forms can move.
• Every recreated form gets a new URL. Links in emails, SharePoint pages, Teams tabs, QR codes, and Power Automate flows must be updated.
• The deletion clock is short. Forms data is deleted 30 days after the owner’s account is deleted.

For a broader step-by-step overview, see the Microsoft Forms Migration Guide.

How We Compared the Options

We compared the four options on what moves, what is lost, effort, and cost. Sources, in priority order, were Microsoft Learn and Microsoft Support, vendor documentation, and Microsoft Q&A. We also checked the public documentation of ShareGate, AvePoint Fly, Quest On Demand Migration, BitTitan MigrationWiz, Cloudiway, CloudFuze, Kernel, and SysTools for Forms support.

What this review is not: a lab benchmark. We report no speed numbers of our own. All information was checked in October 2026.

Microsoft Forms Migration Options at a Glance

There are four real options for Microsoft Forms migration. Apps4.Pro is the only one of the four designed to keep layout, live responses, file uploads, quiz grading, themes, and permissions together in one migration.

Feature Comparison: Apps4.Pro vs Manual Duplicate vs Excel Export vs Microsoft Native

Takeaway: Microsoft native tools do not cover Forms at all, so the real choice is between partial manual migration and automated migration with Apps4.Pro. For field-level detail, see the Microsoft Forms Migration knowledge base guide.

Which Forms Migration Option Fits Your Scenario?

See Apps4.Pro Microsoft Forms Migration in Action

Stop relying on manual workarounds. Review the supported scenarios on the Apps4.Pro Microsoft Forms Migration tool page and start a free trial, which includes a pre-migration inventory report.

1. Apps4.Pro Automated Forms Migration: Best Overall for Complete Forms Tenant-to-Tenant Migration

Apps4.Pro Migration Manager migrates Microsoft Forms between tenants with a tenant-level, policy-friendly approach that fits Microsoft 365 governance, as part of the same platform that migrates mailboxes, OneDrive, Teams, and SharePoint.

You connect once to each tenant. The tool needs minimum privileges similar to an Office Apps Administrator account, with Modern Authentication and MFA, plus specific Forms permissions.

How automated Forms migration works

1. Discover all personal and group forms, including orphaned forms.
2. Map users and groups across tenants with auto-map or CSV import.
3. Generate the inventory report, showing created and modified dates, response counts, question counts, and upload question counts.
4. Select forms and start migration, with built-in retry logic and task tracking.
5. Verify forms, responses, and attachments in the target tenant against the source.

Responses migrate as live data linked to the migrated forms, so admins see the same summary and detailed views. Users can keep analyzing results, export to Excel, and use question-wise and respondent-wise views. See Microsoft Forms Migration with Real-Time Responses.

What it migrates

Form and quiz definitions, all supported question types with branching, responses as real-time linked data, file upload attachments, themes and branding, collaborator permissions, and form settings. Per the Apps4.Pro knowledge base guide:

• Personal (user) forms, group forms, and form collections, including quizzes.
• Question attributes such as required, subtitle, and restrictions.
• Settings (collect-response options, response receipts) and styles (background, custom theme, colors, images, background music).
• Images, videos, and file attachments. Respondent uploads go to the group form’s SharePoint with permissions applied.
• Collaborator permissions, which can be skipped by removing their mappings.

Documented limitations

• Responses are posted by the service account because of API limitations.
• Group-level permissions are not migrated, and incremental migration is not supported.
• User forms with upload-type questions become group forms. On those forms you cannot add new collaborators or new upload-type questions after migration.
• Connector accounts need a Forms-enabled license and the Office Apps Administrator role with admin consent, and must be members of the groups that own group forms.

Pricing

• $5,995 for a single-machine installation (Essentials), supporting up to 300 Forms, or $8,995 for a five-machine installation (Growth), supporting up to 500 Forms. The Enterprise plan costs $17,995 for 20+ machine installations and supports up to 2,000 Forms. A 15-day free trial is available, and a free pre-migration inventory report is included.

Best fit: mergers and consolidations with many forms, or forms with responses, uploads, quizzes, or compliance value.

Not a fit: projects that need responses to show the original respondent as the submitter, or ongoing incremental syncs.

2. Manual Duplicate in Microsoft Forms: Best for a Few Simple Forms

Duplicate copies the form or quiz structure into a new instance owned by you or a chosen group.

What manual Duplicate copies

• It copies the structure, questions, format, and layout to another owner or group where you have access.
• How it works across tenants: the owner shares the form as a template link in the source tenant, opens it while signed in to the target tenant, and selects Duplicate (Microsoft Support).

What manual Duplicate does not carry over

• Responses, file upload attachments, sharing configuration, historical data, and collaborator permissions.
• You must rebuild sharing, quizzes, grading rules, and answer explanations manually.
• You must manage new URLs and cutover dates yourself.
• Branching must be rebuilt manually, which is error-prone, and themes must be recreated.
• It works one form at a time. This overhead grows quickly across many critical forms.

Pricing

• No tool cost, but admin and owner time for every form.

Best fit: a handful of simple forms with no responses or uploads worth keeping.

Not a fit: forms with responses, quizzes that need scores, or large numbers of forms.

3. Manual Excel Export: Best for Archiving Responses

Excel export gives a static snapshot of responses in an .xlsx file, stored in OneDrive or locally. It is a safety net, not a migration.

What Excel export keeps

• A static snapshot of answers from the source form.
• Upload questions appear as file links only; the files stay in source OneDrive or SharePoint storage.

What Excel export loses

• New responses to a recreated form live separately, so old and new data are never in one continuous history.
• There is no live view of legacy responses in the new form.
• Branching, quiz scores, themes, and permissions are not included.
• Attachments must be tracked manually.

Pricing

• No tool cost, but per-form manual effort.

Best fit: retired forms whose responses must be kept for records or audit. Often combined with manual Duplicate.

Not a fit: any form that must keep collecting responses with its history intact.

4. Microsoft Native Tools: No Forms Workload

Microsoft’s native cross-tenant migration covers Exchange mailboxes, OneDrive, and Teams chats or meetings. Forms is not included.

What Microsoft’s tools cover

• Migration Orchestrator and Cross-Tenant User Data Migration (CTUDM) move user-level data. Microsoft lists four supported workloads: Exchange mailboxes, OneDrive, Teams chats, and Teams meetings (Microsoft Learn).
• Even with Migration Orchestrator and FastTrack, teams need a separate strategy to protect Forms, quizzes, responses, and attachments.
• Microsoft Graph API offers no complete, supported way to recreate forms, quizzes, responses, and attachments across tenants with full fidelity.
• Ownership transfer (same tenant only): an Office Apps administrator can transfer forms of disabled or recently deleted users to another user or group in the same tenant, within 30 days of deletion. It does not move forms to another tenant, but it can rescue forms of departing source users until they are migrated (Microsoft Learn).

Pricing

• Cross-tenant user data migration requires a one-time per-user license for the workloads it supports; it adds nothing for Forms.

Best fit: mailboxes, OneDrive, and Teams chats, alongside a separate Forms plan.

Not a fit: any Forms migration.

Migration Tools Without Documented Forms Support

ShareGate states that “Microsoft Forms is a Microsoft 365 workspace that ShareGate Migrate currently does not support” (ShareGate help). AvePoint Fly, Quest On Demand Migration, BitTitan MigrationWiz, Cloudiway, CloudFuze, Kernel, and SysTools do not document Microsoft Forms migration on their public pages (checked October 2026).

Unique Insight: Where Your Forms Responses Actually Land

Unique Insight: Microsoft Limits That Shape a Forms Migration

Sources: Microsoft Support: Forms limits, Microsoft Learn: Forms admin information.

Pricing Compared

How to Choose: Automated or Manual? A 6-Step Checklist

1. Inventory every form. List personal, group, and orphaned forms with owners, response counts, upload questions, and where each form is linked or embedded.
2. Protect forms of departing users. Transfer ownership of forms owned by disabled or deleted accounts before the 30-day window closes.
3. Sort forms by method. Use automated migration for forms with responses, uploads, quizzes, or compliance value; manual Duplicate only for simple forms; manual Excel export for responses you only need to archive.
4. Prepare the target. Create and license target users, create Microsoft 365 groups for group forms, and check the 400-form limit.
5. Migrate and validate. Compare question and response counts, open uploaded files, and test branching and quiz scoring.
6. Update every link. Replace form URLs in emails, SharePoint pages, Teams tabs, QR codes, and Power Automate flows, then retire the source forms.

Related Reading

• Microsoft Forms Migration Guide
• Microsoft Forms Migration with Real-Time Responses
• Benefits of Apps4.Pro for Microsoft Forms Tenant Migration
• Microsoft Forms Migration knowledge base guide
• Apps4.Pro Microsoft Forms Migration tool
• Microsoft Forms Quiz Migration for Education Tenants
• Microsoft Forms Pre-Migration Inventory Risks for MSPs
• Microsoft Forms Migration in Mergers and Acquisitions
• When You Need Microsoft Forms Tenant-to-Tenant Migration
• Microsoft 365 Tenant-to-Tenant Migration
• Apps4.Pro Migration Manager

Frequently Asked Questions: Automated vs Manual Microsoft Forms Migration