Mail Tasks Migration Details
Understand what task data transfers during migrations and the limitations for different migration paths.
Overview
This guide explains what task data transfers during migrations using Cloudiway's Email Migration solution. Different migration paths (M365-to-M365 vs. Google-to-M365) support varying levels of task data transfer due to API limitations and platform differences.
Supported Migration Paths
M365 to M365
Tenant-to-tenant migration
Google to M365
Cross-platform migration
Task Migration Scope
Task migration capabilities vary by platform. Review the details below to understand what will transfer for your specific migration scenario.
M365 Tenant-to-Tenant Migration
Microsoft 365 to Microsoft 365 tenant migrations support comprehensive task data transfer, including most task properties and metadata.
What Migrates
The following task data transfers during M365 tenant-to-tenant migration:
Supported Task Data
- Default task folder
- Subfolders
- Task titles
- Completion status
- Reminders
- Repeat settings
- Categories
- Attachments
- Notes
- Favorite flag
Notes About Migrated Data
- Reminders: May appear greyed out initially but users can modify them by removing and recreating the reminder.
- Categories: Will be visible within the emails themselves and are not accessible through the user settings.
What Does Not Migrate
Due to Microsoft API limitations, certain task data cannot be transferred:
Unsupported Task Data
- Task Steps
API limitation prevents transfer of task steps/subtasks within tasks
- List Groups
Subfolders migrate independently, not as grouped collections
Google to M365 Migration
Google to Microsoft 365 migrations have more limited task transfer capabilities due to platform differences and API constraints.
What Migrates
The following Google Tasks data transfers to Microsoft 365:
Supported Task Data
- Default task list
- Other task lists (migrated as separate lists)
- Task titles
- Task descriptions
- Due dates
- Completion status
What Does Not Migrate
Due to Google API limitations, certain task data cannot be transferred:
Unsupported Task Data
- Subtasks
Google subtasks cannot be transferred during migration
Workaround for Subtasks
Before migration, consider converting important subtasks to separate top-level tasks with clear naming conventions (e.g., "Parent Task - Subtask Name") to preserve this information.
Migration Comparison Table
| Task Element | M365 to M365 | Google to M365 |
|---|---|---|
| Task Titles | ||
| Due Dates | ||
| Completion Status | ||
| Reminders | ||
| Repeat Settings | ||
| Attachments | ||
| Subtasks/Steps |