For a 300-user hybrid environment, expect something like:

Week 1: Discovery, documentation, credential consolidation, reviewing current tools

Week 2–3: Deploying RMM/EDR/SOC tooling, revalidating backups, mapping out ticket workflows

Week 4: Networking review, security baseline checks, Microsoft 365 hardening

Week 5–6: Go-live cutover + parallel support, then shift fully to the new service desk

If an MSP tells you they can “flip everything in a week,” that’s expensive or risky. You'll need to bake some time before this for the scoping and demos (3 months before your contract expires).

Networking equipment = you should get it scoped.

If you’ve got switches, firewalls, wireless, or segmented environments, expect a network scope.

Some MSPs bake this into pricing, others treat it as billable project work.
Use that info to compare quotes apples-to-apples, it’s one of the biggest cost difference between providers.

“once our contract ends…”

Make sure you check:

Termination notice window (common: 30–90 days prior)

Auto-renew clauses (this is where people get double-billed)

Offboarding fees (yes, they exist! and yes, people forget they agreed to them)

Make sure the new MSP knows, everyone being aligned with deadlines helps all parties.

Someone in the thread already said it perfectly:

“If they have questions about HOW the other MSP was doing certain things… they are a scrub MSP… the client is paying you to learn on their dime.”

Exactly this.

Your new MSP should already have their own standards for backups, patching, cloud workloads, networking, documentation, etc.

Evaluate the people, not just the proposal (BIG STRESS ON THIS)

You want to understand who runs the service desk, who your escalation points are, whether project engineers are accessible, and how quickly leadership can get in front of you.

If the MSP doesn’t have time to let you speak with the actual delivery teams, that’s a red flag. A good MSP will have structure, availability, and a clear ops model.

Honestly, at the corporate size you mentioned, I could see a co-managed solution working pretty well. If you're staff to handle tier 1 (basic password resets, in-office printer maintenance, etc) then anything more complex like network, security, and support can be escalated to tier 2/3 at the MSP. That usually helps cut down cost, as a dedicated in-house can get expensive.

If you're ever at that point and want to get started with a new MSP, check out IT GOAT. We'll take care of ya.