Why user count is only the starting point
The number of users affects licences, account preparation, mailbox mapping and user-side changes, but two businesses with the same headcount can have very different projects. Ten simple IMAP mailboxes are not equivalent to ten large Google Workspace users with calendars, shared drives and multiple sending systems.
A useful quote starts with user count and then examines the source platforms, data volumes, domain control, licences, shared mailboxes, devices and target services.
Mailbox size, archive data and source platform
Large mailboxes take longer to transfer and verify. Online archives, disabled users, shared mailboxes and historic domains can add work even when the active user count is small.
The source platform determines which migration methods are available. Gmail, Exchange, IMAP and tenant-to-tenant moves expose different data and authentication options. A lower-cost method may move email only, while calendars, contacts or permissions require additional tooling or preparation.
- Number and type of mailboxes
- Mailbox and archive sizes
- Source-system access and export capabilities
- Calendar and contact requirements
- Shared mailbox, alias and distribution-list requirements
OneDrive, SharePoint and file complexity
Adding business files changes the scope substantially. File count, total volume, folder depth, ownership, permissions and incompatible names all affect preparation and validation.
Google-native documents may need conversion. Local file shares may contain application data or folders with complex permissions that should not be copied blindly into SharePoint. These questions are why file work is assessed separately within the overall migration.
DNS, devices and timing
Domain verification and MX, SPF, DKIM and DMARC changes require reliable DNS access and an understanding of every legitimate sending service. Outlook profiles, phones, scanners and business applications may also need work after the mail cutover.
Out-of-hours delivery can reduce user disruption but affects staffing and scheduling. A rushed deadline can also increase risk or require additional migration tooling. The quote should state who handles each user and device task.
- Domain and DNS access
- Outlook and mobile-device changes
- Scanners, websites and applications that send email
- Out-of-hours or phased cutover
- User communications and post-migration support window
How to get a useful fixed-scope quote
Prepare an approximate user list, mailbox sizes, current provider, domain details, file volumes and target date. Note any shared addresses, archives, leavers and applications that send email.
Next Layer IT uses that information to define a project scope rather than publishing a headline price that only applies to the simplest case. Read more about our Microsoft 365 migration service or request a quote based on your current setup.