Skip to main content

Migrating from Orion to Tessera

Migration Process

We recommend use of Tessera as a drop-in replacement private transaction manager in place of Orion. As Tessera supports the same endpoints and functionality, nothing needs to be changed in your Besu deployment to migrate. However, as Orion and Tessera can not communicate, you must stop all privacy-enabled Besu nodes in the network to perform the migration. Besu nodes without an associated private transaction manager can remain live during this time.

A utility is included in Tessera which enables migration of an Orion configuration file and database to a Tessera configuration file and database.

A full migration workflow would be as follows:

  1. Build or download the migration utility.
  2. Shut down all privacy-enabled Besu nodes and Orion instances in the network (non-privacy-enabled nodes can remain active).
  3. Perform configuration and database migration.
  4. Start Tessera instances with the new configuration and database files.
  5. Restart all privacy-enabled Besu nodes in the network.

Build Migration Utility

The utility can be built from the Tessera repository.

First clone the Tessera repository:

git clone

Navigate to the project root directory:

cd tessera

Build the migration utility with the Gradle wrapper gradlew:

./gradlew clean migration:orion-to-tessera:installDist -x test

Download Migration Utility

Or download the migration utility binaries, which are available at the following download links: .zip and .tar.

Verify Installation

Verify the installation by running the migration utility with the --help flag.

./bin/migrate --help


By default Tessera uses an H2 database. However, you can configure alternative databases. Refer to the SQL Data Definition Language files for help with other databases.


If migrating from an SQL database to Tessera, you must add the JDBC driver to the CLASSPATH environment variable and to the start script at ./bin/migrate.


Password protected keys are migrated to the Tessera format as part of the migration. The original Orion format keys are renamed with a .orion suffix.

Verify State and Stop Services

Verify the private state root and private transaction count on your Besu and Orion network using priv_debugGetStateRoot

"jsonrpc": "2.0",
"method": "priv_debugGetStateRoot",
"params": ["MC4aHjApHsGb0j5glU2iAj5KcR5LId52S0BU9mtdeuY=", "latest"],
"id": 1

and then priv_getTransactionCount.

"jsonrpc": "2.0",
"method": "priv_getTransactionCount",
"params": [
"id": 1

After recording the state root and transaction count, stop your Besu and Orion nodes.

Run Migration

Begin the migration by running migrate with all required options. Substitute Orion config file, outputFile, password, url and username with your own values.


To ensure you have the correct database path, run the migration tool from the same directory in which Orion was running. Alternatively, modify the Orion configuration file to add storage and workdir parameters with absolute paths.

./bin/migrate -f <Orion config file> -o <outputFile> tessera.jdbc.password <password> tessera.jdbc.url <url> tessera.jdbc.user <username>

On a successful migration, the count of transactions and privacy groups migrated will match expected values.

Restart Services and Verify State

Start Besu and Tessera using the new Tessera configuration file and database.

Verify the private state root and private transaction count on your Besu and Tessera network using priv_debugGetStateRoot and priv_getTransactionCount.

It should give identical results to those collected earlier.


You must specify the following options in order to run the migration tool:

Orion config file= Orion configuration file location

outputFile= Target Tessera configuration file location

username= Target Tessera database username

password= Target Tessera database password

url= Target Tessera database JDBC connection string

Enterprise support

If you require support to undertake this process or any other use of ConsenSys Quorum software, ConsenSys offers support subscriptions for Quorum to accelerate time to market and provide confidence in production networks. Visit the following site to find out more: ConsenSys Quorum Support.