You are reading Part 4 of our 12-part Non-Profit Authority Series.
A non-profit switching IT providers should evaluate more than price and Help Desk response. A successful transition should address administrative access, documentation, security controls, monitoring, Microsoft 365, backups, vendor relationships, and unresolved technology risks. WTITC can typically complete its core onboarding process in approximately one business day, depending on the size and complexity of the environment. For a 15-30 employee organization, the goal should be a controlled transition that establishes ownership quickly without unnecessarily disrupting employees.
The 6-Step IT Provider Transition Framework
A non-profit can evaluate a provider change using six steps:
- Identify why the current relationship is failing.
- Confirm ownership and administrative access.
- Inventory the technology environment.
- Establish security and monitoring.
- Define service scope and accepted risk.
- Build the first technology improvement plan.
The provider change should solve structural problems, not simply replace the company answering the phone.
1. Define Why You Are Changing Providers
Before evaluating another IT company, leadership should identify the problems it actually wants to solve.
Common reasons may include:
- Recurring technical problems
- Poor communication
- Unclear accountability
- Weak documentation
- Inadequate cybersecurity
- Unexpected invoices
- Lack of technology planning
- Aging equipment
- Poor Microsoft 365 management
- Uncertainty about backups
- No clear escalation process
This list becomes part of the provider-selection criteria.
For example, if recurring downtime is the problem, changing to another provider that primarily waits for employees to report failures may not produce a different outcome.
WTITC’s model is built around proactive managed services rather than traditional break-fix support. That distinction should be understood before a non-profit signs an agreement.
2. Confirm Administrative Access and Technology Ownership
One of the most important transition questions is simple:
Does the organization actually control its technology accounts and administrative access?
Leadership should know who controls or has access to:
- Microsoft 365
- Domain registration
- DNS
- Firewalls
- Network equipment
- Servers
- Backup systems
- Security products
- Cloud applications
- Administrative credentials
- Vendor accounts
The outgoing IT provider may legitimately have administrative access, but the organization should not discover during a transition that critical systems are inaccessible or that ownership is unclear.
Documentation matters here.
A strong transition should identify what documentation exists, what is missing, and what needs to be rebuilt.
For regulated or risk-sensitive organizations, access records and documentation can also support audit readiness and help demonstrate active management of important systems.
3. Establish Monitoring and Security Early
A provider transition should not create an extended period in which systems are unmanaged.
WTITC’s onboarding process includes coordinating technicians and Help Desk resources, obtaining required administrative access, and deploying Datto RMM and applicable security tooling.
Core onboarding can typically occur in approximately one business day, although the actual timeframe depends on environment size and complexity.
That does not mean every historical technology problem will be corrected in one day. It means the organization can begin moving into the managed environment while deeper issues are documented and prioritized.
The security discussion should also distinguish between endpoint and user protection.
WTITC’s Essentials Security Package includes antivirus, Endpoint Detection and Response, unified device backup, and Datto SaaS Protection where applicable.
The Complete Security Package adds Inky email security, BullPhish ID security awareness training, Dark Web ID monitoring, SaaS Alerts, and Microsoft 365 management and maintenance.
A realistic managed IT budget gives a non-profit the security, monitoring, documentation, and support foundation needed to avoid repeating the same weaknesses with a new provider.
Changing providers without correcting security and management gaps can simply transfer the same risks to a different IT company.
4. Understand What Is Included Before Signing
A non-profit should never assume that “managed IT” means every technology-related activity is included in the monthly fee.
WTITC’s managed services structure contains three layers:
- Security Package
- Managed Services Fee
- Tiered Technology Fee
The Managed Services Fee is $40 per managed endpoint per month and includes Datto RMM monitoring and patching, proactive alerting and remediation, IT Glue documentation, secure password management, unlimited Help Desk support, and coordinated remote and onsite support when warranted.
Some onsite hours may be included depending on agreement size, but onsite work is not unlimited. Major projects and additional onsite needs may require separate professional services.
WTITC uses $150 per hour as its professional services benchmark for project work and exceptional or out-of-scope activities.
A la carte services can include:
- Business Continuity and Disaster Recovery
- Third-party penetration testing through Vonahi
- Compliance Manager
Understanding which technology work falls outside the managed services agreement prevents a provider change from creating a new set of billing and responsibility surprises.
Leadership should ask prospective providers to explain both what they do and what they do not do.
That transparency is a trust signal.
5. Evaluate the Provider’s Long-Term Management Model
Onboarding is only the beginning.
A non-profit should ask what happens in month 2, month 12, and year 3.
WTITC’s Tiered Technology Fee supports functions including:
- 24/7 monitoring infrastructure
- Security operations
- Alert triage
- Monthly service audits
- Technology Alignment Manager oversight
- Tooling and automation
- Internal escalation
- Service management
- Dispatch
- Quality control
Technology alignment is particularly important after a transition because the first months often reveal problems that have accumulated over time.
The objective should not be to create a long list of projects immediately. It should be to identify and prioritize the issues that affect reliability, security, employee productivity, and business risk.
For a non-profit, that may mean addressing one critical network problem first while planning workstation replacements over several budget cycles.
6. Compare Providers by Outcomes, Not Just Monthly Price
A properly secured managed environment can reasonably be planned around approximately $125-$175 per endpoint per month, but that is a planning range rather than a universal quote.
Actual pricing can vary according to:
- Security package
- Endpoint count
- User count
- User-security requirements
- Environment size
- Tiered Technology Fee
- Optional services
- Projects
- Multiple locations
- Cloud systems
- Compliance requirements
A lower proposal may legitimately represent a different service model.
That is why decision-makers should compare scope and outcomes, not simply totals.
A strong Permian Basin IT provider should be able to explain its proactive management model, cybersecurity approach, pricing structure, communication process, and technology-alignment strategy before asking a non-profit to make a long-term commitment.
Hypothetical Example: Changing Providers at a 24-Employee Non-Profit
Consider a hypothetical non-profit in Odessa with 24 employees and 28 managed endpoints.
Leadership wants to change providers because employees experience recurring connectivity problems, Microsoft 365 administration is inconsistent, and no one is certain when backups were last validated.
A structured transition would begin by:
- Obtaining administrative access.
- Documenting systems and vendors.
- Deploying monitoring and appropriate security tooling.
- Identifying critical risks.
- Confirming backup and recovery responsibilities.
- Prioritizing unresolved problems.
- Establishing an improvement roadmap.
The expected result is not that years of accumulated technology problems disappear overnight.
The expected result is clear ownership, visibility into the environment, documented priorities, and a structured path toward improvement.
IT Provider Switching Checklist
Before authorizing a transition, ask:
- Why are we leaving the current provider?
- What must be different with the new provider?
- Do we control our administrative accounts?
- Is our documentation complete?
- How quickly will monitoring be established?
- How will endpoint and user security be addressed?
- Who manages Microsoft 365?
- Who owns backup and recovery responsibilities?
- What is included in the monthly agreement?
- What is considered a project?
- How is onsite work handled?
- How are compliance-related controls documented?
- What happens after onboarding?
- Who is responsible for long-term technology planning?
A provider that can answer those questions clearly gives leadership a much better basis for comparison.
What Should a Non-Profit Expect From the Transition?
A good transition should create more clarity, not more uncertainty.
The organization should know who is responsible, how support works, what security controls are present, which risks remain, and what needs to improve next.
For non-profits in Midland, Odessa, and surrounding West Texas communities, that creates a foundation for a technology relationship focused on long-term operational health rather than simply changing the name of the company receiving support calls.
Explore a managed services model built around proactive support, security, clear accountability, and long-term technology alignment.
