Migrate your Splashtop Remote Support data

Every managed endpoint in Splashtop Remote Support is a Computer object with properties including Computer Name, Group Name, Last Session Time, and Notes. We export the full computer list as a CSV from the Management console and map each row to the destination platform's device/endpoint object. The Streamer must be reinstalled on migrated endpoints as part of any new remote support platform deployment.

Technicians are the licensed users who initiate remote support sessions. We map Technicians to the destination's technician or agent object, preserving role assignments. Splashtop Remote Support tiers (Basic, Plus, Premium) limit the number of concurrent technicians, which factors into our scoping.

Computers can be organized into named Groups for easier management and permission scoping. We export Group assignments alongside the computer list and reconstruct the group hierarchy in the destination platform. Group-level access permissions are preserved in the Access Permissions CSV.

Access Permissions define which Technicians can reach which Computers or Groups, along with their role. Splashtop exports these as a CSV showing user-to-endpoint assignments, roles, and status. We map these to the destination platform's permission model, which may use different role names or inheritance structures, requiring explicit field mapping.

Enterprise tier supports Service Desk Channels with features like SOS Call, invitation links, PIN codes, and web form widgets. Custom fields can be defined on web forms. We map Channel configurations and their associated custom field schemas, though destination ITSM platforms often use fundamentally different data models for tickets and channels.

Splashtop does not expose a full session history export via its public API or admin console CSV export. Session logs are retained within the Splashtop web console but are not available as a standalone downloadable dataset. We flag this for customer awareness and note that Splashtop's REST API can export limited log data for integration with third-party analytics tools.

Splashtop Connector supports importing and exporting RDP profiles as CSV files, including fields like Profile Name, Deploy Code, Enable Recording, and RDP-specific settings. We transfer profile CSVs where present, but RDP profile schemas vary significantly and often require manual reconfiguration in the destination.

Splashtop SOS Call generates support requests from end users, which can be routed to technicians or channels. These are tracked within the Service Desk console. We map open SOS requests to the destination ticketing system, preserving requester identity and status, but the destination ticketing workflow may not have a direct equivalent.

Splashtop Remote Support uses deployment codes to silently install the Streamer on managed computers. These codes are scoped to the account and tied to the computer inventory. We preserve the deployment code used for each computer where available, but destination platforms use their own deployment mechanisms (agents, MDM, etc.) that must be separately configured.

Splashtop defines roles like Admin, Technician, and User with granular permission levels. The role definitions themselves are not exported as a standalone artifact; we infer them from the Access Permissions CSV. Destination platforms often use RBAC models with different built-in roles and custom permission sets that require manual alignment.