Migration from Sisense Windows Deployment

Sisense provides a migration tool for migrating existing Windows deployments to Linux deployment. The Windows2Linux migration tool migrates the following Sisense assets from a Sisense deployment in Windows to a Sisense deployment in Linux:

The following assets are not migrated and must be migrated manually:

In a single node deployment, the Windows2Linux migration tool should be run from your production machine. If you have implemented a multi-node deployment, the tool should be run on one of your query nodes. This assumes that your query nodes are identical. If they are not identical, then you should run the tool on each query node you want to migrate. When you run the migration tool on the second query node, you should perform a partial migration of just the .ecdata files. In this scenario, you should consult with Sisense Technical Support for more information.

As the migration tool is run on one of your query nodes and not a build node, if you have any customized files, such as rebranded emails or translated language files, you must migrate these manually to the following directories in your Linux machine:

Note: In multi-node deployments, these files are saved in shared storage that you can access with the command: 
kubectl -n [NAMESPACE] cp [FILENAME] management-<TAB>:/opt/sisense/storage/[shared asset name - plugins, languages, emails]

When you run the migration tool in Windows, Sisense duplicates all the assets to be migrated in a new directory automatically created on your Windows machine. Keep in mind that depending on the size of your .ecdata files (your data models and their data), this assets directory can be quite large and you must insure that you have enough space to support these files. Once the migration is complete, the assets directory is deleted, while your original files remain on the machine.

Note: SSO will be disabled automatically in Linux after migrating the Sisense assets.


  1. Sisense V7.2 and higher
  2. Data is transferred through SSH through port 22
  3. Downtime is required for each ElastiCube only while exporting the ElastiCube data
  4. SSO is disabled automatically in Linux, after migration you will need to enable it in Linux manually

  5. Moving assets from Windows to Linux uses SCP, which uses Secure Shell (SSH) for data transfer. You should ensure that such communication possible from Windows to Linux machines