Migrating from TeamViewer

What transfers, what does not

Set the scope before starting. What transfers well:

• the device list in your address book;
• groups and device assignment;
• technician accounts, recreated in Ubidesk.

What does not transfer:

• TeamViewer connection history and logs: archive them before cancelling;
• unattended-access passwords stored on the TeamViewer side: redistribute them from scratch;
• custom modules: recreate them in Ubidesk.

Plan for a dual-run period, especially if some devices live outside your network.

Step 1 — Prepare the export from TeamViewer

1. Sign in to the Management Console for your account.
2. Export the device list of each group (name, ID, assigned group).
3. Note the policies you apply (unattended access, per-group permissions): you will use them to rebuild the same organization in Ubidesk.
4. Review the list: devices that have been offline for a long time are a good excuse for an inventory.

Step 2 — Create the Ubidesk workspace and map technicians

1. Create the Ubidesk workspace and choose the plan: Solo covers 50 devices (12 EUR per month), Pro and above are unlimited (24 EUR per technician per month). The full grid is on the Pricing page.
2. Create one account per technician. MFA is mandatory (TOTP, passkeys or FIDO2): allow a few minutes per person.
3. Recreate your device groups in the console to keep your working habits.

Step 3 — Redeploy the agents

The Ubidesk agent replaces the TeamViewer agent on every machine:

1. Download the right package: MSI, PKG, DEB or RPM.
2. Deploy it at scale with GPO or Intune (Windows) and Jamf (macOS). The detailed procedure is in Installing and deploying the agent.
3. Check in the console that every machine comes online, including after a reboot.
4. Uninstall TeamViewer after verification, in batches, starting with a pilot group.

For remote-work machines, schedule the deployment with the users: a laptop in extended sleep will not receive the package when you expect it to.

Step 4 — Import clients

1. Build an import file from your exports: client name, devices, assigned technician.
2. Import clients into Ubidesk and attach devices once the agents are online.
3. Test one unattended connection and one Wake-on-LAN per client before calling the cutover done.

Cutover checklist

• TeamViewer export archived outside the old account
• Ubidesk workspace created, residency region chosen (EU, Canada or United States)
• Technicians created, MFA active
• Ubidesk agents redeployed across the whole fleet
• TeamViewer uninstalled from machines
• Clients imported and devices attached
• Test session per technician
• TeamViewer subscription cancelled after the dual-run period

Honest notes

TeamViewer has the advantage of being familiar to your users, so the cutover needs a small communication effort the first time they join a Ubidesk session. The delicate part is the same as in any migration: devices outside your network. See also Migrating from ScreenConnect if you run both tools.