Switch IT providers without the downtime or the bill.
We assess what you have, build the plan, make the call to your current provider, and do most of the work outside your hours. Up to $5,000 credited against onboarding, and it’s finished inside a month.
The bill was never the real problem.
We took that off the table because it’s the reason people give. It isn’t usually the reason they stay. Here are the ones they don’t say out loud, and what we do about each.
Nobody has time to run it.
A transition is a project, and projects need somebody to own them. You already have a job.
A Project Manager owns the schedule, the vendor calls and the checklist.
You don’t know what your contract says.
Most agreements have a notice period and an auto-renewal date, and most people find out which when they try to leave.
Send us the agreement and we’ll find the dates that matter.
You’re worried about being held on the way out.
Domain registrations. Microsoft tenant ownership. Licence assignments. Administrator credentials on equipment you paid for.
We inventory all of it before you give notice, not after.
You’re worried something quiet will break in month three.
The risk isn’t the day of the cutover. It’s the backup job nobody documented, or the certificate that expires in November.
That’s what the assessment is for, and it happens before we quote.
If it goes wrong, it’s on you.
You’re the person who recommended the change. That’s the quiet reason a lot of these decisions never get made, and no website will say it, so we will.
Sometimes staying put is the right call — you’re mid-way through replacing your accounting system, or your agreement renews in nine months with no exit clause. We’d rather say so in week one than have you regret it in month four.
You see the plan in full before you commit, and you can stop there at no cost.
You assume the free part has a catch.
It usually does. The standard version of this offer buys your onboarding in exchange for signing three years.
Ours has no minimum term. What happens after is judged on whether we’re any good.
What the $5,000 actually covers.
Onboarding means taking control. Your environment, physical and digital, handed over to us properly so we can be responsible for it. That’s the assessment. Documenting what you have. Standing up monitoring and security. Transferring licences, credentials and ownership. Coordinating the handover with your outgoing provider. The project management that holds all of it together.
The credit applies to our hours doing that work. Up to $5,000 of it.
That’s the whole rule. If it’s our people’s time taking control of your environment, the credit covers it. If it’s somebody else’s invoice — Microsoft, a hardware vendor, your outgoing provider — it doesn’t.
There’s no term attached.
You don’t have to sign a three-year agreement to get the credit. It’s limited by what the work is, not by how long you stay.
It’s onboarding only.
Getting you moved across and running properly is what’s credited. A project you ask us to take on in month three is a project, and it’s quoted like one.
When we find something broken.
Taking responsibility for what’s there and making what’s there good are two different questions, and the second one gets its own answer.
Sometimes the assessment turns up a fundamental fault. Cabling that was never run properly. A switch that’s failing. Equipment past the end of its working life. That isn’t day-to-day support and it isn’t proactive maintenance — it’s a repair, and calling it onboarding would just bury the cost somewhere you can’t see it.
So we don’t. We show you what we found, and it becomes its own one-time project with a written scope and a quote, so you can see exactly what’s proposed and what it costs before you decide anything. You can say no. The transition carries on around it.
Nothing in this transition gets invoiced to you without a quote you approved first.
Switching IT providers takes about a month. You’ll know the exact date in week one.
We look before we quote.
A full assessment of what you have, including a security review. We build the plan on what’s actually running, not on what got described over the phone. At the end of this week you have a written plan, a date, and a number.
We make the awkward call.
We coordinate the handover with your current provider directly. You don’t have to manage that relationship on your way out the door. Notice goes in on the date your contract says it should, not before.
Most of it happens quietly.
Monitoring, security, documentation, licence transfers. The bulk of it is done remotely and in the background. Your Project Manager tells you what’s happening before it happens, not after.
Cutover.
Scheduled around your operating hours wherever it can be. The parts that can’t happen in the background happen when the fewest people are working.
You get a name, not a queue.
You’re introduced to your Client Relationship Specialist, who becomes your point of contact from that day on, backed by the IT team, the security team, and the developers.
Your team’s part of this, in one column.
Most of a transition happens without you. This is the whole of what we need from your side.
- Give us access for the assessment
- Send us your current agreement
- Name one person who can approve decisions
- Approve the plan
- Tell your staff the date
- The assessment and the security review
- Reading your agreement and finding the dates that matter
- The plan, the schedule, and the quote
- The conversation with your outgoing provider
- Monitoring, security, documentation, licence transfer
- The cutover, mostly outside your hours
- Everything after
Five things. Everything else is ours.
You’re probably under contract. That’s usually fine.
Most agreements run month to month after an initial term, or renew annually on a date nobody remembers. A few have notice periods measured in months. Whichever yours is, the answer is the same: we work out the dates before anything is signed, and we build the schedule around them.
What we won’t do is tell you to break an agreement. If the timing means the right move is to start the assessment now and transition in four months, that’s the plan we’ll give you.
Five questions almost nobody can answer.
If half of this reads like jargon, that is more or less the point. These are the details that quietly decide how easily you can leave, and hardly anyone outside IT keeps track of them — there is no particular reason you should. Not knowing isn’t a failing. Finding out is our job, and we work through all five with you during the assessment, before notice goes in.
What to check before you leave your IT provider
- Who is the registrant on your domain names?
- Who owns your Microsoft tenant, and are your licences assigned to it or to theirs?
- Do you have administrator credentials for your own firewall and switches?
- Where do your backups live, and whose account are they in?
- What is your notice period, and when does the agreement renew?
Most people we ask can answer one or two. Plenty can’t answer any, and that puts them in good company. Every one of these has an answer once somebody goes looking, and you shouldn’t have to be the one looking.
Sometimes the thing that keeps breaking isn’t the network.
Most providers find those during the assessment, mark them out of scope, and move on. That’s how a business changes IT providers and still has the same problem six months later.
We have developers on staff — the same team that builds custom software and runs our own products. When the assessment turns up something like that, we can support it, rebuild it, or tell you plainly that it should be replaced and what that would cost. It stops being a thing you live with.
What working with us is actually like.
“The team at BKY are amazing, they take the time to get to know their clients needs and work with them to provide the best support. I would highly recommend them to any business looking for managed IT services.”
“BKY’s team has been very responsive and efficient with all of my IT needs. They are quick to respond and resolve issues in the day to day operations.”
If you ever want out, we won’t make it hard.
It has happened twice in five years. Both times we handed over what the next provider needed — documentation, configurations, credentials, and every account and licence that belonged to the client rather than to us — and then we stayed out of it. No exit fee, and nothing held back to make the move harder than it needed to be.
We’d rather keep you because the work is good than because getting out would be painful.
That’s the argument this whole page makes. It would be strange to stop making it the day you sign.
Everything else you’d want to know before you call.
What does the $5,000 credit actually cover?
It applies to our hours taking control of your environment: the assessment, documenting what you have, standing up monitoring and security, transferring licences and credentials, and coordinating with your outgoing provider. It doesn’t cover hardware or third-party subscriptions like Microsoft licensing. If it’s our people’s time, the credit covers it. If it’s another company’s invoice, it doesn’t.
Do we have to sign a long-term agreement to get the credit?
No. There’s no minimum term attached. The credit is limited by what the work is — it covers onboarding — not by how long you stay afterward.
How long does it take to switch IT providers?
Inside a month, in most cases. You’ll have a written plan and a firm date at the end of the first week, before you commit to anything.
What if you find something that’s actually broken?
Sometimes we do — cabling that was never run properly, a switch that’s failing, equipment past the end of its working life. That’s a repair rather than part of taking over, so we don’t fold it into onboarding and hope you don’t notice. We show you what we found, scope it as its own one-time project, and quote it, so you can see the work and the cost before deciding. You can say no, and the transition carries on around it. Nothing in the transition gets invoiced without a quote you approved first.
What if we’re still under contract with our current provider?
Common, and usually workable. Send us the agreement — we’ll find the notice period and the renewal date and schedule the transition around them, so you’re never paying two providers at once. We won’t advise you to break an agreement.
Who tells our current provider we’re leaving?
You give the formal notice, because it’s your agreement. We handle the technical handover conversations from there, so you’re not managing that relationship on your way out the door.
What if they won’t cooperate?
It happens occasionally. It’s why we inventory domain registrations, tenant ownership, licence assignments and administrator credentials during the assessment — before notice goes in. Knowing what you own in advance turns an uncooperative handover from a problem into an inconvenience.
Will our staff lose access to anything?
The plan is built so they don’t. Most of the work happens remotely and in the background, and the parts that require a cutover are scheduled around your operating hours where they can be. Your Project Manager tells your team what’s changing before it changes.
Do you actually come on site, or is this all remote?
We come on site. Most day-to-day support is faster handled remotely, so that’s where the bulk of it happens, but our team is spread across Alberta and our people spend most of their working week at client sites rather than in a call centre. When something needs hands on it, hands turn up. There’s no travel charge for the visit if you’re in the greater Edmonton or Calgary area.
What happens if we ever want to leave BKY?
You get everything you need to run your systems somewhere else: documentation, configurations, credentials, and ownership of what’s yours. It’s happened twice in five years and we didn’t get in the way either time.
Start with the assessment. Decide after.
No cost, no commitment, and the plan is yours either way. If it says stay where you are this year, that’s what it’ll say.