Skip to main content



How can we help you?


Druva Documentation

Guidelines for moving from inSync On-Premise to inSync Cloud

Heads up!

We've transitioned to a new documentation portal to serve you better. Access the latest content by clicking here.

Product edition: inSync On-Premise and inSync Cloud



The article aims at a seamless process of configuring inSync Client to backup to inSync Cloud from your existing On-Premise environment. No configuration or data will be migrated to Cloud in this process.  All the clients activated to inSync Cloud will perform a full backup initially.

Users with Windows Active Directory infrastructure integration and Windows client may benefit from this information. 

Migration involves two major tasks:
1.    Migrating inSync users
2.    Upgrading inSync Client versions 


Ensure following configurations are performed before migrating users:

  1. Install AD Connector on the machine or a Server which is always online and is connected to AD. 
  2. Register an AD account on inSync Management Console. The account must have read-only permissions on the domain.
    The procedure to configure AD connector is described in the Configure the inSync Ad/LDAP Connector section
  3. Remote deployment tool, such as SCCM, Landesk, or GPO, to deploy the package and script on all the systems. 

Migrate inSync users

You can refer to the On-Premise instance while performing these steps.

  1. On inSync Management Console for cloud, create a profile which is similar to the profile you have on the On-Premise Server. See Create a profile.
  2. Create an AD mapping to migrate users from AD. Druva recommends to create a security group in AD and map it to inSync.
    While creating the AD-mapping, always select “All-Users” in OU. Map the Security Group at the end to avoid issues for users with group membership change. The steps for creating AD mapping are described in the Creating an AD mapping section.

Upgrade inSync Client versions

inSync Client version for Cloud and On-Premise are different. Therefore, you need to replace the On-Premise Client with of inSync Cloud Client and activate it with the Cloud instance. inSync Client will perform a complete backup to inSync Cloud only when it is activated.

 Here is a sample script that you can use on Windows systems to uninstall On-Premise Client, install the Cloud Client, and finally activate the Cloud Client with a Cloud instance.

Considerations for the script:

  • The script is created for inSync Client 5.9 version and will not initiate on systems already having Client 5.9 installed. 
  • The script is controlled by the REG Query parameter provided in the first line of the script:

    REG Query "HKEY_CLASSES_ROOT\Installer\Products\752C201840E984F4AB16ABE5EF4CE7D6" >> "C:\inSyncReactivate.log"  2>&1
  • You need to change the registry value according to the latest version of inSync Client available.
  • You must update the port according to your configuration. Contact your system administrator if you are not sure of the configured port. 
  • If you use IMDv2 while deployment, provide the token in single quotation marks (').

Sample script

echo on

REG Query "HKEY_CLASSES_ROOT\Installer\Products\752C201840E984F4AB16ABE5EF4CE7D6" >> "C:\inSyncReactivate.log"  2>&1
if %errorlevel% == 0 GOTO END

net stop inSyncCPHService   >> "C:\inSyncReactivate.log"  2>&1
timeout -t 10
TASKKILL.exe /f /im inSyncAgent.exe >> "C:\inSyncReactivate.log"  2>&1
timeout -t 2

wmic product where "name like '%%Druva inSync%%'" call uninstall /nointeractive >> "C:\inSyncReactivate.log"  2>&1

timeout -t 2

reg query "HKLM\SOFTWARE\Wow6432Node\Druva Software" >> "C:\inSyncReactivate.log"  2>&1
if %errorlevel% == 0  reg delete "HKLM\SOFTWARE\Wow6432Node\Druva Software" /f >> "C:\inSyncReactivate.log"  2>&1

reg query "HKLM\SOFTWARE\Druva Software" >> "C:\inSyncReactivate.log"  2>&1
if %errorlevel% == 0  reg delete "HKLM\SOFTWARE\Druva Software" /f >> "C:\inSyncReactivate.log"  2>&1

timeout -t 2

Ren "C:\inSync4" inSync_old  >> "C:\inSyncReactivate.log"  2>&1
Ren "C:\ProgramData\Druva\inSync4" inSync_old  >> "C:\inSyncReactivate.log"  2>&1
Ren "C:\Program Files(x86)\Druva" Druva_old  >> "C:\inSyncReactivate.log"  2>&1

timeout -t 2

msiexec /qn /i "<path to inSync msi>" TOKENV2='<mass deployment token>' SERVERLIST="<Backup/sync port>"


See also:

  • Was this article helpful?