The deal is signed. The champagne’s been popped in the boardroom. And now, somewhere in a windowless office, an IT team stares at a spreadsheet titled “Tenant Consolidation Workload Inventory” with hundreds of line items for Exchange, SharePoint, Teams, and OneDrive.
But there’s one workload conspicuously missing: Microsoft Forms.
It’s not malice. It’s not laziness. It’s just that Forms flies under the radar until the source tenant gets decommissioned and thousands of customer surveys, compliance questionnaires, and HR onboarding forms vanish into the void. Permanently.
If you’re part of an M&A IT integration team planning an M365 tenant consolidation, this guide will show you why Microsoft Forms deserves a seat at the migration table and how to make sure it gets one.
Why M&A Is the #1 Trigger for Tenant Migration
Mergers, acquisitions, and divestitures are the single most common reason organizations undertake tenant to tenant migration. When Company A acquires Company B, the IT roadmap almost always includes consolidating both organizations into a single Microsoft 365 tenant. The reasons are straightforward:
- Unified Global Address List - one directory, one identity platform
- License optimization - eliminating duplicate subscriptions
- Security posture - a single tenant is easier to govern than two
- Collaboration - seamless Teams, SharePoint, and email communication across the merged entity
Most M&A integration teams follow a well-established Office 365 migration checklist that covers the “big five” workloads: Exchange Online, SharePoint Online, OneDrive, Teams, and Azure AD. These get dedicated project streams, wave planning, and executive sponsors.
Forms? It usually shows up as a panicked Slack message three weeks before the source tenant is scheduled for decommission.
The “Forgotten Workload” Problem
Microsoft Forms doesn’t generate the same volume of storage as SharePoint or OneDrive, so it rarely appears in tenant analytics dashboards. It doesn’t have its own admin center with neat usage reports that jump off the screen. And because individual users – not IT – create most Forms, there’s no centralized inventory.
This creates a dangerous blind spot. Here’s what’s actually living inside Forms across a typical enterprise tenant:
- Customer satisfaction surveys tied to CRM workflows
- Regulatory and compliance questionnaires (GDPR data subject requests, SOX controls checklists, safety incident reports)
- HR onboarding and offboarding forms collecting PII
- Internal audit forms with historical response data
- IT service request forms embedded in SharePoint and Teams
- Training assessments and quizzes with completion records
Each of these carries data that may be subject to legal hold, regulatory retention, or contractual obligations. Losing them isn’t just inconvenient – it’s a compliance risk.
What Happens to Forms When the Source Tenant Dies
Let’s be blunt: when a Microsoft 365 tenant is decommissioned, every Form in that tenant is permanently deleted. There is no recycle bin. There is no grace period. The form definitions, all collected responses, branching logic, and sharing permissions – gone.
Unlike SharePoint (which supports export to migration packages) or Exchange (which has PST export), Forms has no native bulk-export mechanism provided by Microsoft. You can manually download individual response spreadsheets one at a time, but that gives you only the data - not the form structure, not the logic, not the integrations with Power Automate flows, and not the sharing links embedded across your intranet.
For organizations operating under a Transition Services Agreement (TSA), this is especially critical. TSAs define a contractual window, typically 6 to 18 months during which the divesting entity continues to provide IT services to the carved-out business unit. Once that window closes and the source tenant is shut down, anything not migrated is lost.
The TSA Deadline Trap
Here’s how it typically plays out:
- Month 1–3: Migration team focuses on identity, Exchange, and SharePoint.
- Month 4–6: Teams and OneDrive migrations begin. Someone asks, “What about Forms?” It gets added to a backlog.
- Month 7–9: Power Platform, Power Automate, and Power BI migrations reveal downstream dependencies on Forms.
- Month 10–12: The backlog item for Forms gets prioritized but now there’s limited runway before the TSA expires.
- Month 13+: Panic mode. Manual exports. Incomplete data. Broken integrations.
The fix is simple in principle: include Forms in your migration playbook from Day 1.
Forms as a Compliance Risk During M&A
M&A transactions are compliance-intensive events. Regulatory bodies, auditors, and legal teams scrutinize data handling practices closely during integration. Microsoft Forms often contains data that falls squarely within compliance scope.
Customer-Facing Surveys
If the acquired company used Forms for NPS surveys, product feedback, or support satisfaction scores, the response data may be contractually required to transfer with the business. Losing this data could violate customer agreements or impact ongoing service commitments.
Regulatory and Audit Forms
SOX compliance checklists, safety inspection forms, environmental reporting questionnaires – these are audit artifacts. Regulatory bodies expect you to retain them for defined periods (often 5–7 years). Decommissioning the source tenant without migrating these forms could trigger an audit finding.
HR and PII-Containing Forms
Onboarding forms, benefits enrollment questionnaires, and employee feedback surveys contain personally identifiable information. Under GDPR, CCPA, and India’s DPDP Act, you have obligations around data portability and retention. You can’t fulfill a data subject access request for data that no longer exists.
Legal Hold and eDiscovery
If the acquired entity is subject to active litigation, any Forms data relevant to the case may be under legal hold. Decommissioning the tenant without preserving this data could constitute spoliation of evidence – a serious legal issue.
How to Include Forms in Your M&A Migration Playbook
A solid Microsoft Forms M&A migration strategy has five phases. Here’s how to build it into your broader tenant migration checklist:
Phase 1: Discovery and Inventory
Before you can migrate Forms, you need to know what exists. This is harder than it sounds because Forms doesn’t have a centralized admin inventory.
- Use PowerShell and Microsoft Graph API to enumerate all Forms across the source tenant
- Identify form owners, creation dates, response counts, and last-modified dates
- Flag forms embedded in SharePoint pages, Teams tabs, or Power Automate flows
- Classify forms by business criticality: compliance-critical, business-critical, nice-to-have, and obsolete
Phase 2: Stakeholder Alignment
Forms are created by business users, not IT. You need their input.
- Notify form owners that migration is happening and gather requirements
- Work with Legal and Compliance to identify forms under retention obligations or legal hold
- Coordinate with HR, Finance, and Operations to prioritize business-critical forms
Phase 3: Pre-Migration Preparation
- Document form structures, branching logic, and connected workflows
- Export response data as a backup (Excel downloads per form)
- Map source tenant users to target tenant identities for ownership reassignment
- Identify Power Automate flows triggered by Forms and plan their migration separately
Phase 4: Migration Execution
This is where manual methods hit a wall. Manually recreating hundreds of forms in a new tenant with branching logic, response data, and permissions intact is impractical at scale.
A purpose-built migration tool like Apps4.Pro Microsoft Forms Migration can automate this process, preserving form structure, response data, ownership, and sharing settings during a tenant to tenant migration. For a detailed walkthrough, see the Microsoft Forms Migration Guide.
Phase 5: Post-Migration Validation
- Verify form structures, branching logic, and response data in the target tenant
- Test embedded links in SharePoint pages and Teams tabs – update URLs as needed
- Reconnect Power Automate flows to migrated Forms
- Confirm ownership and sharing permissions match the target tenant’s identity map
- Decommission source forms only after stakeholder sign-off
For step-by-step technical guidance on each phase, the Forms migration knowledge base is a solid reference.
A Quick M&A Forms Migration Checklist
| Task | Owner | Phase |
|---|---|---|
| Enumerate all Forms in source tenant | IT Migration Team | Discovery |
| Classify forms by compliance and business criticality | Legal + Business Units | Discovery |
| Identify forms under legal hold or regulatory retention | Legal / Compliance | Discovery |
| Map form owners to target tenant identities | Identity Team | Pre-Migration |
| Export response data as backup | IT Migration Team | Pre-Migration |
| Migrate form structures, responses, and permissions | IT Migration Team | Execution |
| Update embedded URLs in SharePoint and Teams | SharePoint / Teams Admin | Post-Migration |
| Reconnect Power Automate flows | Power Platform Team | Post-Migration |
| Stakeholder validation and sign-off | Business Units | Post-Migration |
Don’t Let Forms Be Your M&A Blind Spot
Every M&A integration has its surprises such as unexpected licensing entanglements, shadow IT discoveries, that one business unit still running a server in a closet. But losing Microsoft Forms data shouldn’t be one of them.
Forms may be lightweight in storage, but it’s heavyweight in business impact. Customer surveys inform product strategy. Compliance questionnaires satisfy regulators. HR forms onboard your people. These aren’t disposable artifacts – they’re operational assets.
The fix isn’t complicated. Add Forms to your M365 migration checklist early, run discovery before the TSA clock starts ticking, and use a migration tool that handles Forms natively so you’re not manually rebuilding hundreds of forms in the target tenant.
Your future self – the one not explaining to Legal why audit forms disappeared – will thank you.
Migrate
Manage
Migrate Microsoft 365
