Migrating from ScreenConnect

What transfers, what does not

Let’s be clear about the scope before starting. What transfers well:

• the endpoint list and how machines are grouped per client;
• client names and contact details;
• technician accounts, recreated in Ubidesk.

What does not transfer:

• ScreenConnect session history: it stays in the old instance, export it before cancelling;
• passwords and secrets stored on the ScreenConnect side;
• scripts and extensions: recreate them in Ubidesk.

Plan for a dual-run period: both tools run in parallel until the agents are redeployed.

Step 1 — Export endpoints from ScreenConnect

1. Sign in to the ScreenConnect administration.
2. Export the machine list: the administration lets you export a CSV with each endpoint’s name, address and group.
3. Separately export machine-to-client assignment and security groups, if you use them.
4. Keep these exports outside the old server, somewhere shared by the team running the cutover.

Step 2 — Create the Ubidesk workspace and map technicians

1. Create the Ubidesk workspace and choose the plan. From Pro up, the device count is unlimited (24 EUR per technician per month).
2. Create one account per technician. MFA is mandatory (TOTP, passkeys or FIDO2): allow a few minutes per person.
3. Recreate machine groups in the console to keep your organization.
4. For a large fleet, start the dual run at this stage: both consoles stay usable in parallel.

Step 3 — Redeploy the agents

The Ubidesk agent must replace the ScreenConnect 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.
4. Uninstall the ScreenConnect agent after verification, machine by machine or in batches.

This step sets the duration of the cutover: the more heterogeneous the fleet, the more margin you should plan.

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. Spot-check that one device per client responds before removing the old tool at that client.

Cutover checklist

• ScreenConnect export archived outside the old instance
• Ubidesk workspace created, residency region chosen (EU, Canada or United States)
• Technicians created, MFA active
• Ubidesk agents redeployed across the whole fleet
• ScreenConnect agent uninstalled
• Clients imported and devices attached
• First test session per technician
• Old instance cancelled after the dual-run period

Honest notes

ScreenConnect remains a solid product; the migration is justified by per-technician cost and a simpler stack. The delicate part is not exporting the data but redeploying agents on machines outside your direct control (remote workers, distant clients). If you also manage a TeamViewer fleet, see Migrating from TeamViewer.