Workstream 01
Break the project into priced workstreams
Treat discovery, mailbox migration, collaboration data, identity/licensing, cutover and aftercare as distinct rows. The supplier should document assumptions such as maximum source data per user, number of devices and whether shared mailboxes or guest permissions are counted separately.
Some costs depend on volume; others depend on complexity. A ten-person organisation with several Shared Drives and strict retention rules might require more engineering than a fifty-person mail-only transfer.
| Workstream | Variables to disclose | Frequently omitted |
|---|---|---|
| Discovery and readiness | Tenant count, administrator access, licence mapping | Unsupported item assessment |
| Mail, contacts and calendars | Mailbox sizes, archive, delegates and number of waves | Shared calendars and room booking recreation |
| Drive, OneDrive and SharePoint | Storage, file types, team sites and permissions | Conversion exceptions and broken links |
| Identity and DNS | Domain control, MFA, mail routing and integrations | Third-party senders and coexistence |
| Device setup and training | Operating systems, locations, number of devices | Remote assistance for each staff member |
| Aftercare and warranty boundaries | Hours, duration, severity and escalation route | Weekend cover and separately billable issues |
Workstream 02
Illustrative example: why the user count misleads
Consider two hypothetical 20-user clients. Company A has twenty ordinary mailboxes and no shared files; Company B has the same number of mailboxes plus six team Drives, externally shared finance folders, assistant-managed calendars and a strict cutover date. These are not real client results or quotations.
Company B needs additional discovery, permission mapping, document-conversion testing and user acceptance. It would be misleading to offer both companies the same price solely because they each have twenty accounts.
Workstream 03
Ask about cost of risk—not only migration tooling
A quote should identify the person making a rollback decision, how a failed batch is handled, the limits of any fallback and which test results close the project. If the proposal doesn't include the time required to check real user workflows, the fee may defer the work into a dispute.
Separate ongoing Microsoft 365 administration from migration aftercare. Retained support can be a valuable follow-on service, but it should never be an unexpected mandatory charge in a standalone migration quote.
What to capture before the decision
- Source and target platforms and workload ownership
- Seat, size, archive and device assumptions
- Tool/licence costs and tax treatment
- Data validation and permissions acceptance
- Rush/weekend fees, support window and exclusions
- Final quote approval before tenant access or purchase
Workstream 04
Build a scope-based bill of work, not a per-mailbox guess
A fair comparison begins with quantities the buyer can verify: user and shared mailbox counts, total source gigabytes, source platforms, SharePoint sites, team-owned drives, device support, users needing assistance and the desired cutover window. Ask each vendor to state its assumptions about throughput, licensing, remediation and what happens when those assumptions prove wrong. Licence fees, migration tool fees and third-party contractor work should be distinguishable from professional-services labour.
Price the exceptions and acceptance work explicitly. Data discovery, preservation policy review, calendar corrections, identity remapping, link remediation, end-user support and aftercare are the parts most likely to be omitted from a simple price-per-user quote. Only a measured inventory and a delivery-cost model justify a fixed commercial commitment.
| Cost driver | Question to establish before quoting | Possible commercial treatment |
|---|---|---|
| Mailbox/data volume | How many objects and GB, including archives? | Base work plus agreed data-band assumption |
| File permissions | How many governed sites and guest relationships? | Discovery and verified access workstream |
| Cutover constraints | Weekend, multi-wave, regulated freeze? | Explicit window and contingency pricing |
| Aftercare | Which users, hours, devices and severity? | Time-bound scoped support line |
Workstream 05
How to compare two quotes without being misled
Build a side-by-side acceptance sheet with included workloads, exclusions, pilot criteria, change control, named client approvals, licence ownership, retention and termination obligations. Where a quote excludes historical data or shared resources, that is not necessarily wrong: it is a business decision to be priced and agreed. Where it is silent, request clarification in writing.
Treat any numeric output from this site's estimator as an illustrative planning scenario, not a quote, guaranteed throughput or tested implementation commitment. Actual rates and service coverage can be offered only after technical capacity and fully loaded economics have been verified.
What to capture before the decision
- Separate client-purchased licences from labour and tool costs
- Require a costed workstream for permissions and file conversion
- Insist on a written change-order rule for unexpected data
- Identify objective handover/acceptance evidence
- Do not infer zero downtime or fixed completion from a calculator
The right quote lets a customer compare exactly what will happen, what might fail and what they can reasonably expect at handover.
Source documents and limitations
These references establish current vendor behaviour; they do not verify an individual customer's configuration or imply Microsoft affiliation. Technical claims should be rechecked before execution.