TARGETED PROJECT
M365 Migration & Right-Size Audit.
A fixed-price migration with the licensing and TechSoup eligibility worked out before the cutover, not after.
-
3–6 weeks
typical engagement duration, by user count
-
8–20 hours
total time required from your team
-
$5,500–$12,000
fixed, by user count and complexity
Why this matters.
Two patterns drive most of the SMB and nonprofit M365 work in the field, and both lose money quietly. The first: an organization on Google Workspace paying full retail per seat when they qualify for nonprofit Google or could move to M365 at TechSoup pricing for less than half the cost. The second: an organization already on M365 Business Standard who could be on Business Premium for two dollars more per user per month — and who's already paying separately for the SaaS antivirus, the standalone MFA tool, and the third-party MDM that Premium includes. The right-size audit names what you should be on; the migration plan delivers it without surprising your inbox or your finance team.
What we do.
Platform assessment up front — current state across users, mailboxes, calendars, contacts, shared drives, and any SaaS the productivity stack actually depends on. Nonprofit pricing eligibility check (TechSoup, M365 nonprofit grants, Google nonprofit comparison if the source is Workspace). License right-size analysis: what SKU you're on, what SKU fits, and what you save or spend in the move. A written migration plan with risks, mitigations, and a defined cutover window. Mailbox, calendar, and contact migration. Shared-drive content migration with retention and access rights preserved. Basic Outlook, Teams, and OneDrive end-user training in the cutover week. Post-migration health check — every user verified, every legacy account decommissioned, every license rebalanced.
What you walk away with.
A working M365 environment sized to your actual usage, not your sales rep's quota. A documented migration plan you can reference in any future audit or compliance conversation. Right-size recommendations carried into license posture (so you're not paying for E3 seats when E1 fits, or paying retail when nonprofit pricing applies). Trained end users who know where their email lives now and how to find a file. The migration plan is yours; if your existing team or MSP wants to execute it instead of us, that's a discovery-call conversation — we can scope assessment-only at a different price point.
What's in scope.
Platform assessment (current state across users, mailboxes, calendars, contacts, shared drives, and productivity-stack SaaS dependencies). Nonprofit pricing eligibility check (TechSoup, M365 nonprofit grants, Google nonprofit comparison where relevant). Written migration plan with risks, mitigations, and cutover window. Mailbox migration (full content, calendar, contacts). Shared-drive / OneDrive content migration with access rights preserved. Tenant configuration baseline (email signatures, branded login, basic security defaults). End-user communications (cutover notice, post-migration where-to-find guide). Basic Outlook / Teams / OneDrive training in the cutover week. Post-migration health check (per-user verification, legacy account decommissioning, license rebalancing). 30 days of post-cutover support for migration-related issues.
What's out of scope.
Custom Power Automate flows, Power Apps, or SharePoint information-architecture redesign (separate Process Automation Sprint or scoped project). In-depth Intune device enrollment or modern device management rollout (separate Identity Modernization or follow-on engagement). Historical email archiving beyond the active mailbox content (separate scope; usually requires a third-party archive product). Teams Phone setup, Teams Rooms, or contact center work (separate scope). Migration of more than two source platforms in a single engagement (we run one source → M365 cleanly; multi-source consolidations get scoped on discovery). Application migrations or line-of-business system rehosts that touch M365 only tangentially.
This is the right engagement when…
- You're on Google Workspace and your subscription cost has crept past the value you're getting — nonprofit pricing is leaving money on the table, or your team is already living in Outlook on the side because that's what the rest of the world uses.
- You're on M365 Business Standard and a vendor recently quoted you Premium without explaining what changes — the right-size audit names whether the upgrade pays for itself, and whether you're already paying separately for security tooling Premium would absorb.
- You're a nonprofit and "TechSoup" / "Microsoft nonprofit grants" sounds vaguely familiar but you don't know what you actually qualify for or how to claim it.
- A board, an auditor, an insurer, or a major donor is asking about IT modernization, and the M365 migration is the move that buys you the documented progress they want to see in this fiscal year.
- You went through an M&A event in the past twelve months and you're now running two productivity stacks with two licensing bills and one increasingly tired finance team.
What you receive across the engagement.
- Written platform assessment Signed off at engagement start; defines current state across users, mailboxes, calendars, shared content, and SaaS dependencies. Becomes the input to the migration plan.
- Nonprofit pricing eligibility memo Separate one-pager when applicable. Names what you qualify for (TechSoup, M365 nonprofit grants, Google nonprofit), what the savings look like at your seat count, and what's required to claim it.
- License right-size recommendation What SKU mix you should be on, what you save or spend in the move, and what tooling you stop paying for separately because the new SKU absorbs it.
- Migration plan Risks, mitigations, cutover window, communications timeline, rollback plan if needed. Reviewable by your leadership team or MSP before cutover.
- Executed migration Mailbox, calendar, contacts, shared drives. Per-user verification at cutover. Legacy account decommissioning and license rebalancing inside 30 days post-cutover.
- End-user training materials Short Outlook / Teams / OneDrive how-to documents in your branding. Yours to keep and reuse for new hires.
Here's the shape of finding the engagement is built to surface — the kind of issue a right-size audit catches before the migration locks in the wrong licensing decision.
Pricing model — fixed by user count.
The default engagement is fixed-price by user count, banded as follows: 10–25 users at $5,500–$7,500 (single source platform, single cutover window, basic training); 25–75 users at $7,500–$10,500 (phased cutover by department or team if the operational shape calls for it); 75–150 users at $10,500–$12,000+ (multi-phase cutover, additional stakeholder coordination, optional pre-cutover dry-run).
Engagements above 150 users are scoped separately on discovery — the ratio of complexity to user count is non-linear past that mark, and the productized band stops being honest. We'll quote a fixed price after a 30-minute discovery call rather than estimate from the storefront.
We don't sell the migration on a time-and-materials basis. T&M is the industry default for migrations because it lets the firm absorb cost overruns by extending the engagement; the customer absorbs the same overruns directly. Fixed-price productized work flips the incentive — the migration plan exists to surface scope risk before the engagement starts, so the price holds.
How we're different.
- Fixed-price productized. Most M365 migration work is sold T&M, which transfers schedule risk to you. The migration plan that ships as part of the assessment is also the scope contract — surprises mean a change order, not a runaway invoice.
- Nonprofit pricing actually surfaced. TechSoup eligibility, M365 nonprofit grants, and the Google nonprofit comparison get worked through with real numbers, not handed off as "you should look into that." If you qualify, we name what for and what it saves.
- Right-size, not forklift. A migration that moves you to the wrong SKU is a more expensive version of the same problem. The license right-size analysis sits inside the migration scope, not on top of it.
- Vendor-neutral on the outcome. No Microsoft reseller relationship, no financial stake in which platform you land on. The recommendation reflects what fits — including the Google Workspace comparison where it's relevant.