Managed IT transition: a case study covering the 17-day provider handover, remote-workforce device onboarding, security cleanup, and quarterly governance ETTE delivered for a Washington, DC advocacy firm.
Switching IT providers without missing a day of advocacy work
The client is a Washington, DC-based public affairs and advocacy firm whose staff work 90–95% remotely. After selecting ETTE through a competitive RFP in December 2025, the firm needed to leave its outgoing IT provider without a gap in coverage, get every laptop and Mac under management, and clean up years of accumulated sharing and security debt — all while its consultants stayed heads-down on client campaigns. ETTE ran the kickoff on January 5, 2026 and took over support in full seventeen days later. This page documents how the transition worked. The client's name is withheld; every date and count comes from the project record.
From outgoing provider to steady state
ETTE ran the transition as a sequence: take over cleanly, meet every user and device, fix what the handover exposed, then settle into a governance rhythm.
-
Kick off & planTransition schedule, staff communication templates, and support channels set in one meeting
-
Coordinated handoverCredentials, admin roles, and management tooling transferred jointly with the outgoing provider
-
Onboard every deviceScheduled one-on-one sessions for a remote workforce, PCs and Macs, with written SOPs
-
Harden & clean upPublic sharing links cut, tenant defaults tightened, firewall and email filtering replaced
-
Move to a rhythmWeekly checkpoints during transition, then quarterly business reviews with the firm's leadership
A handover run jointly, then onboarding built around the client's calendar
Provider switches usually fail at one of two points: the handover, where credentials and admin access fall through the cracks, or the months after, when the new provider discovers what the old one left behind. ETTE addressed the first with a joint transition call that put both providers at the same table — working through admin accounts, the endpoint management tenant, communication platform roles, network controller configuration, and security tool access item by item — and set the outgoing contract to end the same week ETTE's management tooling went live, so the firm never paid for overlapping coverage or sat uncovered. The second it addressed with patience: device onboarding for a 90–95% remote workforce ran as scheduled one-on-one sessions over roughly eight weeks, batched on Fridays at the client's request so consultants lost as little billable time as possible.
Onboarding as a feedback loop
The firm's operations lead collected written feedback from the first wave of staff sessions and ETTE adjusted the next waves around it — including investigating a permission-prompt setting for remote access software after early adopters said they wanted more visibility into when a technician could see their screen. Mac onboarding time dropped noticeably once the first sessions were turned into a written standard operating procedure.
Security debt handled in the open
The handover exposed years of accumulated exposure: thousands of publicly accessible sharing links, tenant defaults that let documents leave the organization silently, an email filter mid-decommission, and aging network hardware. Each item went onto the weekly checkpoint agenda with the client's operations lead, was prioritized together, and was reported on until closed — not fixed silently in the background.
Transition timeline
What the transition actually involved
Every item below comes from the project record: the kickoff and weekly checkpoint meetings, the joint handover call with the outgoing provider, the ticket history, and the first quarterly business review. Dates and counts are taken directly from those sources.
Rather than chase the outgoing provider by email for months, ETTE convened a joint call eleven days after kickoff and worked the transfer item by item: tenant admin accounts, the endpoint management platform, communication tool admin roles, the network controller configuration, domain registrar access, and security training accounts. Gaps — like an undocumented network controller whose config lived on one laptop — were found on the call, not six months later. Credentials went into ETTE's documentation system, and the outgoing contract ended the same week ETTE's tooling went live.
With staff 90–95% remote, there was no office day when everyone could be onboarded at once. ETTE technicians ran scheduled one-on-one sessions — PCs and Macs both — batched on Fridays at the client's request, with the firm's operations lead nudging stragglers over the firm's own channels. Early Mac sessions were distilled into written SOPs that cut per-device time for the rest of the fleet, and staff feedback from the first wave reshaped how later sessions were communicated and run.
The tenant audit found thousands of publicly accessible sharing links accumulated over years, with defaults that let documents leave the organization silently. ETTE ran a phased reset that cut public links from over 2,000 to 688, changed the tenant's default sharing scope to people inside the firm, and moved critical shared files toward role-based SharePoint access — sequenced carefully because the firm's external contractors still needed legitimate access to keep working.
New-hire setup requests had arrived as free-form emails, each missing something different. ETTE built the firm custom web forms for onboarding and offboarding that capture everything in one submission — including the firm's specific license choices and standard channel assignments — and create a tracked ticket automatically. The client's operations lead test-drove the forms, requested changes, and had them live before the firm's next new hire started.
Thank you for checking in and providing the update. I appreciate the transparency and guidance.
— Senior Director of Operations, client firm · June 2026Where the client stands now
By the first quarterly review, 81 of 86 support tickets were resolved with 100% satisfaction on post-ticket feedback, and the firm's leadership receives ticket metrics it can present to its own senior leadership team on request.
The firm's security posture score climbed from the mid-40s at handover to the mid-60s by the March leadership briefing, with a stated target of 75–80% — deliberately balanced against the flexibility a fast-moving advocacy practice needs.
The full fleet — PCs, Macs, and mobile devices — is enrolled in endpoint management with 24/7 monitoring, upgraded security tooling at no added cost over the prior arrangement, and a hardware lifecycle report that flags aging equipment before it fails.
Public sharing links are down from over 2,000 to 688 and shrinking, tenant defaults keep new shares internal, and shared files are moving to role-based SharePoint structures instead of person-to-person links.
Weekly transition checkpoints have given way to quarterly business reviews with the firm's leadership, self-service onboarding and offboarding forms handle staff changes, and recommendations from each review become tracked tickets rather than good intentions.
The team on the transition
Descriptions and quoted remarks come from the project's meeting record and ticket history.
Ran the kickoff and the joint handover with the outgoing provider, led the tenant audit and sharing cleanup, replaced the office firewall, and presented the security posture and roadmap at the all-staff leadership briefing and the quarterly review. Documented credentials and configuration in ETTE's systems as they transferred, so nothing lived in one person's inbox.
Coordinated the weekly checkpoint agenda, scheduled and ran the one-on-one device sessions across the remote workforce, turned the early Mac sessions into written SOPs, and handled the follow-through on quarterly review recommendations — each one logged as a tracked ticket with an owner.
Owned the transition from the firm's side: authorized the handover with the outgoing provider, gathered staff feedback after each onboarding wave, chased down the last unonboarded devices over the firm's own channels, and test-drove the new onboarding forms before they went live. The weekly checkpoint — and later the quarterly review — ran through this desk.
If you're stuck with an IT provider that isn't working
Provider transitions for organizations like this one
Most organizations stay with an underperforming IT provider because the switch feels riskier than the status quo — lost credentials, uncovered weeks, staff disruption. This transition shows the alternative: a joint handover that transfers everything on the record, a cutover date both providers work toward, and onboarding paced around your calendar rather than the provider's. ETTE runs this as a practiced process through its Managed IT and Remote-Only Managed IT plans, with Microsoft 365 management and quarterly business reviews built in.
The pattern that worked here — weekly checkpoints during the transition, honest reporting on what the handover uncovered, and a security posture raised in negotiated steps rather than imposed all at once — is how a fully remote organization changes providers without losing a day of work.