Scope
Define which mailboxes, aliases, shared folders, calendars, and archives are in scope; include size thresholds, exclusions, and data classification levels to ensure consistent handling.
Maintaining a clear, signed Email Migration Document reduces the risk of data loss, documents consent and authority, and records retention and legal-hold decisions required for regulated records during migration.
Typical users include IT operations, security and compliance teams, project managers, and external migration vendors coordinating account transfers.
The document ensures these parties share a common timeline, acceptance criteria, and responsibility assignments before migration begins.
Define which mailboxes, aliases, shared folders, calendars, and archives are in scope; include size thresholds, exclusions, and data classification levels to ensure consistent handling.
Provide detailed timelines, maintenance windows, per-group migration windows, expected downtime, and rollback windows so stakeholders can plan communications and service continuity.
Specify account mappings, username transformations, domain changes, and shared mailbox assignments; include CSV examples and validation steps for automated imports.
Document required credentials, service accounts, OAuth or API scopes, multi-factor impacts, and steps for securely rotating secrets after migration.
Record retention policies to apply during migration, including hold exemptions, folder-level retention, and how legal holds will be preserved or transferred.
List post-migration checks: message counts, folder structure integrity, searchability, delegated access, and an acceptance checklist for each mailbox owner.
| Field | Configuration |
|---|---|
| Authentication | OAuth2 with service account and MFA where required |
| Migration Tool | Choose incremental or full transfer; enable throttling |
| Validation Checks | Message counts, attachments, and folder structure verification |
| Notifications | Email status reports, failure alerts, and final sign-off summary |
Platforms and delivery channels supported for distributing the Email Migration Document, collecting approvals, and preserving an auditable signature record across systems.
Require sign-off at least 10 business days before start
Provide notice 7–14 days before migration
Scheduled maintenance window begins at agreed time
Complete verification within 5 business days
Record retention period begins on migration completion
Define scope, approvals, timelines, and tools before scheduling work
Provision accounts, validate credentials, and test small pilot batches
Perform bulk migration during agreed windows with monitoring enabled
Run verification, reconcile counts, obtain sign-off, and archive records
| signNow | DocuSign | Adobe Sign | PandaDoc | HelloSign | |
|---|---|---|---|---|---|
| Starting Price | $8/user/mo | $15/user/mo | $14/user/mo | $19/user/mo | $15/user/mo |
| Free Trial | 7-day trial, no card | Varies by vendor | Varies by vendor | Varies by vendor | Varies by vendor |
| Bulk Send | Yes | Yes | Yes | Yes | No |
| Audit Trail | Yes | Yes | Yes | Yes | Yes |
| HIPAA Compliant | Yes | Yes | Yes | No | No |
| Envelope Cap | No cap | 100 envelopes/user/year | Varies by plan | Varies by plan | Varies by plan |