Migrating from TeamViewer without disrupting your clients

Switching remote-control tools should never happen at your clients’ expense. With a two-phase cutover, you migrate without interrupting a single session and without anyone reinstalling anything.

The principle: parallel, then switch

You cut nothing until the new tool runs. Old and new coexist during the transition, each on its own scope, until the full switch. That is the entire trick: two tools, one handover, zero downtime.

Step 1. Take stock of what exists

Before deciding anything, list what has to move.

• Technicians, their rights and their habits.
• The number of machines under unattended access.
• The machines that escape normal deployment: off-domain devices and personal laptops.
• The end date of the current contract: the ideal is to switch before renewal.

This list is your dashboard until the final uninstall.

With Ubidesk, subscriptions cancel monthly with no commitment, and early customers had their price locked for 24 months. You do not need to run two annual contracts in parallel or wait for a distant renewal date.

Step 2. Pilot on a small group

Test with a few technicians and a few machines first.

• Check firewall traversal: Ubidesk uses port 443 only.
• Turn on multi-factor authentication, mandatory, via TOTP, passkeys or FIDO2.
• Run a first attended session with a 6-digit code.

If something blocks, fix it before widening: the pilot exists to absorb surprises.

Step 3. Prepare your clients

A short notice is enough. Announce the change: same service, new entry point, nothing to install. Send it a week ahead, and repeat it the day before. On the client side, sessions start with a 6-digit code through a temporary client, with no installation and no administrator rights. File transfers still require explicit confirmation, no exceptions. Mention the verified technician badge too: your clients will know a real session from a scam.

Step 4. Switch attended support

On cutover day, give clients the new entry point. Ubidesk remote support keeps the same workflow: invitation, session, close. Your clients find their bearings in the first minute. Same screens, same steps, new name.

Step 5. Migrate unattended machines

Deploy the agent to the machines you maintain, via GPO, Intune or Jamf.

• The agent reconnects automatically after a reboot, including in Safe Mode.
• Wake-on-LAN powers on a sleeping machine when the intervention starts.
• Track the rollout in device management to confirm every machine reports in.

Cross the list against the step 1 inventory: every gap is a machine that could have lost access.

Step 6. Remove the old tool

Let a few incident-free days pass, then remove the old software from the fleet and revoke licences. Archive access logs before closing the account. A final inventory sweep confirms nothing was left behind.

The questions your clients will ask

• Why change? Short answer: you are consolidating tools, and their experience stays the same.
• Do I need to reinstall anything? No: the temporary client runs on the spot, with no installation and no administrator rights.
• Is my data still protected? Transfers require their confirmation, and banking sites and password fields blur during the session.

What your clients should remember

• Nothing to install on their side.
• The technician stays identifiable through a verified badge.
• File transfers always require their approval.
• Banking sites and password fields blur during the session.

A clean migration is judged by one criterion: the client notices only the name change. The same roadmap works for MSPs switching several clients at once. Pilot one client first, validate, then repeat the run for the rest.