This section describes two separate, but related procedures, backing up a Sisense installation and migrating a Sisense installation from one machine to another.

Backing up your installation is recommended before a migration process, but also on a regular basis for securing your data and Sisense configurations.

You may need to migrate your entire setup when moving from a staging/development environment to a production environment, when upgrading hardware, etc.

Note: If you have advanced and/or customized web configurations, such as SSL, SSO, redirects, etc., please consult us through our Help Center.

Backing Up a Sisense Installation

The backup process requires backing up data from the two main Sisense components, the ElastiCube server and the Sisense Web Application.

In addition, if you have any custom plugins located in the directory C:\Program Files\Sisense\PrismWeb\plugins, this folder should be backed up as well.

The following procedure describes how to back up the data from the two components.

To back up Sisense data:

  1. To back up ElastiCube data, enter the following path:
    For Sisense V6.6.1 and earlier:


    Note: This is the default path. To check which path is being used, open the Sisense Server Console and click on the server preferences icon pref cog to verify the correct path.
    Each folder in this location represents an ElastiCube, and contains both the ElastiCube schema, and the data that was imported when the ElastiCube was built. Copy the data to your backup location.

  2. To back up Sisense Web data, go to:
    For Sisense V6.6.1 and earlier:
    %ProgramData%\Sisense\PrismWeb\DB\ProdFor Sisense V6.7 and later:

    For more information, see Backing Up the Application Database.

  3. Copy the data to your backup location.
  4. (Optional) Back up your custom plugins by copying the folder C:\Program Files\Sisense\PrismWeb\plugins and saving it in the appropriate folder in the new server.

Migrating a Sisense Installation

The migration process involves migrating data for the two main Sisense components, the ElastiCube server and the Sisense Web Application. If you are using plugins, you must back up the Plugins folder as well located in C:\Program Files\Sisense\PrismWeb\plugins. The following procedures explain the migration procedures for each component.

ElastiCube Server

ElastiCube data is stored in folders per ElastiCube. Each folder contains both the ElastiCube schema, and the data that was imported when the ElastiCube was last built. You can either copy the folder where the data is stored, or export the data.
Note: If you had build failures/server restarts, you may encounter multiple copies of the same ElastiCube. You can identify the latest ElastiCube by the path shown in the Server Console.

  1. Before you begin, Sisense recommends declaring downtime to avoid the loss of work during the process.
  2. Open the Sisense Server Console. Do one of the following:
    • Copy the data folder (see above in the migration section)
    • Export the the data to an .ecdata file.  Click here for instructions on how to export your data.
      Note: You must stop the server before exporting the data. Click Stop to stop the server.
  3. In the new server, attach the copied data, or import the .ecdata file you exported in the previous step.
  4. Start the server.
  5. If the database location was changed as well, modify the connectivity settings. Click here to learn how.
    Note: If you change the location, first stop the the IIS as follows:

    • If you are using IIS: Open the command line interpreter and type iisreset /stop.
    • If you are  using IIS Express: Open Services sisensewebExpress, right-click and select Stop.

Sisense Web Application

The Sisense web data contains user, dashboard, widget, and other information. This information is stored in a MongoDB instance on the machine where your Sisense Web Application is installed.

The data is stored in the following directories:

For Sisense V6.6.1 and earlier:


For Sisense V6.7 and later:


From these directories, it can be backed up and moved to your new server.

Note: You can access the database on the Sisense web server using any MongoDB Browser by connecting to localhost on port 27018.

To transfer the Sisense Web Application data, you can use one of the following methods depending on your requirements:

  • If you don’t have many dashboards already and do not need too much setting up (adding new users, configuring sharing, data security and other system settings), then you can export the dashboards from the old environment and import them into the new one, set new sharing permissions and configure the environment per your required settings. To learn more, click here.
    Note: If you have any plugins that are based on specific dashboards or widgets, you must modify them manually with their new IDs, as these IDs change when imported into a new environment.
  • If you have created quite a few dashboards and have already configured sharing, data security and other system settings, you can transfer your existing environment as is. In this case, you must:
  1. Back up your current MongoDB database and copy it to the new environment, as follows:
    1. To back up the old environment, open your machine’s Control Panel, and go to System and Security > Administrative Tools > Services, and stop the SisenseRepository service (this will make the website inaccessible). You can run the following command:Stop Sisense.Repostory
    2. Create a copy of the entire Prod folder.
    3. Start the SisenseRepository service again to get the website up again.Start Sisense.Repostory
    4. To restore in the new machine, stop the SisenseRepository service.
    5. Replace the existing Prod folder with the one you backed up.
    6. Start the SisenseRepository service.
  2. Migrate the ecdata (schema and data):
    • Stop the Web service to ensure the ElastiCube is not triggered during the copy process:
      • If you are using IIS: Open the command line and type in iisreset /stop
      • If you are  using IIS Express: Open Services > sisensewebExpress, right-click and click Stop.