Your First 90 Days With a New IT Provider

Signing with a new IT provider feels like the finish line. It is actually the starting gun. The first 90 days decide whether you bought a genuine upgrade or just a new logo on the same old problems, and the difference is rarely luck. Good onboardings follow a sequence. Bad ones improvise.

This is the sequence we run, written out so you can hold any provider to it, including us. If you have not signed yet, read the 10 questions to ask before signing a new IT contract first; a clean start depends on terms you negotiated before day one. Once the ink is dry, here is what the first three months should look like, step by step.

Days 1 to 30: take inventory, take custody, change nothing rashly

The first month is about knowledge transfer and control, not improvement projects. A provider who starts ripping out systems in week two is guessing.

1. Kickoff with named humans. You should leave the first meeting knowing your account manager, your lead engineer, how to open a ticket, and what response times you were promised. If the people in the room all disappear after the sale, that is your first red flag.
2. Credential recovery and custody. Every administrative password gets collected from the old provider, rotated, and stored in a password vault your company owns. This is the single most important step of the entire switch; everything else can be redone later, but lost credentials are lost leverage.
3. Full environment documentation. Devices, servers, network gear, software licenses, domain and DNS records, cloud tenants, vendor contacts. Ask to see the documentation, not just hear that it exists.
4. Backup verification. Not "backups are configured" but "we restored a file and a server image, and here is the proof." Many businesses discover their backups were fiction only during a crisis. Make the new provider prove it in month one.
5. Security baseline. Multi-factor authentication enforced on email and admin accounts, endpoint protection deployed and reporting, patching current. These are hygiene, not projects, and 30 days is enough time for all of them.
6. Old provider formally closed out. Access revoked, final invoices reconciled, data return confirmed in writing. If leaving felt impossible, our piece on the signs you should fire your IT provider explains why that feeling was the strongest argument for going.

Days 31 to 60: fix the known pains, measure everything

Month two is where the switch starts paying rent. The discovery work is done, so the recurring problems you switched to escape should now get root-cause fixes rather than patches.

7. Top-issues list, worked in order. The five problems that made you switch, each with an owner and a date. The VPN that drops every Friday should die in month two, permanently.
8. First real reporting. Ticket volume, response times against the SLA, patch status, backup success rate. If the provider promised metrics in the sales process, this is when they appear, unprompted.
9. Lifecycle and license audit. What hardware is past warranty, what renews in the next 12 months and at what price, what you are paying for and not using. Most businesses find at least one zombie subscription here.
10. A 12-month roadmap draft. Not a sales document, a plan: replacements, upgrades, and projects with rough budgets, so nothing in the next year arrives as a surprise invoice.

Days 61 to 90: pressure-test the relationship

By month three the honeymoon polish has worn off, which makes it the honest measurement window.

11. Test the SLA when nothing is wrong. Open a low-priority ticket and a high-priority one a few weeks apart. Compare actual response to promised response. You want the data now, not during an outage.
12. Run a restore drill. Ask for a specific file from a specific date, then time it. A provider who bristles at being tested is telling you something.
13. The 90-day review meeting. Ticket trends, SLA performance, roadmap progress, and the question that matters: what has measurably improved since day one? Bring your own list too; a good provider wants your scorecard.
14. Decide, on evidence. Month-to-month agreements make this real: renew because the numbers earned it. If you are on a term contract and the evidence is bad, read MSP contract exit clauses, explained sooner rather than later, because notice windows wait for no one.

Red flags in the first 90 days

A few patterns predict long-term trouble with unpleasant reliability: documentation that never quite materializes, "we will get to that" on backup testing, tickets answered by a rotating cast of strangers, and invoices that already contain surprises in month two. None of these improve with time. The best providers are at their most attentive in the first quarter; if the first quarter is sloppy, year two will not be better.

The part before day one

Everything above assumes the transition itself went cleanly, and that is the part that scares most owners out of switching at all. It is also the part that is genuinely solvable: we onboard silently in parallel with your current provider, document everything before anything changes hands, cut over with zero downtime, and make the breakup call ourselves, credentials recovered and rotated before the old provider finishes being annoyed. Choosing the right provider to do that with is its own skill; our guide to comparing IT providers apples to apples gives you the scoring framework.