Day 1 with a New IT Provider: What to Expect

What to Expect on Day 1 with a Novatech Managed IT Contract

By the time Day 1 rolls around, the work of switching MSPs is mostly already done.

Onboarding takes a few weeks for a reason. We’ve documented your network, mapped your users, audited your licensing, taken stock of your hardware, and inventoried the systems we’ll be supporting.

We’ve already found the things that were going to be problems. The expired SSL cert, the server running an OS that went end-of-life two years ago, the firewall nobody has logged into since 2019. Most of that gets surfaced and triaged before we ever flip the switch.

So in technical terms, Day 1 is usually quiet. The phones don’t melt. The servers don’t fall over. We’ve already done the hard part.

Where Day 1 actually gets interesting is with people. Here’s what to expect, and how to set yourself up for a smooth first week.

The Biggest Challenge Isn’t Technical, It’s Behavioral

People are creatures of habit. You can send three emails. You can post a notice in Slack. You can put a printed sign on the breakroom fridge. And on Day 1, somebody is still going to email “Bob at the old IT company” because that’s what they did last Tuesday and the Tuesday before that.

This is the single most predictable thing about a Day 1 transition. We see it every time, no matter how clear the communication has been beforehand.

What this means in practice: your internal point person (usually the owner, the office manager, or whoever fields IT questions internally) is going to get a wave of calls and messages from frustrated users saying “I put in a ticket and nobody’s responded.” The ticket isn’t actually with us. It went to the old provider’s portal, or to a personal inbox, or to a system that no longer routes anywhere.

The fix is straightforward but it takes a couple of weeks of repetition:

• Have one clear way to submit tickets and say it five times more than feels necessary
• When someone reports a “missing” ticket, don’t troubleshoot it, just resubmit it through the right channel
• Resist the urge to bridge the gap by relaying tickets yourself, because that just trains people not to learn the new process

By week 3 or 4, behavior catches up. Until then, expect the chaos to be human, not technical.

The Credential and Access Surprise

Onboarding catches most of the systems we’ll need to support. It almost never catches all of them.

Day 1 has a way of surfacing the one thing nobody documented. The QuickBooks file on the bookkeeper’s desktop. The Adobe license registered to a former employee’s personal email. The vendor portal that only the office manager who left two years ago had the login for. The custom database that “just works” and nobody remembers who built it.

These show up the moment someone needs to use them and we have to ask, “what are the credentials for that?” And then everyone looks at each other.

This is normal. It’s not a sign onboarding was sloppy. It’s a sign your business has been running long enough to have collected the kind of small access debt every business collects. Day 1 is just when it gets paid down.

How to prepare: in the week leading up to the transition, ask your team this exact question by email: “Are there any systems, vendor portals, or software licenses you use that you’d be locked out of if you forgot your password tomorrow?” You’ll get answers nobody thought to mention during onboarding.

The “Is This Normal?” Calls

Here’s a strange one. Users will report things to us on Day 1 that have been broken for months. Sometimes years.

The slow scanner that everyone routes around. The shared drive that takes 30 seconds to load. The conference room TV that only works if you unplug and replug the HDMI cable. These have all been quiet annoyances under the old provider. The minute there’s a new IT team to call, suddenly they’re tickets.

This can feel, from the owner’s seat, like the new MSP is causing problems. They aren’t. They’re inheriting them. We just happen to be the first people in a long time who actually have an obligation to fix them.

The mental adjustment to make on Day 1: a sudden uptick in tickets is usually a good sign. It means the team trusts us enough to report things, and it means we’re going to clear out a backlog of half-broken stuff that nobody had bandwidth to tackle before. By month two, the ticket volume settles into a normal rhythm.

Inherited Work and Half-Finished Tickets

The old provider rarely hands off cleanly. Sometimes they do. Sometimes they’re professional about it and we get a clear list of in-flight issues. But often there are tickets in some state of partial resolution, projects that were paused mid-stream, or recurring issues that were being “monitored” without anyone actually fixing them.

We pick those up on Day 1, but it takes time to reconstruct context. If a user reports something that was already being worked on, we may need to ask questions that feel like we’re starting from scratch. We’re not. We’re rebuilding the picture so we can finish the work properly instead of guessing at where it was left off.

Day 1 Is Really More Like Week 1

The contract has a start date, but the real transition is a rolling few-week process. The technical handoff happens fast. The human handoff is slower. People are still routing tickets to old places, still discovering systems we hadn’t documented, still surfacing issues that have been quietly festering, and still adjusting to a new way of asking for help.

If you go in expecting that, the first week feels organized. If you go in expecting a flip-of-a-switch transformation, it feels chaotic.

The companies that have the smoothest transitions tend to do three things:

• Pick one internal point person and route all questions through them in the first two weeks
• Send the “how to submit a ticket” instructions more times than feels reasonable
• Treat the first 30 days as a settling-in period rather than a steady state

By the end of month one, you’ll be on the other side of it, and most of what you experienced on Day 1 will be a memory.

Want to Know What Your Day 1 Would Actually Look Like?

Every company’s transition is a little different. The size of your team, the state of your current IT setup, and how much technical debt has accumulated all change the picture.

If you’re considering switching providers and want a real read on what onboarding would look like for your business, start with a free assessment. We’ll walk through your current environment, identify what would need to be addressed during onboarding, and give you a realistic picture of what Day 1 would actually feel like before you commit to anything.

The fewer surprises, the smoother the transition.