“`html

MSP Handover Checklist When Changing IT Providers

An MSP handover checklist helps make sure your business receives the passwords, accounts, licenses, configurations, documentation, and vendor information needed before changing IT providers. Without a complete handover, the new provider may spend valuable time rebuilding information that should already belong to your company.

For an Atlanta law firm, accounting office, construction company, nonprofit, or other small business, changing IT providers can affect much more than helpdesk support. Your outgoing MSP may have administrative access to Microsoft 365, network equipment, backups, security tools, software subscriptions, domains, and other systems employees depend on every day.

A good transition is not simply about getting a list of passwords. The goal is to give the incoming IT provider enough accurate information and access to understand, support, secure, and manage the environment without unnecessary disruption.

What Should an MSP Hand Over When You Change Providers?

Your outgoing MSP should transfer the administrative access, system documentation, licenses, configurations, vendor details, security information, and technical records your company needs to maintain control of its IT environment.

The exact list depends on your environment. A ten-person consulting company may have a relatively simple setup, while a manufacturer or financial services company may have multiple locations, servers, cloud platforms, network appliances, line-of-business applications, and outside technology vendors.

The important principle is ownership. Your business should know which systems it uses, who owns each account, how those systems are accessed, what services are being paid for, and which vendors support them.

1. Administrative Accounts and Passwords

Administrative credentials are among the most important items in an MSP transition. The new provider needs appropriate administrative access to manage the systems it will be responsible for supporting.

Depending on your environment, the handover may include:

• Microsoft 365 or Google Workspace administrator accounts
• Local and domain administrator accounts
• Server administration credentials
• Firewall and router credentials
• Wireless network management accounts
• Backup platform administrator access
• Endpoint management platform access
• Security platform administrator accounts
• Phone system administration credentials
• Website hosting, domain registrar, and DNS accounts

Passwords should be transferred using an appropriate secure method rather than placed in an unprotected document or ordinary email. After the transition, privileged passwords and recovery methods should also be reviewed so former provider access can be removed where appropriate.

Do not forget multifactor authentication

A username and password may not be enough to transfer an account. The business should also understand who controls multifactor authentication, recovery email addresses, recovery phone numbers, hardware tokens, and emergency administrator accounts.

An account technically owned by your company can still become difficult to recover if its authentication or recovery options point only to the outgoing provider.

2. Domain, DNS, Email, and Cloud Account Ownership

Your company should know who owns and controls the accounts behind its domain name, email platform, DNS records, cloud applications, and other business-critical online services.

The outgoing MSP should identify important accounts and provide the access or ownership information needed for the new provider to manage them.

• Domain registrar
• DNS hosting provider
• Microsoft 365 tenant
• Google Workspace environment
• Cloud storage platforms
• Website hosting
• Email filtering or security services
• Cloud backup services
• Other SaaS platforms administered by the MSP

This becomes especially important when an MSP originally created accounts on the client’s behalf. The incoming provider should be able to determine whether the business itself is the account owner or whether changes are needed to establish clearer ownership.

3. Network and Infrastructure Documentation

Network documentation gives the incoming MSP a working map of how your technology is connected. Without it, technicians may have to rediscover basic details during troubleshooting.

Useful documentation can include:

• Network diagrams
• Firewall configuration information
• Router and switch information
• Wireless network configurations
• IP address assignments
• VLAN information where applicable
• VPN configurations
• Server names and roles
• Internet service details
• Remote access configurations

Why does network documentation matter?

Imagine an Atlanta architecture firm loses access to a shared application or network resource. If the new IT provider already understands the firewall, switches, servers, and network layout, troubleshooting can begin with useful context instead of first trying to reconstruct the environment.

Good documentation does not solve every technical issue, but it can remove unnecessary uncertainty during support and planning.

4. Complete Device and Hardware Inventory

The new provider should receive a reasonable inventory of the devices and infrastructure it is expected to support.

That may include:

• Desktop computers
• Laptops
• Servers
• Firewalls
• Network switches
• Wireless access points
• Printers and scanners
• Phone equipment
• Backup devices
• Other managed endpoints

Useful inventory details can include device name, model, serial number, assigned employee, operating system, warranty information, location, and management status when available.

5. Software Licenses and Subscription Information

Software licensing should be clearly documented before the outgoing provider leaves. Your company needs to know what it is paying for, who owns each license, how renewals work, and whether any subscription is tied to the MSP’s own account.

Review items such as:

• Microsoft 365 licenses
• Google Workspace subscriptions
• Antivirus and endpoint security licenses
• Backup subscriptions
• Remote access tools
• Line-of-business applications
• Cloud storage
• Phone system licensing
• Other software purchased or managed through the MSP

Ask who controls renewal and billing

A license list is more useful when it also identifies renewal dates, billing arrangements, contract terms, and the account that controls each subscription. This helps prevent an important service from being overlooked after the MSP relationship ends.

6. Backup and Business Continuity Information

The incoming provider should understand how business data is backed up, where backups are stored, how they are monitored, and what systems are covered.

A backup handover may include:

• Backup platform access
• Systems included in backups
• Backup schedules
• Storage destinations
• Retention settings
• Recent backup status information
• Recovery procedures or documentation
• Business continuity systems currently in place

The new MSP should review this information rather than assume the existing backup setup meets the company’s current recovery needs. Backup strategy should reflect the systems, data, operating requirements, and risk profile of the business.

7. Security Tools and Existing Cybersecurity Controls

A provider change should include a clear handover of the security tools currently protecting users, devices, email, networks, and other systems.

The incoming MSP may need information about antivirus, endpoint protection, DNS filtering, email filtering, multifactor authentication, firewall policies, security alerts, patch management, and other controls currently deployed.

Cybersecurity deserves particular attention during a provider transition because administrative access is changing hands. The business and incoming MSP should review which former accounts or remote management tools should be removed once the handover is complete.

8. Vendor, Carrier, and Support Contact Information

Most businesses rely on more technology vendors than they realize. The MSP may have been coordinating with many of them behind the scenes.

Ask for information about providers such as:

• Internet service providers
• Phone carriers
• Copier and printer vendors
• Software vendors
• Website and hosting companies
• Cloud service providers
• Security vendors
• Backup vendors
• Line-of-business application support teams

Account numbers, support numbers, portal access, authorized contacts, and contract details can make future vendor coordination much easier.

9. IT Documentation, Procedures, and Known Issues

A strong MSP handover should include the operational knowledge the outgoing provider has built while supporting your company.

Useful documentation may cover:

• New employee setup procedures
• Employee termination procedures
• Common troubleshooting steps
• Application-specific instructions
• Network and server documentation
• Security policies
• Backup procedures
• Recurring maintenance activities
• Known technical problems or limitations

Known issues are especially valuable. The new provider should not have to discover that a certain application requires a special configuration or that a recurring network problem has already been investigated several times.

10. Open Tickets, Projects, Contracts, and Renewal Dates

The provider transition should also capture work that is still in progress. A clean handover identifies what has been completed, what remains unresolved, and what commitments are approaching.

• Open support tickets
• Unresolved recurring problems
• Hardware orders
• Software migrations
• Infrastructure projects
• Pending warranty claims
• License renewals
• Vendor contracts
• Internet or phone service changes

This prevents an unfinished project from disappearing between providers and gives the new MSP a clearer picture of immediate priorities.

What Are the Most Common MSP Handover Problems?

Most difficult IT transitions are not caused by one missing password. They usually happen because important knowledge, ownership, and access are spread across different people, platforms, and vendors.

Common problems include:

• Accounts registered to the former MSP: The company discovers that an important portal or subscription is controlled through the provider’s account.
• Incomplete documentation: The new provider receives credentials but little explanation of how systems are configured.
• Unknown recurring services: Software, security, backup, or telecom services continue billing without clear ownership.
• Old remote access remains active: Former support tools or administrator accounts are not reviewed after the transition.
• Projects disappear between providers: An unresolved ticket, upgrade, or renewal is not included in the handover.

These problems are easier to address when the incoming provider is involved before the final termination date instead of receiving whatever information happens to be available afterward.

A Simple MSP Transition Checklist for Business Owners

Before your current MSP relationship ends, confirm that your business can identify its systems, access its administrative accounts, verify its licenses, locate its documentation, and understand which vendors support its technology.

Use this checklist with your outgoing and incoming providers:

1. Identify every system the current MSP manages.
2. Confirm your company has administrative ownership or appropriate access.
3. Collect documentation for networks, servers, devices, cloud platforms, and applications.
4. Document software licenses, subscriptions, contracts, and renewal dates.
5. Review backup systems and recovery procedures.
6. Identify security products and remote management tools.
7. Collect vendor and carrier contact information.
8. Review unresolved tickets and projects.
9. Agree on a secure method for transferring credentials.
10. Schedule removal or modification of former provider access after transition.

When Should the New MSP Get Involved?

Ideally, the incoming MSP should be involved before the outgoing provider’s access ends. This creates an opportunity to identify missing information while the current provider can still answer questions and provide documentation.

The incoming MSP can review what has been supplied, identify obvious gaps, verify access, document the environment, and build a transition plan around the systems that matter most to daily operations.

For example, an Atlanta accounting firm changing providers should not wait until the day after its former MSP is disconnected to discover that nobody has administrative access to an important server, Microsoft 365 account, or backup platform.

What Should the New MSP Do After the Handover?

Receiving documentation is only the first step. The incoming provider should validate the environment instead of assuming every document is current or every configuration is appropriate.

A practical onboarding review may include:

• Confirming administrator access
• Reviewing device inventory
• Checking software update and patch status
• Reviewing endpoint protection
• Understanding backup coverage
• Reviewing network equipment and configurations
• Documenting cloud platforms and business applications
• Reviewing open technical issues
• Removing unnecessary legacy access where appropriate

This is where proactive managed IT becomes different from simply taking over a helpdesk phone number. The provider needs enough visibility into the environment to support users, maintain devices, monitor infrastructure, coordinate vendors, and help plan future improvements.

Reactive Handover vs. Proactive MSP Transition

A reactive transition waits for missing information to become a problem. A proactive transition identifies dependencies before the provider change is complete.

A reactive transition often looks like this

• The old MSP disconnects first.
• The new MSP starts asking for passwords afterward.
• Nobody knows who owns certain accounts.
• Network documentation is incomplete.
• The new provider discovers unknown vendors during a support problem.

A proactive transition looks different

• Systems and vendors are identified first.
• Administrative access is verified.
• Documentation is reviewed before the handover closes.
• Open projects and known issues are documented.
• The incoming MSP has a plan for onboarding and support.

The proactive approach gives the business more visibility and reduces the amount of technical knowledge that depends on one outgoing provider.

How Can Atlanta Businesses Prepare Before Changing MSPs?

Start by building an internal list of the systems your employees depend on. You do not need to understand every technical detail. You need enough business visibility to ask the right questions.

Ask department leaders what applications they use, identify recurring technology invoices, review your internet and phone providers, and confirm where important administrative accounts are registered.

For businesses with multiple offices, remote employees, specialized software, servers, regulated information, or complex networks, the incoming MSP may need additional time to understand dependencies before making significant changes.

Questions to ask before your current MSP leaves

• Do we have administrative access to every major system?
• Are any accounts owned by the MSP instead of our company?
• Where is our network documentation?
• Which tools are licensed through the current MSP?
• Who manages our backups?
• What remote access tools does the MSP currently use?
• Which contracts or subscriptions are approaching renewal?
• Are there unresolved IT issues or unfinished projects?
• Which outside vendors does the MSP normally contact for us?

How trueITpros Approaches an MSP Transition

When an Atlanta business changes IT providers, the transition should establish a clear understanding of users, devices, networks, cloud platforms, security tools, applications, vendors, backups, and current technical priorities.

trueITpros provides Managed IT Services that can include endpoint management, software updates and security patch maintenance, antivirus and malware protection, Microsoft 365 and Google Workspace administration, line-of-business application support, managed networking, infrastructure monitoring, onsite support, business continuity services, and strategic Virtual CIO and CTO guidance.

The goal is not simply to inherit the previous provider’s setup. It is to understand what the business has, identify areas that need attention, build accurate documentation, and create a more manageable support structure going forward.

Frequently Asked Questions About Changing MSPs

Does my MSP have to give me my passwords when I leave?

Your business should identify and obtain appropriate access to the systems and accounts it owns or is responsible for managing. Contract terms and account structures can differ, so review your agreement and ownership details before the transition date.

How long should an MSP transition take?

The timeline depends on the size and complexity of the environment. A small office with mostly cloud services may require less coordination than a multi-location company with servers, specialized applications, networking equipment, and several vendors.

Should the old MSP and new MSP communicate directly?

Direct technical communication can make the transition more efficient when all parties cooperate. It allows the incoming provider to ask specific questions about systems, configurations, documentation, vendors, and unresolved issues.

What passwords should I change after switching IT providers?

Privileged accounts and other credentials previously accessible to the outgoing provider should be reviewed. The appropriate changes depend on your environment, authentication methods, and which systems the former provider could access.

Can a new MSP help if our old provider did not document everything?

Yes. An incoming MSP can inventory systems, verify accounts, review network equipment, identify services, and rebuild documentation. However, obtaining as much information as possible before the old provider leaves usually makes the transition easier.

Make Your Next IT Provider Transition More Organized

Changing MSPs should leave your business with more clarity, not less. Before the relationship with your current provider ends, make sure you understand your administrative accounts, licenses, network, devices, backups, vendors, security tools, documentation, open projects, and recurring services.

Bringing the incoming provider into the process early can also help uncover missing information while there is still time to resolve it.

To learn more about how trueITpros can help your business with changing IT providers and MSP handovers, contact us.

To learn more about how trueITpros can help your company with Managed IT Services in Atlanta, contact us at www.trueitpros.com/contact

Related Content

• Why Email Security Matters for Atlanta SMBs
• What is a Managed IT Service Provider (MSP) & How Can It Help Your Business?

“`