Switching IT providers starts with knowing who controls your business accounts. Your domain, email, backups, and software subscriptions may each have a different administrator or billing contact. A handoff gives you a chance to confirm those details while the outgoing provider can still answer questions. For a Bakersfield business, the work also needs to fit around staff schedules and any systems that must stay available. Put an owner and a verification step beside each item before agreeing that the transition is finished.
Collect an account inventory, business-controlled administrator and recovery access, license records, backup details, vendor contacts, and current system documentation. Agree on the transfer date and support responsibilities with both providers. Have the incoming provider test its approved access, confirm that essential work still functions, and document removal of the outgoing provider's access at the agreed time.
The worksheet below is an editorial planning aid. Adapt it to your systems, contracts, and vendor requirements. A provider change doesn't require every service to move at once.
Name a business owner who can authorize access and accept the completed work. Each provider should identify a technical contact. Review the existing agreement for notice periods, exit work, documentation delivery, and any charges that need approval. Your IT support quote should also explain what the incoming provider will handle during onboarding.
Set the work window around the tasks your staff need to perform. Record any planned outage, the person who can stop a change, and the fallback if testing fails. Tell employees when the support contact changes and how to report a problem during the transition.
| Area | What to collect | How to verify the handoff |
|---|---|---|
| Domain and DNS | Registrar, registered holder, renewal date, billing contact, DNS host, and current records. | An authorized business contact can reach the account and recovery method. Confirm website and email behavior after any approved change. |
| Email and cloud administration | Tenant identifier, approved administrators, partner relationships, authentication methods, and recovery process. | The incoming administrator signs in with an individual approved account and confirms the required role. |
| Software and licenses | Product, subscription owner, reseller, assigned users, renewal terms, and vendor support entitlement. | Confirm who will supply and bill each license after the transition and when any change takes effect. |
| Backups | Protected systems, console access, storage locations, retention, encryption-key custody, alerts, and recent test results. | Complete an agreed restore test and confirm who receives failure alerts. Record how older backups will remain accessible. |
| Devices and network | Inventory, configuration records, firewall and Wi-Fi administration, device recovery keys, and approved remote tools. | Test authorized management access and essential connections. Confirm who handles each device and location. |
| Security services | Covered devices and identities, tool ownership, alert contacts, log retention, and incident escalation. | Confirm replacement coverage and alert delivery before retiring outgoing tools. |
| Business vendors | Internet, phones, website, line-of-business applications, support account numbers, and authorized contacts. | Ask each vendor to confirm the new support contact and its process for approving access. |
| Open work | Unresolved tickets, scheduled changes, known faults, warranties, and pending renewals. | Assign each item to a named person, with a next action and review date. |
Keep passwords, recovery codes, private keys, and sensitive configuration files out of the worksheet. Record their secure storage location and authorized custodian instead. Agree on a protected transfer method and confirm the recipient through a known contact channel.
Your registrar handles the domain registration. DNS hosting directs services such as your website and email. Identify both before approving changes. Ask whether the handoff can retain the current registration and DNS setup while transferring the needed administration.
If a registrar transfer is required, check the current registrar's process and transfer status first. ICANN explains that some changes to registrant details can trigger a 60-day transfer lock. Coordinate the order of account and registration changes with the registrar. Preserve a copy of the DNS records and confirm the renewal arrangement before work begins.
Use named accounts with the permissions needed for the approved work. Confirm that the business can recover administrative access without depending entirely on the departing provider's email address or phone. Have a qualified administrator review emergency access as part of that work.
For Microsoft Entra ID, Microsoft recommends at least two emergency access accounts, protected with strong authentication, securely stored credentials, monitoring, and regular validation. Their configuration needs careful review against Microsoft's current guidance. Routine provider work belongs in normal administrative accounts.
In Microsoft 365, review Settings > Partner relationships as well as accounts inside the tenant. Microsoft distinguishes partner administrator roles from the reseller relationship. Removing admin roles leaves that relationship in place, so confirm billing and subscription arrangements separately. The incoming provider should explain the roles it requests and why those roles are needed.
Include approved applications, service accounts, API credentials, and remote-management tools in the review. Record their dependencies before changing secrets or removing access. A service account used by a scheduled task needs its own change and test plan.
Ask both providers which services will continue, which will move, and which must be replaced. Put the order in writing. Confirm the right to retain and restore existing backup data, any export limits, the required software, and the charges that apply after the support agreement ends.
NIST's small-business guidance recommends an asset inventory, access appropriate to each person's work, and tested backups. Apply those checks to the transition. Have the incoming provider restore an agreed item into a safe location and record the result. Broader application recovery needs separate testing, including the dependencies described in our minimum viable recovery guide.
Coordinate removal of endpoint protection and monitoring agents with the replacement plan and each vendor's instructions. Agree on who receives alerts throughout the change. Review cybersecurity service responsibilities and backup and recovery scope when assigning that work.
Use a completion record with these fields: system, business owner, outgoing contact, incoming contact, action, test result, evidence location, completion date, and remaining exception. This creates a useful record without placing secrets in general meeting notes.
Confirm your tenant, subscription arrangements, and administrative control with the providers before planning a migration. A support-provider change can often take place within the existing tenant. Licensing and reseller changes need their own review, including current terms and effective dates.
For a planned transition, agree on the sequence and verify replacement access and service coverage before the scheduled removal. Suspected unauthorized access requires action under your incident response process and may change that order. Escalate that concern promptly to the person authorized to direct the response.
Set the schedule after reviewing the inventory and dependencies. Missing account control, vendor approvals, subscription terms, and data-transfer work can affect timing. Ask for milestones and the unresolved items that could delay them.
Contact Second Star Technologies to discuss your systems and a proposed handoff scope. Bring your service inventory and any known access gaps, keeping credentials out of the initial message. Our managed IT services information explains how coverage and responsibilities are defined in a written proposal.
Editorial review: October 15, 2026. Platform procedures and contract terms should be checked again before a live transition.
Read the audio summary transcriptBefore your business changes IT providers, find out who controls its domain and how an authorized person can recover each important account. Confirm who receives renewal notices and pays the bills. Ask the outgoing provider to explain where the current settings are documented. Those answers help you plan the handoff while the people who know your systems are still available.
Welcome to The IT Edge: Business Tech Made Simple, from Second Star Technologies. Today we're talking about the account and access checks to make when your business changes IT providers.
Start by naming the person in your business who can authorize the work. That person should receive a written handoff plan from the providers, with the timing, expected interruptions, and a contact for problems. Review your existing agreement for notice requirements and exit work. Ask the incoming provider which onboarding tasks are included in its proposal.
Next, build an inventory of the services your staff depend on. Include your domain registration and DNS hosting, business email, backup service, network equipment, security tools, and the applications people use to do their jobs. For each service, record the account owner, the administrator, the billing contact, and how the business recovers access. Keep passwords and recovery codes in an approved secure location. Your worksheet should point to the custodian or storage location.
Domain registration deserves a separate check. Changing IT providers may leave the registrar and DNS host in place. If a registrar transfer is needed, confirm the process before changing registration details. Some registrant changes can trigger a transfer lock. Have the registrar and technical contacts agree on the sequence while you still have access to the existing setup.
For administrative access, ask the incoming provider to use individual accounts and explain the permissions it needs. Confirm that someone authorized by your business can recover control if the normal administrator becomes unavailable. Microsoft publishes specific guidance for emergency access accounts. Have a qualified administrator check that setup, including authentication, secure storage, monitoring, and testing.
If you use Microsoft 365, review partner relationships as well as user accounts. Partner admin roles and the reseller relationship are separate. Removing admin roles leaves the reseller relationship in place. Confirm who will supply your licenses and handle billing after the change, using the current subscription terms.
Backups need a practical handoff test. Agree on an item to restore into a safe location, and record whether it works. Check who holds any required encryption keys, who gets failure alerts, and how you can restore older backups after the outgoing contract ends. If a full business application needs recovery, plan testing for its other systems and accounts too.
Security tools need coordination during the same window. Ask when the new coverage starts and when outgoing tools will be removed. Follow vendor instructions, and confirm who receives alerts throughout the change. Include remote support tools and service accounts in that review, since they can provide access outside an ordinary staff login.
Before signing off, have staff test the work affected by the transition. Check that the incoming provider can perform its approved tasks. Then close the outgoing access at the authorized time and record the actions taken. Give any remaining problem an owner and a review date.
You can begin today by listing your key services and asking who controls each account. If you're planning a provider change in Bakersfield or Kern County, contact Second Star Technologies to discuss your systems and a written handoff scope. Keep credentials out of your first message. We'll start with the work you need covered and the gaps that need an answer.
Internet Corporation for Assigned Names and Numbers. (n.d.). FAQs for registrants: Transferring your domain name. https://www.icann.org/resources/pages/name-holder-faqs-2017-10-10-en
Microsoft. (2026, March 30). Manage Microsoft-certified solution provider partner relationships. Microsoft Learn. https://learn.microsoft.com/en-us/microsoft-365/commerce/manage-partners?view=o365-worldwide
Microsoft. (2026, September 3). Review Microsoft-certified cloud solution provider (partner) administrative privileges. Microsoft Learn. https://learn.microsoft.com/en-us/microsoft-365/commerce/review-partner-admin-privileges?view=o365-worldwide
Microsoft. (n.d.). Manage emergency access accounts in Microsoft Entra ID. Microsoft Learn. https://learn.microsoft.com/en-us/entra/identity/role-based-access-control/security-emergency-access
National Institute of Standards and Technology. (2024). NIST Cybersecurity Framework 2.0: Small business quick-start guide (NIST SP 1300). https://doi.org/10.6028/NIST.SP.1300