The consultant who has looked after your company for fifteen years sends a friendly retirement note. Everyone wishes them well. A week later, the printer stops working, the finance director needs an administrator to approve an application, and no one can say who owns the domain name or the Microsoft 365 tenant.
For a privately held company, this can feel like an awkward personal problem. In practice it's an ownership and continuity problem, and it has a practical fix. Most of what the consultant built can stay. The work ahead is about making sure the business can run, recover, and choose its next partner on its own.
At a glance
- Confirm who legally and administratively owns the core accounts before anyone changes production systems.
- Take inventory of identities, domains, DNS, backup, vendors, networking, devices, documentation, and recurring commitments.
- Move to named administrators, monitored emergency access, and a documented support model so the next transition is routine.
Keep the business stable first
When nobody is sure who has access, the urge to "clean everything up" is understandable. Hold off for the first few days. Changing a domain registrar, resetting service passwords, canceling a license, or replacing a firewall without knowing what depends on it can take down email, payroll, remote access, or backups. Stability comes first, and modernization can wait a week.
Ask one person, often the COO or controller, to coordinate the transition. Request a structured handover from the departing consultant while the relationship is still friendly. Keep a simple log of what changes, who makes the change, and when. If the departure is contentious, bring in your legal and contractual advisors before anyone tries to recover access. Ownership has to be established through authorized channels. Guesswork and credential workarounds only create new problems.
The first inventory: what the company must own
Domain and DNS
Identify the registrar, the registrant on record, administrative contacts, the DNS provider, account recovery methods, the renewal date, and the payment method. Email, the website, sign-in, and many business tools depend on DNS records. A domain registered under someone's personal account is a risk worth fixing promptly through the registrar's legitimate ownership process.
Microsoft 365 and identity
Find the tenant's verified domains, billing relationship, global administrators, Microsoft Entra roles, conditional access settings, recovery methods, shared mailboxes, service accounts, and any directory synchronized from an on-premises server. Confirm the company has its own authorized administrator identities instead of relying on the consultant's account. List any third-party delegated administration too.
Microsoft recommends keeping at least two carefully protected, cloud-only emergency access accounts in Entra. These are break-glass identities reserved for recovery, and nobody should treat them as everyday shared admin logins. They need secure custody, independent authentication options, monitoring, and periodic testing. No outside partner, old or new, should ever be the only party able to unlock your company.
Backups and recovery
Find the backup console, repository accounts, retention settings, encryption keys, recovery instructions, and the record of the last successful restore. A daily status email confirms that a job ran. Recovery is a separate question, so ask it directly: if the main administrator account disappeared tomorrow, could an authorized person restore a critical application and its data?
Networks, devices, and applications
List firewalls, switches, Wi-Fi equipment, internet contracts, remote-access tools, endpoint management, servers, line-of-business applications, accounting systems, and vendor support portals. Note physical locations and serial numbers where they matter. Most important, find out which systems sign in through other systems, and which ones rely on hard-coded integrations or shared passwords.
Contracts, costs, and people
Collect vendor agreements, support numbers, renewal dates, domain invoices, licensing arrangements, warranty details, escalation paths, and contacts. The person who pays the bill isn't always the person who controls the account. Sort out which obligations are in the company's name and which are tangled up in the former consultant's reseller agreement.
A practical first 30 days
Days 1 to 3: establish communication and priorities. Contact the consultant or current provider, agree on a handover date, ask about urgent renewals and fragile systems, and confirm backups are still running. Name the people authorized to make decisions for the company. If credentials are lost, start each vendor's documented recovery process instead of improvising.
Days 4 to 10: verify and record access. Set up company-controlled administrator access to the priority systems: registrar, DNS, identity, backup, network, and security monitoring. Test each access path without making destructive changes. Record the accounts, recovery factors, owners, and test dates in a secure repository. Flag personal accounts and service accounts that need a planned transition.
Days 11 to 20: separate responsibilities. Create named administrator identities, review privileges, rotate credentials where it makes sense, remove delegations you no longer need, and turn on alerts for unusual admin activity. Change service credentials only after you understand the impact, have talked with the application owners, and have a rollback plan. Run a recovery test on the current environment before anyone recommends a major redesign.
Days 21 to 30: decide what to improve. Rank risks by consequence: losing control of email or the domain, being unable to restore, unmonitored outside access, knowledge held by one person, and unsupported equipment. Write a short plan with cost, owner, sequence, and the evidence that will show each item is done. A system that works well can stay, even if its documentation was thin.
The handover meeting worth insisting on
Ask the former consultant to walk through one routine task and one emergency. For the routine side: how does a new employee get access, how is a laptop prepared, and where do requests go? For the emergency: how does the company reach the internet provider, spot a failed backup, restore the finance application, or shut down a compromised administrator account?
Request a current network diagram, a system inventory, an account ownership list, recovery instructions, known technical debt, open tickets, and pending renewals. Where documentation is incomplete, write down what's known, what's still unverified, and who can test it. A good handover document is one that another qualified professional could pick up and follow on their first day.
What if the consultant is unavailable or uncooperative?
Treat it as a structured recovery project. Gather contracts, invoices, domain registration records, corporate documents, proof of license ownership, and the names of authorized business contacts. Use each vendor's verified ownership or administrative recovery process, and keep a log of requests, approvals, and responses. Counsel may need to review service agreements and access rights.
Be wary of anyone who offers to "hack back into" a tenant or get around a provider's security. That creates a new security problem and a legal one. Authorized recovery takes longer, but it protects the company and leaves a clear record of who did what.
Choosing the next IT partner
Judge the next partner partly by the handoff they would leave behind. A good one will document the environment, make sure the company holds ownership and emergency access, explain licensing and recurring costs, and support a future change of provider without friction. Ask who will know your environment day to day, who can act after hours, how backups are tested, and whether your in-house team or trusted advisors can review the operating record.
At CTP, we start by understanding the environment and mapping its dependencies, then validate a plan and document the decisions. We treat identity, collaboration, monitoring, backup, applications, infrastructure, and connectivity as separate layers, so changing one vendor doesn't force a complete rebuild. For private companies, our managed IT work pairs that structure with a named senior contact and real discretion with sensitive information.
Make ownership the new normal
Getting access back is the immediate goal. The lasting benefit is ending the pattern where one person, however capable and trusted, holds the map to everything. Your company should own its systems, have tested ways to recover them, know who can make changes, and be able to welcome a new provider without an emergency.
If your consultant has already left, or a transition is on the horizon, we can help you set up a controlled handover before anyone proposes new tools. Read more about our work with private companies and family offices, or start a conversation.

