You can change IT providers without starting by unplugging anything. First identify who legally owns each account and device, preserve current access, and document dependencies. Then plan a controlled handoff for the firewall, Microsoft 365, internet service, backups, and building systems. If the incumbent will not cooperate, use documented ownership and vendor recovery channels rather than guessing passwords or disrupting service.
In This Article
- Which systems should a Carmel business put on its handoff list?
- How do we change providers without interrupting email or internet?
- What if the former IT company will not share administrator access?
- What should Carmel offices and multi-tenant buildings coordinate?
- How can we judge whether the handoff is actually complete?
- Frequently Asked Questions
Which systems should a Carmel business put on its handoff list?
Start with the systems that can stop work across the office. That usually means the firewall and network equipment, internet and voice services, Microsoft 365, endpoint administration, backups, and any security or building technology tied to the network.
In a Carmel City Center office, a multi-tenant building, or a space along the US-31 corridor, the technical handoff may also involve landlord-controlled equipment rooms, shared cabling pathways, building access systems, or a carrier account held in another party's name. Keep those responsibilities distinct: the tenant's IT provider should not assume authority over landlord or facilities systems.
For each item, record the owner, account holder, administrator, renewal or contract contact, physical location, and recovery method. Include the serial number and support details for network equipment where available. A password list alone is not an inventory; it can leave out account ownership, recovery email addresses, licensing, and vendor support rights.
- Firewall, switches, wireless equipment, and configuration backups.
- Microsoft 365 tenant, administrator accounts, licenses, domains, and recovery contacts.
- Internet, DNS, telephone, backup, security, and line-of-business vendor accounts.
- Building access, cameras, cabling, and equipment-room responsibilities, where applicable.
- Documentation, support contracts, renewal dates, and current change requests.
Make a written inventory of every system that could interrupt work if its administrator account became unavailable.
The handoff list should follow business dependencies, not just the old provider's ticket categories.
How do we change providers without interrupting email or internet?
Do not begin by changing every password at once. First establish which accounts are controlled by your business, which are controlled by the incumbent, and which belong to a third-party vendor or property owner. Then agree on a change window and an order of operations based on how your staff actually work.
For Microsoft 365, confirm that an authorized business representative can access the tenant and its recovery methods before changing administrator roles. Document the current configuration and identify connected services that rely on the tenant, such as email routing, identity, collaboration, or business applications. A change to one account can affect more than the person signing in.
For the firewall and internet service, document the current configuration and support path before making changes. Confirm who can contact the carrier, who owns the circuit, and whether a building manager must approve access to a shared equipment room. A provider transition should not be treated as permission to alter a landlord's network or a production system without its owner.
Use a staged sequence: establish authorized access, capture the current state, confirm recovery options, coordinate vendor and building contacts, schedule changes, test the work that matters, and record the resulting configuration. Keep the previous service available until the replacement arrangement has been checked and responsibilities are clear.
For a business with compliance obligations, include the people responsible for privacy, security, or regulated workflows in the change plan. Indiana's Consumer Data Protection Act took effect January 1, 2026, and applies only when its applicability thresholds and conditions are met, with statutory exemptions. A provider change does not by itself determine whether the law applies to your organization. Review IT compliance support alongside your own legal and privacy review.
Keep the transition controlled, documented, and tied to the work employees need to perform.
What if the former IT company will not share administrator access?
First, separate a contractual disagreement from a technical recovery problem. Check the service agreement, invoices, equipment records, domain registration, and cloud billing records to establish what your organization owns and what the provider was authorized to manage. Avoid repeated password attempts or unapproved access methods; those can create security and accountability problems.
Ask the incumbent in writing for a specific handoff: the business-owned accounts, current administrator access or a supported transfer, equipment and configuration records, vendor contacts, and any scheduled changes. Set a clear date for the response and preserve the correspondence. If the request concerns a third-party service, contact that vendor through its documented account-recovery or ownership-verification process.
When credentials are returned, do not treat receipt as proof that access is complete. Check whether the business controls the recovery email, multifactor authentication, billing, domain, and any secondary administrator account. Remove former-provider access only after confirming an authorized replacement account works and that the change will not lock out the business or a required support vendor.
If there is a dispute about ownership or contract obligations, involve counsel before making a change that could affect service or evidence. If the issue involves suspected unauthorized access or an active security incident, prioritize containment and evidence preservation with qualified incident response support. Cybersecurity services can be part of the broader risk review; the specific response scope should be agreed before work begins.
Use documented recovery channels and preserve the record; do not turn a handoff dispute into an avoidable outage.
What should Carmel offices and multi-tenant buildings coordinate?
In a shared building, an IT transition may touch spaces and services your company does not control. Before a site visit or equipment change, identify who can authorize entry to telecom rooms, risers, shared network closets, and secured areas. Confirm building procedures with the property manager and coordinate any work that depends on landlord pathways or carrier access.
For a new tenant, an expanding office, or a move, map the sequence between internet activation, cabling, network equipment, user setup, and access systems. A missed handoff between a carrier appointment and a building access window can leave a technically sound plan waiting outside a locked room. Document who opens the space, who approves work, and who verifies each completed step.
Commercial real estate teams should also clarify the boundary between tenant-owned systems and building systems. Cameras, access control, shared Wi-Fi, riser cabling, and tenant networks can have different owners and support contracts. Commercial real estate technology planning should account for those boundaries instead of assuming one provider controls the whole property.
For work that includes a new tenant's infrastructure, define the requirements, landlord and vendor coordination, installation sequence, and handoff documentation before deployment. GDS Technology offers tenant technology buildout services; the scope should specify what is included and what remains the responsibility of the property team, carrier, or tenant.
Confirm site authority and ownership before scheduling physical work.
How can we judge whether the handoff is actually complete?
Closeout means more than a new provider saying they can log in. The business should know who owns each critical account, who can recover it, and who is responsible for support after the transition. Test access using the authorized business accounts, verify the agreed services, and make sure the final record reflects what changed.
Ask the incoming provider to document any access that remains unresolved, the operational impact, the party responsible for resolving it, and the next agreed step. The handoff record should distinguish confirmed access from an assumption or an open request. Where a system remains under a landlord or vendor, name that owner and the proper escalation route.
A real customer described the value of follow-through this way: "GDS followed up the next day to make sure the door sensor issue is resolved. That kind of attention shows real customer service." The example is a reminder to verify the outcome of a change, especially when technology affects a physical workflow, rather than closing the work at the moment a setting is adjusted.
GDS Technology provides managed IT and Microsoft 365 management services, including user administration, license review, access troubleshooting, tenant configuration review, change documentation, and vendor escalation within the agreed scope. It does not mean every migration, license charge, or third-party application task is automatically included. Confirm the service scope before the handoff begins.
Close the transition only when the business can verify access, responsibilities, and the work employees depend on.
Frequently Asked Questions
Can our old IT provider legally keep our administrator passwords?
That depends on account ownership, the service agreement, and the facts of the relationship. Review the contract and account records, then make a written, specific request for business-owned access and documentation. If ownership or contractual duties are disputed, seek legal advice before attempting access or making changes that could interrupt service.
Should we change every password on the first day with a new provider?
No. First confirm that your organization controls the recovery methods and that an authorized replacement administrator can sign in. Then plan changes in a sequence that accounts for email, identity, network equipment, vendors, and building systems. A rushed reset can lock out the business or break a service that still depends on the old configuration.
What should we check before changing the firewall?
Confirm who owns the firewall, who can authorize a change, and whether the internet circuit or building equipment is shared. Record the existing configuration and support contacts, plan an approved change window, and identify how to restore service if the change fails. Do not alter equipment controlled by a landlord or another party without authorization.
Does Indiana's Consumer Data Protection Act apply to every Carmel business?
No. Indiana's law took effect January 1, 2026, and its applicability depends on statutory conditions, including data-volume and revenue thresholds; the law also includes exemptions. A provider transition does not establish whether your business is covered. Review the law and your organization's facts with qualified legal or privacy counsel.
How do we know an IT provider handoff is finished?
Verify that the business can access the agreed accounts, recover them through business-controlled methods, and identify an owner and support route for each critical system. Confirm that planned tests were completed and that remaining exceptions are documented with a responsible party and next step. A successful login alone does not prove the full handoff is complete.