Skip to main content

Microsoft 365 migration & admin for Boise small business

Bad M365 migrations cost businesses for years: broken permissions, lost mail rules, MFA chaos, shared mailboxes nobody understands, and licenses you're overpaying for. Idaho Proper IT runs migrations the right way: pre-flight audit, staged cutover, MFA enrolled before go-live, conditional access policies in place, written admin handoff. Then I manage the tenant going forward, or hand it back clean if you have in-house IT.

Pre-flight audit Minimal-downtime email MFA & Conditional Access Written admin handoff Flat-fee pricing

Why most M365 migrations go wrong

Microsoft 365 looks simple on the outside. You pay per user and get email and Office. The reality is a large platform: Exchange Online, SharePoint, OneDrive, Teams, Entra ID, Defender, Purview, Intune, conditional access, mail flow rules, retention policies, sensitivity labels, and a license matrix that gets reorganized every couple of years. A migration that ignores any of those pieces leaves landmines that go off six months later when the original "IT person" is long gone.

Common problems in migrations done by someone else:

Broken permissions on SharePoint. Files migrated, but inheritance was never cleaned up. Either everyone has access to everything (compliance risk) or nobody has access to anything they need (productivity drain). Both happen routinely.

Lost mail rules and signatures. Server-side rules in old Exchange or Outlook-side rules don't always survive cutover. Critical mail goes to the wrong folder (or into the void), and nobody notices for weeks.

Shared mailbox confusion. "Sales@" and "Info@" get migrated as user mailboxes (with licenses that cost money), or as shared mailboxes that nobody can access because permissions were never set. Receipts, leads, and customer replies disappear.

MFA enforcement chaos. Migration completes, MFA gets toggled on, half the users get locked out on Monday morning. That's because nobody pre-enrolled them, told them what was happening, or set up break-glass accounts.

No conditional access. MFA without conditional access still lets attackers connect from anywhere. A proper migration ships with policies that block legacy auth, restrict admin sign-in to known locations, and require compliant devices for sensitive resources.

What a clean migration looks like

Pre-flight auditInventory every user, mailbox, shared mailbox, distribution list, mail rule, and license. Document what's in use before anything moves.
Identity mappingMatch source accounts to target accounts, set up Entra ID, configure SSO if applicable, and establish break-glass admin accounts before anything else.
Mailbox migrationPre-stage mailboxes, run delta syncs, and cut over MX records during a planned low-traffic window. Designed so mail isn't lost and there's no multi-day outage.
OneDrive & SharePoint migrationFiles migrated with permissions preserved (or rebuilt cleanly when source permissions are a mess). Document libraries restructured so they work instead of being copied as-is.
MFA enrollmentEvery user enrolled in MFA before cutover, with clear instructions. Authenticator app preferred, SMS as a fallback, written recovery process.
Conditional Access policiesBlock legacy authentication. Require MFA for all sign-ins. Restrict admin access to known locations and compliant devices. These are the policies that stop credential-theft attacks.
Written admin handoffA document that lists every account, every license, every policy, every mail rule, and how to make changes. That way your next IT person, or your in-house team, isn't reverse-engineering anything.

M365, done properly

A migration project, ongoing tenant admin, and license optimization that saves you money.

Full migration project

Pre-flight audit, identity setup, mailbox + OneDrive + SharePoint migration in stages, MFA + conditional access, written handoff. 1 to 3 weeks typical for under 25 users. Flat fee, quoted up front.

Ongoing tenant admin

User provisioning and offboarding, license assignments, mail flow rules, distribution lists, shared mailbox setup, retention policies, support tickets. Included in managed-IT plans.

License optimization

Most small businesses overpay for M365. I audit what licenses you have, what each user needs, and match the mix to that. Business Basic, Business Standard, Business Premium, F-series, add-ons. There's almost always money on the table.

Defender & Purview hardening

Defender for Office 365 anti-phishing, safe links, safe attachments. Purview DLP rules for PII and payment data. Sensitivity labels for confidential documents. The security features you're already paying for, turned on and tuned.

M365 migration & admin pricing

Flat-fee migration project. Ongoing admin included in managed-IT plans.

Migration project

"Get on M365 the right way."

Quoted

flat fee, up front

✓ Pre-flight audit
✓ Mailbox migration
✓ OneDrive & SharePoint migration
✓ MFA + conditional access
✓ Written admin handoff
✓ 30-day post-migration support
Recommended

Migration + ProperCare

"Migration plus ongoing admin."

$150

per user / month after migration

✓ Migration project (reduced rate)
✓ Ongoing tenant admin
✓ License optimization reviews
✓ Defender / Purview tuning
✓ M365 backup (separate vendor)
✓ Quarterly business review

Tenant takeover audit

"Inheriting a mess?"

Quoted

flat fee

✓ Tenant access transfer
✓ Full security & license audit
✓ Cleanup & documentation
✓ Findings report
✓ Optional ongoing admin

12-month managed agreement. 30-day satisfaction guarantee. 10% off if you prepay annually.

M365 migration FAQ

For a small business under 25 users, a typical migration runs 1 to 3 weeks from kickoff to handoff. That includes pre-flight audit, identity setup, mailbox and OneDrive cutover, SharePoint migration if applicable, MFA enrollment, conditional access policies, and a written admin handoff document. More complex environments (multiple domains, on-prem Exchange, or shared mailbox sprawl) take longer. I give you a realistic timeline up front.
No. The migration is staged so your team keeps sending and receiving the entire time. Mailboxes are pre-staged in M365, MX records flip during a planned low-traffic window (usually after-hours or weekend), and any mail that arrives mid-flip is delivered on the first sync after cutover. Worst case, a user might see a few minutes where new mail is delayed; the cutover is designed so mail isn't lost.
Yes. Step one is getting Global Admin access (or having the outgoing IT grant delegated access). Step two is a full audit: what licenses you have, what's in use, what security controls are or aren't enabled, who has admin rights they shouldn't, and what mail rules and conditional access policies are in place. Step three is cleaning it up and documenting it. After that you can stay on managed IT or take a clean handoff to in-house. Both work.

Get a migration plan that won't break email

Request a call back. I'll walk you through what a clean migration looks like for your environment, give you a realistic timeline, and quote a flat fee instead of billing hourly.

Request a call back Call (208) 918-0636

Flat-fee migration. 30-day post-migration support included.

Also from Idaho Proper IT